Re: [Plib-users] Need advices to use Plib for a Roam algo

[Maltez <ma...@no...>]

> I'm not sure - that's why I asked!  I suppose you'd need to store a LIST
of
> states inside each node and to pick which set of states to use depending
> on the ssgContext that's set when your node is called.

Oh well, i didn't think about multiple root nodes for the graph, one for
each ssgContext.
Is this not a better choice to manage graphic or geometry states depending
on the camera ?

> Well, it's hard not to allow discontinuous motion...pretty much every
> application does that sooner or later.  But even if the camera motion
> is "smooth", when you are culled from the field of view - then when you
> come back into the field of view, the camera may have moved twenty miles
> and be looking at the terrain from the opposite direction.

Hmm, that will hapen only if the terrain engine is doing some kind of
pre-load or pre-computing with some predictive assumption of the camera
motion. My algo is far from that. But one day...

> Well, I thought your intention was to put this ROAM stuff *into* SSG.
That
> would be "A Good Thing" for the community - so if you are doing this as
> OpenSourced code then it would be good to put it into SSG rather than as
> a separate package.
>
> That's your call though.
>
Sorry it's not my current intention. When i feel confident and the code more
ready, i will think about that.
For now i just want to make the good choice in using and sub-classing SSG.

Maltez