, April 13, 2007 7:18 PM
Subject: Re: [osg-users] obscure state bug
If users want AlphaFunc on by default for the opaque bin then they can
simply attached an osg::AlphaFunc to the topmost StateSet in the scene
graph and get back the old functionality.
Are we certain that this will work? I.e
If users want AlphaFunc on by default for the opaque bin then they can
simply attached an osg::AlphaFunc to the topmost StateSet in the scene
graph and get back the old functionality.
Are we certain that this will work? I.e., that it will remain turned on
in the course of the traversal etc? I
On 4/13/07, Marc Bernatchez [EMAIL PROTECTED] wrote:
If users want AlphaFunc on by default for the opaque bin then they can
simply attached an osg::AlphaFunc to the topmost StateSet in the scene
graph and get back the old functionality.
Are we certain that this will work? I
There are no
Hi Robert,
Unless we have alpha blending we do not need to sort objects from back
to front hence we can save some performance by not putting such objects
to the transparent bin. Lets say we have a few hundred trees which are
rendered with alpha test but not alpha blending. Putting them to the
Hi Tugkan,
If users want AlphaFunc on by default for the opaque bin then they can
simply attached an osg::AlphaFunc to the topmost StateSet in the scene
graph and get back the old functionality.
Robert.
On 4/12/07, Tugkan Calapoglu [EMAIL PROTECTED] wrote:
Hi Robert,
Unless we have alpha
: Thursday, April 12, 2007 10:40 AM
Subject: Re: [osg-users] obscure state bug
Hi Marc,
This isn't a bug, rather it looked like it was working before because
the problem was masked out, quite literally. Originally the OSG set
turned on glAlphaFunc (osg::AlphaFunc) for both transparent and opaque
Bad timing, I just saw the answers for my questions
- Original Message -
From: Wojciech Lewandowski [EMAIL PROTECTED]
To: osg users [EMAIL PROTECTED]
Sent: Thursday, April 12, 2007 12:09 PM
Subject: Re: [osg-users] obscure state bug
I will join this discussion because it looks
Robert Osfield wrote:
Hi Tugkan,
If users want AlphaFunc on by default for the opaque bin then they can
simply attached an osg::AlphaFunc to the topmost StateSet in the scene
graph and get back the old functionality.
Robert.
I misunderstood the change then. I thought that OSG prevents
Hi Robert,
Here is what I tried in the code:
osg::AlphaFunc *TurnOnAlphaFuncbyDefault = new osg::AlphaFunc();
osg::StateSet *NewStateSet = SceneGraphRoot-getOrCreateStateSet();
NewStateSet-setAttribute(TurnOnAlphaFuncbyDefault,
osg::StateAttribute::ON);
I still see the artifacts. Does the
Hi Marc,
You'll need to set the AlphaFunc's parameters. i.e.
osg::AlphaFunc* alphafunc = new osg::AlphaFunc;
alphafunc-setFunction(osg::AlphaFunc::GREATER,0.0f);
Robert.
On 4/12/07, Marc Bernatchez [EMAIL PROTECTED] wrote:
Hi Robert,
Here is what I tried in the code:
Any progress on this bug? I don't know if it is the bug I'm seeing but
it roughly started when I went to OSG 1.2 and appears to only show up
with OpenFlight models. I noticed some strange transparency bugs as I
went 1.2. Some objects that were totally transparent got half visible
while other
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
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 osg-users@openscenegraph.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii; format
Hi Frashid,
On 3/14/07, Farshid Lashkari [EMAIL PROTECTED] wrote:
Hi Paul,
I'm pretty sure it's a render bin problem. I did some debugging and
discovered that each geometry is being placed into a different
RenderBin, although their bin number and names are the same during the
cull traversal.
Hi Robert,
On 3/14/07, Robert Osfield [EMAIL PROTECTED] wrote:
Normally they will go into the same RenderBin, but if you nest a
subgraph within a RenderBin then all internal RenderBin references
within this RenderBin will be nested as well using new RenderBin's. I
hope that makes sense,
: Tugkan Calapoglu [EMAIL PROTECTED]
Subject: Re: [osg-users] obscure state bug
To: osg users osg-users@openscenegraph.net
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
Hi Terry,
On 3/13/07, Terry Welsh [EMAIL PROTECTED] wrote:
Any progress on this bug or should I look for a workaround? I can't
for the life of me figure out the real cause of problem, and I think
it's going to get in my way pretty badly soon
I spent a couple of hours recreating and
Hi Terry,
On 2/22/07, Terry Welsh [EMAIL PROTECTED] 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
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
+0100
From: Tugkan Calapoglu [EMAIL PROTECTED]
Subject: Re: [osg-users] obscure state bug
To: osg users osg-users@openscenegraph.net
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
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
21 matches
Mail list logo
