Re: XSI Import troubles

2012-06-28 Thread Stefan Kubicek
The FBX framework (incl. Converter) has been updated to version 2013.2: http://www.the-area.com/forum/autodesk-fbx/fbx-sdk/fbx-20132-now-available/page-last/ Download: http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112id=10775855 Does ne1 know as to why there is no Softimage plugin for

RE: XSI Import troubles

2012-06-28 Thread Stephen Blair
Sent: June-28-12 3:29 AM To: softimage@listproc.autodesk.com Subject: Re: XSI Import troubles The FBX framework (incl. Converter) has been updated to version 2013.2: http://www.the-area.com/forum/autodesk-fbx/fbx-sdk/fbx-20132-now-available/page-last/ Download: http://usa.autodesk.com/adsk

XSI Import troubles

2012-06-07 Thread olivier jeannel
Hi guys, I might have to work with CityEngine http://www.esri.com/software/cityengine/ in a near future. The Basic version of CityEngine only exports in .obj. In Softimage the opening of a sample Obj of 8 buildings (43 polymesh, 43 materials, total of 1300 faces) takes around 15s. The

Re: XSI Import troubles

2012-06-07 Thread olivier jeannel
Hi Dan, Here's the file : https://www.dropbox.com/c/shmodel?nsid=137042506sjid=0state=2signature=dc46ef3path=/OBJ_1.zipid=shmodel Downloading the Autodesk converter atm. Le 07/06/2012 15:17, Dan Yargici a écrit : Have you tried using the Autodesk FBX Converter (converts obj also) found here:

Re: XSI Import troubles

2012-06-07 Thread Dan Yargici
Hi Olivier, that link doesn't work for me, I get: Error Creating Link There was an error creating your link. Please try againhttps://www.dropbox.com/home . On Thu, Jun 7, 2012 at 4:34 PM, olivier jeannel olivier.jean...@noos.frwrote: Hi Dan, Here's the file :

Re: XSI Import troubles

2012-06-07 Thread olivier jeannel
Yes thanks ! Still not able to change the textures path though. (can do it one by one), but the Search and replace doesn't seem to work on path... What is the syntax to change "every files" to [Project path]\Pictures\every files ? replace Le

Re: XSI Import troubles

2012-06-07 Thread Dan Yargici
If the search and replace supported regular expressions it'd be a breeze. I would think that the way it is now makes it pretty much impossible without scripting (and doing some RegExpr search/replacing...) On Thu, Jun 7, 2012 at 6:03 PM, olivier jeannel olivier.jean...@noos.frwrote: Yes thanks

Re: XSI Import troubles

2012-06-07 Thread Luc-Eric Rousseau
You can use the FBX library to import the .obj directly, without going through the converter, in Softimage 2013. Go in File-Crosswalk-ImportFBX, and change the filter to .obj The FBX .obj importer will be used instead of Softimage's native one. FBX also offers .3ds, .dxf and collada

Re: XSI Import troubles

2012-06-07 Thread olivier jeannel
...sometimes I feel like the difference between XSI and Notepad is close to none :( Le 07/06/2012 18:09, Dan Yargici a crit: If the search and replace supported regular expressions it'd be a breeze. I would think that the way it is now makes it

Re: XSI Import troubles

2012-06-07 Thread Guillaume Laforge
Of *olivier jeannel *Sent:* Thursday, June 07, 2012 8:03 AM *To:* softimage@listproc.autodesk.com *Subject:* Re: XSI Import troubles ** ** Yes thanks ! Still not able to change the textures path though. (can do it one by one), but the Search and replace doesn't seem to work on path... What

Re: XSI Import troubles

2012-06-07 Thread olivier jeannel
todesk.com] On Behalf Of olivier jeannel Sent: Thursday, June 07, 2012 8:03 AM To: softimage@listproc.autodesk.com Subject: Re: XSI Import troubles Yes thanks ! Still not able

Re: XSI Import troubles

2012-06-07 Thread olivier jeannel
To: softimage@listproc.autodesk.com Subject: Re: XSI Import troubles Yes thanks ! Still not able

Re: XSI Import troubles

2012-06-07 Thread Dan Yargici
Here you go. It's very quick, dirty, crude and un-foolproof, but will basically set the paths of all your image sources to Pictures\Filename... :) oSources = Application.FindObjects(, {BB74AA1E-12C5-11D3-B37A-00105A1E70DE}) for oSource in oSources: filePath = oSource.Filename.value fileName =

Re: XSI Import troubles

2012-06-07 Thread Alok
Hi Dan, A little more efficient code can be written using the os module. It will be more error-proof on all the platforms. import os oSources = Application.FindObjects("", "{BB74AA1E-12C5-11D3-B37A-00105A1E70DE}") for oSource in oSources:

Re: XSI Import troubles

2012-06-07 Thread Alok Gandhi
Thanks for enlightenment Joe, I know that there are some limitation with os module, that is why I said more error-proof and not absolutely error proof. Most of the time I would use: os.path.join(c, Desktop, Users, jo, mydatas) 'c\\Desktop\\Users\\jo\\mydatas' As far as possible I avoid using

Re: XSI Import troubles

2012-06-07 Thread jo benayoun
No need of plugins Eric, when coding on Notepad, you know you have to be aware of everything and can't trust anything. That makes your code looking * sublime*, smarter and more professional ! :D -- Jo 2012/6/7 Eric Thivierge ethivie...@gmail.com Notepad might have a plugin for all of that...