>> ... organizational nulls are all hidden, maybe even locked too to
prevent them being disturbed (looking at you animators). :P

You could call the main hidden null "*kraken*" and be all like,
*"NEVERrelease the Kraken!"
* :p


On Thu, Jun 20, 2013 at 1:13 PM, Eric Thivierge <[email protected]>wrote:

> At a very basic level this is correct. Though can get a bit more complex
> in that under the model (namespace) there can be other organizational
> structures (nulls for example) that also do not move but are more to
> separate the different parts of the rig. One null for controls, one for
> meshes, one for deformers (null objects used in envelopes).
>
> Exampe:
>
> char_bob_midres_rig (model, at zero)
> - char_bob_midres_deformers (null, at zero)
>  - eye_L_def (constrained to object in control hierarchy)
>
> - char_bob_midres_controls (null)
>  - ice_host (null, at zero, calculates some deformation / kinematic data)
>  - srt_M_ctrl (animatable)
>    - offset_M_ctrl (animatable)
>
> - char_bob_midres_geometry (null)
>  - body_M_midres_geo (mesh, at zero)
>  - eye_L_midres_geo (mesh, at zero)
>
> Hope that clears it up. Also worth noting is that the model, and
> organizational nulls are all hidden, maybe even locked too to prevent them
> being disturbed (looking at you animators). :P
>
>
> Eric Thivierge
> ===============
> Character TD / RnD
> Hybride Technologies
>
>
> On June-20-13 1:06:15 PM, Ponthieux, Joseph G. (LARC-E1A)[LITES] wrote:
>
>> Eric,
>>
>> Thanks. I guess now I am confused. I always interpreted Model as a
>> toplevel parent. If I understand this right the practice is to have a
>> transform group underneath the Model and the rest of the hierarchy
>> underneath the transform group? All animation is then performed at the
>> transform group and below while the model is nothing more than a "mini
>> scene" container and kinematics at model level are ignored. Is that a
>> correct assumption?
>>
>> --
>> Joey Ponthieux
>> LaRC Information Technology Enhanced Services (LITES)
>> Mymic Technical Services
>> NASA Langley Research Center
>> ______________________________**____________________
>> Opinions stated here-in are strictly those of the author and do not
>> represent the opinions of NASA or any other party.
>>
>>
>> -----Original Message-----
>> From: 
>> softimage-bounces@listproc.**autodesk.com<[email protected]>[mailto:
>> softimage-bounces@**listproc.autodesk.com<[email protected]>]
>> On Behalf Of Eric Thivierge
>> Sent: Thursday, June 20, 2013 11:58 AM
>> To: [email protected].**com <[email protected]>
>> Subject: Re: Models and ICE
>>
>> Well even outside the realm of ICE, moving the model from zero has always
>> been frowned upon.
>>
>> When dealing with objects with simulations on them that are under the
>> model, the model's matrix if not at world zero can do funky things and have
>> you pulling out hair and punching babies. Not that I've ever punched a
>> baby...
>>
>>
>> Eric Thivierge
>> ===============
>> Character TD / RnD
>> Hybride Technologies
>>
>>
>> On June-20-13 11:48:45 AM, Ponthieux, Joseph G. (LARC-E1A)[LITES] wrote:
>>
>>> That’s really disappointing to hear.
>>>
>>> I’ve got a large set of previously built model assets I want to use. I
>>> could just convert them to old school and parent their structure with
>>> a null as a opposed to a model, but that seems a real waste. It also
>>> seems contradictory to where ICE was headed.
>>>
>>> What’s the point of expanding ICE beyond particles or point clouds if
>>> it’s not recommended to use it on model assets?
>>>
>>> --
>>>
>>> Joey Ponthieux
>>>
>>> LaRC Information Technology Enhanced Services (LITES)
>>>
>>> Mymic Technical Services
>>>
>>> NASA Langley Research Center
>>>
>>> ______________________________**____________________
>>>
>>> Opinions stated here-in are strictly those of the author and do not
>>>
>>> represent the opinions of NASA or any other party.
>>>
>>> *From:*softimage-bounces@**listproc.autodesk.com<[email protected]>
>>> [mailto:softimage-bounces@**listproc.autodesk.com<[email protected]>]
>>> *On Behalf Of *Peter
>>> Agg
>>> *Sent:* Thursday, June 20, 2013 11:40 AM
>>> *To:* [email protected].**com<[email protected]>
>>> *Subject:* Re: Models and ICE
>>>
>>> I would not recommend using ICE on models, to be honest - have a null
>>> underneath it and apply it to that instead. In my (kinda) humble
>>> opinion; if a model is anywhere but world zero I disprove. :)
>>>
>>> On 20 June 2013 16:31, Ponthieux, Joseph G. (LARC-E1A)[LITES]
>>> <[email protected] <mailto:[email protected]>> wrote:
>>>
>>> Is there a standard procedure for how to use ICE with Models?
>>>
>>> Is it not recommended to apply ICE to Models then?
>>>
>>>
>>> --
>>> Joey Ponthieux
>>> LaRC Information Technology Enhanced Services (LITES) Mymic Technical
>>> Services NASA Langley Research Center
>>> ______________________________**____________________
>>>
>>> Opinions stated here-in are strictly those of the author and do not
>>>
>>> represent the opinions of NASA or any other party.
>>>
>>> -----Original Message-----
>>> From: 
>>> softimage-bounces@listproc.**autodesk.com<[email protected]>
>>> <mailto:softimage-bounces@**listproc.autodesk.com<[email protected]>
>>> >
>>> [mailto:softimage-bounces@**listproc.autodesk.com<[email protected]>
>>> <mailto:softimage-bounces@**listproc.autodesk.com<[email protected]>>]
>>> On Behalf Of Eric
>>> Thivierge
>>> Sent: Thursday, June 20, 2013 11:27 AM
>>> To: [email protected].**com <[email protected]>
>>> <mailto:softimage@listproc.**autodesk.com<[email protected]>
>>> >
>>> Subject: Re: Models and ICE
>>>
>>> That may return the scene root if the model is under the scene root
>>> though.
>>>
>>>
>>> Eric Thivierge
>>> ===============
>>> Character TD / RnD
>>> Hybride Technologies
>>>
>>>
>>> On June-20-13 11:17:02 AM, Matt Morris wrote:
>>>
>>>> If its a model you might try using this_model instead of self?
>>>>
>>>>
>>>> On 20 June 2013 15:56, Ponthieux, Joseph G. (LARC-E1A)[LITES]
>>>> <[email protected] <mailto:[email protected]>
>>>>
>>> <mailto:[email protected] <mailto:[email protected]>>**> wrote:
>>>
>>>>
>>>>      I’ve run into the situation where I attempt to apply an ICE tree
>>>>      to a Model, but the ICE window browser gives the status____
>>>>
>>>>      __ __
>>>>
>>>>      “All items hidden due to a filter”____
>>>>
>>>>      __ __
>>>>
>>>>      If I proceed to create an ICE tree on the Model, it works, but
>>>>      does not behave as expected.____
>>>>
>>>>      __ __
>>>>
>>>>      __ __
>>>>
>>>>      Further, if the Model’s name is “Test”, and I attempt to Set data
>>>>      on it with____
>>>>
>>>>      __ __
>>>>
>>>>      Test.kine.pathcns.perc____
>>>>
>>>>      __ __
>>>>
>>>>      It is valid,____
>>>>
>>>>      __ __
>>>>
>>>>      __ __
>>>>
>>>>      But this:____
>>>>
>>>>      __ __
>>>>
>>>>      self.kine.pathcns.perc____
>>>>
>>>>      __ __
>>>>
>>>>      is not valid and lights up like a stop light.____
>>>>
>>>>      __ __
>>>>
>>>>      __ __
>>>>
>>>>      What did I get wrong?____
>>>>
>>>>      __ __
>>>>
>>>>      __ __
>>>>
>>>>      --____
>>>>
>>>>      Joey Ponthieux____
>>>>
>>>>      LaRC Information Technology Enhanced Services (LITES)____
>>>>
>>>>      Mymic Technical Services____
>>>>
>>>>      NASA Langley Research Center____
>>>>
>>>>      ______________________________**________________________
>>>>
>>>>      Opinions stated here-in are strictly those of the author and do
>>>>      not ____
>>>>
>>>>      represent the opinions of NASA or any other party.____
>>>>
>>>>      __ __
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> www.matinai.com <http://www.matinai.com> <http://www.matinai.com>
>>>>
>>>
>>>
>>
>

Reply via email to