it never stroke my mind to export a selection of loose objects as a
model. actually i wonder that its possible at all. there you see how
complex software grows and the insane variety of users and their
habbits.
the natural way would create a model out of a selection and export it.
and i dont see any reason why one should not follow this workflow.
for the center and crazy moving objects i have a question myself.
for sure one has to really read and understand the concept XSI follows
with centers, animatable pivots, neutral poses and the different
transformation modes and what they actually transform.
imagine you got a eye hovering around at its right place in the
character. the transformation center however sits at 0,0,0 (likely
someone was freezing the transformations once).
now, to get the center back into the middle of the eye i would move
the center to the surrounding box/or vertices. that will last till i
reload the scene. but to really move it and fix it there i would
create a neutral pose when the center is in the middle of the eye. i
end up with a center operator in the stack. now i freeze the stack and
the center sits in the middle again.
is THIS the right and failure proofed way to shift centers?
one thing i learned while working with XSI. you should not, i repeat
NOT, push buttons and see what it does. you should KNOW what a button
does(best in depth) and then use it. 3dsmax behaviours lead to complete
destruction, sooner or later ;)
thanks
ciao
franky
Wednesday, May 31, 2006, 7:33:49 PM, you wrote:
TL> From: "guillaume laforge" <guillaume.laforge.3d(at)gmail.com
>> So much noise for nothing. Everybody export-import models everyday without
>> problems so WHAT IS THE PROBLEM ?
>>
>> Sorry...
>>
>> my BIG 0.00000001 euro
TL> the below shows a step by step reproduction of the problem, in a
TL> nutshell, a multiselection export as *.emdl file is accepted without
TL> error checking if there is a modelnode for the entire selection present,
TL> instead, the first selected object is put into a new model (according to
TL> the name the file is saved) and all other objects are ignored in the export.
TL> This may lead to dataloss that is difficult to track down as it´s neither
TL> documented nor expressedly desired behaviour to be toggled.
TL> Cheers
TL> tim
TL> ----- Original Message -----
TL> From: "Joey Ponthieux" <j.g.ponthieux(at)LaRC.NASA.GOV>
TL> To: <XSI(at)Softimage.COM>
TL> Sent: Wednesday, May 31, 2006 5:53 PM
TL> Subject: Re: XSI Montreal "Tips & Tricks" session, looking for presenters
>> Alan,
>>
>> Make a cube, a sphere, and a cone.
>> Select the cube.
>> Go File>Export>Model.
>> Give the Model name Temp.
>> Import Temp.emdl into a new scene in a separate XSI session.
>> You will note that Temp is a Model with the cube underneath.
>>
>> Now go back and select sphere first, cube second, then cone.
>> Go File>Export>Model.
>> Give the Model name Temp2.
>> Import Temp2.emdl into a new scene in a separate XSI session.
>> You will note that Temp2 only possesses sphere.
>>
>> The ability to export selected objects is either broken or needs to be
>> removed as it misleads the user into thinking that this is a functional
>> way of doing business.
>>
>> It is not. Single vs Multi selection distinction was done away with Soft
>> 3D. This should be a multi-selection procedure. It is not. It is broken.
TL> ---
TL> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
TL> unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
