Sure, I completely agree that this is quite useful for effects in general.
-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of peter_b
Posted At: Monday, November 14, 2005 11:26 AM
Posted To: xsi
Conversation: Re[2]: operators and construction mode
Subject: Re: Re[2]: operators and construction mode
consider having a deformed surface to create an ocean, selecting the peaks with a bounding volume and using those to generate particles, and have this all update dynamically.
its just impossible in XSI. and it is something very common to wish for.
(ok you can by mapping a vertical gradient as a texture map)
or rule based selection, like concave or convex areas, dense or less dense areas, angle based edges....
would be cool to have a "selection operator" in the stack, where you could change the rule, treshold, method,...
on the fly, have the selection updated, and the modeling operator that happens next reflect that change.
you're right about the micro-operations, you dont want that kind of flexibility there.
> Yes, such spatial-based clusters could help. It can work well for
operations of relatively large scale (ex: bulge this part, delete that part), however it won't be good enough to keep track of micro operations (collapse that edge, crease that vertex...), which is the way most people model, and it would create an important performance overhead. Still, I agree it can be quite useful for type of some work such as rigging templates (it kind of falls in the GATOR land).
>
> JCG
>
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf
Of Graham D Clark
> Posted At: Sunday, November 13, 2005 3:41 PM Posted To: xsi
> Conversation: Re[2]: operators and construction mode
> Subject: Re: Re[2]: operators and construction mode
>
>
> On 11/9/05, Jérôme Couture-Gagnon <jcgagnon(at)softimage.com> wrote:
> > Hi Frank,
> >
> > We decided to restrict operators that modify the topology to the
modeling construction mode, to avoid that people hit various problems in the
long run. The fact that we know all modeling ops are in the modeling region
actually permits some of the magic of the construction modes...
>
> [g] Feels like more of a limit than a permit. Instead of static clusters
of fixed component collections that XSIs ops seem to use, Flexible component
collection methods, like by bounding volume etc I think would allow many ops
to remain functional with changes made.
> 2 hopeful cents
> Graham
> -------------------------------------------
> CG Supervisor, Omation
> http://www.byrecruit.net
> http://www.grahamdclark.com
>
> >
> > However I agree that it could make sense that the slice is in the
animation region, but the current rules won't allow it. Still, here are two
things that can help you:
> >
> > 1) If the slice in the modeling stack of your mesh, you can still modify
the mesh before the slice by first doing "disable from here" on the slice
operator. Actually, to avoid problems, you should actually create all the
clusters that will be used in your animation stack (ex: to be connected to a
deform) while you have the slice disabled, same for the polygon cluster used
for hair generation (if you have one). Otherwise, since the slice changes
the indices of the components, the clusters created after the slice will
change randomly.
>
> ---
> 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
>
---
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
