Still hijacking...
>Unless of course you read the manual first, in which case you'd be familiar
>with XSI's terminology and know better than to e-mail support about it...
>The term "model" in XSI describes something very specific (a type of
>object). So, "export model" does exactly what it says it does. It exports an
>XSI model just not any old 3d model. The terminology can be confusing...
We both don´t live in an ideal world. Otherwise, this list wouldn´t exist
to post questions to, nor would there be a real requirement to share
Tips&Tricks...
Ok, I sounded a bit harsher than I meant to, sorry for that. But surely if you are having a problem with a feature such as export model not exporting what you think it should be exporting you would spend the 3 minutes to hit F1 in a viewport, type in "export model" in the string search tab and read the file menu section to see what "export model" does, instead of declaring it as buggy and unsafe and rely on other formats than the native xsi one and treating that as gospel...
To minimize any losses, like passes, materials, position and organization,
I´d have clicked "export selection as *.scn", this isn´t available, so I´d
resort to exporting to a model. But a model (in terms of workflow) is
more geared towards referencing and such, expected to be organized
cleanly and readily.
It's geared at whatever you want it to be geared at... heaps of people use them to export characters, rigs, bits of geometry, fxTrees, whatever, it's the native XSI "subscene" object and you can use it to store whatever the heck you want... if you want to export the whole scene, save the scene, if you want just bits and bobs of a scene, stick them under a model and export that... it will preserve everything you had such as construction history, materials, animation etc, which you lose when you export to OBJ. It is also a hell of a lot more reliable than dotXSI (other than the fact that it is tied to the version of XSI which was used to generate it, and can't be exported for previous versions of XSI).
I was trying toexpor snippets to work on seperately.
Again, it's perfectly geared towards that as long as all the dependencies are exported with model. If you freeze the geo you want to export there is no dependencies to worry about...
Anyways, have fun modelling! :)
