Hi Bernard,
I´m sorry for hijacking your thread but really grateful for
the info on using models. Great to know how it´s supposed
to be used. Kim is right by the way, I don´t want developers
distracted by having them clutter the interface with extra buttons.
It´s just in this case, to make it failsave, IF you export to an
.emdll and don´t have a model as topmostnode selected, the
export should prompt you to specify a name/model because
otherwise the export would simply not work reliably. You´d
create a bogus export, flood the support hotline with requests
and would get the feeling XSI is unreliable. And if two lines of script
(no extra button) checking this make this obsolete and userfriendly..
The most efficient userinterface (almost no buttons) I´ve ever
used sofar is the GUI from UVlayout: http://www.uvlayout.com/
Currently in beta, worth checking it out. Takes a while to grasp
the workflow but rewards with extrem speed and ease of use.
Another example would be the new microsoft office package,
they also kicked the menuebars - and assistant - but it´s said
to be too much for most users. (E.g. not for the fainted hearted
average user writting two letters a year).
Whatever, thanks for this pre-"Tips&Tricks" session.
I´d love to see the Montreal show in person.
Cheers
tim
P.S: Porl is right, too. Fortunately, I don´t have a mobile...
----- Original Message -----
From: "Bernard Lebel" <3dbernard(at)gmail.com>
To: <XSI(at)Softimage.COM>
Sent: Wednesday, May 31, 2006 2:02 AM
Subject: Re: XSI Montreal "Tips & Tricks" session, looking for presenters
I´ll definitely look into using the model node, even if I find this
an extra step (worth it for organizing things). Given my backround
in Maya, I would have expected a "save selected as *.scn btw.
That's almost what exporting a model is, Tim. The equivalent of a Maya
namespace, in XSI, is a model. There are very little differences
between a model and the scene root, the scene being a top-most model
with extra properties and features. So you can consider models in a
scene as "sub-scenes in a scene".
When you put things under a model, you are putting these things in an
near-exclusive space. Object name defined in this space will not clash
with names outside the model, and if you make sure to not create
connections with outside the models, you can transfer anything that is
under the model without a problem (unless there is corruption or
something fishy going on).
More, via models you get reference models, which are imho a strong
asset in a pipeline, under certain usage guidelines. No other format
in XSI gives you that.
Just select the objects you want to export, choose MCP > Edit > New
Model, and all the selected objects will be parented under this model.
Then perform the export. An extra step, but a worthy one.
Cheers
Bernard
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
