Thanks Tugkan; that's good to know.  Since it's a known problem I
guess I'll just wait a while and see if Robert patches it.  I really
don't know what the best solution is.

Robert, yes, that change I mentioned is a complete hack.  But it does
make the problem go away.  If you wanted it to not be a hack, you
could probably also replace line 462 with state.popAllStateSets();
However, I think that essentially takes you back to version 1.46.  The
way you're doing things now looks smarter and faster, so I wish I knew
why it didn't work.
- Terry

Message: 11
Date: Fri, 23 Feb 2007 09:47:00 +0100
From: Tugkan Calapoglu <[EMAIL PROTECTED]>
Subject: Re: [osg-users] obscure state bug
To: osg users <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii; format=flowed

Terry Welsh wrote:
> I have a really weird bug that shows up in one of my apps.  Sometimes
> objects get the wrong StateSet applied to them.  I have not been able
> to produce a simple enough test case to send in yet, but I wanted to
> know if anyone else has seen this problem in the last month.
>
> The problem was introduced when RenderBin.cpp went from v1.46 to
> v1.47.  The problem goes away if I add state.popAllStateSets(); at
> line 386.

Hi Terry,

Just to save you some work:
I observed the same bug and created an .osg file to reproduce it. Robert
already has it.

tugkan
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to