|
I have seen A friend at work have trouble
deciphering if a model is referenced or not in jscript. I would guess this might
be a quick fix for such a problem.
----- Original Message -----
Sent: Wednesday, June 21, 2006 12:58
PM
Subject: Re: Why prefix reference
models?
Thanks Rober and Francois,
Anyone have any insight as to
what the usefulness of this preference is-- or what the usefulness of
prefixing it is-- other than seeing that the name is changed? Does it
serve any other purpose?
Just trying to
understand...
Thanks.
On 6/21/06, Robert
Moodie <robertm(at)hybride.com> wrote:
Yep I see it broken with 2 ref
models.
1. But, as everyone else (and I) have said
- do a start up check for your XSI.
2. I honestly have never seen anyone change
this preference.
There are infinite-1 ways to break stuff in a
3D scene - most of them are a lot closer to the surface than this
preference.
-----
Original Message -----
Sent:
Wednesday, June 21, 2006 3:17 PM
Subject:
Re: Why prefix reference models?
Uh, duh.. you'll need the
ref models too, so that scene won't work.
brain screwed on wrong
today...
On 6/21/06, Mike
Werckle < stumbly(at)gmail.com>
wrote:
Thanks Robert--
Try constraining a ref model to another ref
model-- this is when it seems to break.
I'm enclosing a scene
with a test in it-- try loading it with prefixes on-- the cube remains
constrained to the sphere. Then turn prefixes off-- the cube is no
longer constrained. The cone, which is outside of reference
model space, remains constrained in either case.
As far as the
clip problem goes, I'm talking about having a constraint clip that lives
in the reference model. When you have a model that you have to
apply a lot of constraints to every time you load it into a scene ( e.g.
a rifle rig that you want to constrain to a character rig), it's very
handy to have a clip to set the contstraints-- instead of doing it by
hand (or merging in a scene where it's already assembled)
To do
this, you set the constraints in a non-referenced scene, then save them
to a clip that lives within the constrained object. Later, when
you import both objects as ref models, you can apply the constrain clip
and they will be re-constrained to each other-- but the catch is, it
only works with prefixes turned off.
That's the
problem.
Mike
On 6/21/06, Robert Moodie <robertm(at)hybride.com
> wrote:
>>Why add the "referenced" prefix to reference models-- and
why make it the default preference? And then, why even enable
users to turn it off?
[Robert] It's a
preference - you decide.
>>It seems to be the equivalent of having a
"break my scene" button.
[Robert] Nope, thats
ChldComp.
>>If you have constraints between reference models with
prefixes "on," then switch to prefixes "off," constraints
break.
[Robert] I didn't see that
here;
Preference ON
Made a model, exported
it
Got a new
scene
Imported model as
ref
Constrained to another
object
Saved scene
Turned Pref
OFF
Opened scene (no more
prefix on ref model)
Constraint still
works
>>Likewise, if you have a clip that constrains one object
to another, and you try to use it in a scene where your models are
referenced with the prefix option "on," they won't work-- ostensibly
because your constraint isn't referencing an object named
"referenced_whatever."
[Robert] I don't believe
that's how the scene graph works internally -a Soft engineer could
clarify.
Also, not sure if you
really mean clip as in you stored the constraint as a clip in the
mixer (and example above suggests other wise
>>It creates a situation where someone working on a box
with one little hidden check box switched to prefixes "off" can do a
load of work that is unusable on boxes that are set to default
preferences.
[Robert] In my experience
I've never seen it changed - and that's a lot shots with a lot of
people
>> Does this mean if you are working with ref models that
you have to remember to check this setting every time you sit down at
a new box?
[Robert] Not necssarily.
Most people implement a StartUp check (we do it here for frame rates,
output formats etc). It would take 5 mins to add that to
it.
>>Could someone explain why this check box exists and what
it is good for?
[Robert] It's a preference
- depends what you prefer.
>>And how do you convert a scene where constraints
were set "without" prefixes into one "with"
prefixes?
[Robert] Again, I
don't think it gets broken as you describe (in fact I tested it again)
so it really is just a case of changing the preference to whatever you
want.
>>Thanks,
>>Mike
>>p.s. if you're
going to state the obvious and tell me I shouldn't use ref-models, or
that it's the artist's fault for having the preference checked off,
don't bother replying to this.
[Robert] We use
reference models for so many things - our entire pipeline would change
without
them.
|
