Yeah, actually, the FBX commands are the only ones I ever came across
that have spaces in the command name. That combined with the russian
roulette of varying massive bugs in all of the different versions
available makes it pure fun to use... ;)
Hans,Veenendaal,AMplus R&D,SOJ wrote:
Hello Andre,
In VBScript you should be able to call custom commands without using the ExecuteScriptCommand form, but because of the space in the command name you cannot.
That's why I hacked the fbxxsi.dll to have 'FBX_Export' and 'FBX_Import' as the command names instead of 'FBX Import' and 'FBX Export'. It just makes more sense.
Whoever came up with having/allowing spaces in command names should be fired. :-)
Anyway, thanks for the ExecuteScriptCommand solution. Now I can run the script on the unmodified DLL as well. Much appreciate it.
Hans.
-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Andre Adam
Sent: Wednesday, January 10, 2007 7:31 PM
To: XSI(at)Softimage.COM
Subject: Re: FBX question
For importing it works like this, should be the same for a scripted export:
ExecuteScriptCommand("FBX Import", Array(eFBXFiles.item(), 1)); //Import
FBX file
Cheers!
-André
Hans,Veenendaal,AMplus R&D,SOJ wrote:
How do you export FBX from script?
FBX Export "C:\Temp\Test.fbx"
doesn't work.
Thanks,
Hans.
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
