Hi Nerazzuri?,
I suspect that your code to find the switch node is not working.
As a quick and dirty example try saving a pointer to the switch node as a
global and in your main loop try turning it on and off.
Code:
int n = 0
while( !viewer.done() )
{
annotationsSwitch-
Hello,
Q: Can I force the database pager to load a scene? ie. when I switch a
sub-graph "on" I need the data to be ready. It takes about 100 ms to completely
load and I have ~333 ms between switch nodes so I have time but need to avoid
seeing the transitions from low->mid->high resolution.
Hi,
I am trying to use an osg::Switch node in my scene to toggle on/off certain
sub-graphs.
the way I have my subgraph set up is:
I have a geode (textGeode) which is placed under a switch node and the switch
is then place below an LOD node.
Code:
annotationsSwitch->addChild(textGeode, tru
On 9/17/2011 7:53 AM, Paul Martz wrote:
The
Drawables associated with A1 render first.
Second, the Drawables associated with B2 and B3 render grouped by
state.
Third, the Drawables associated with B2 and B3 render grouped by
state.
On 9/17/2011 7:42 AM, Aurelien Albert wrote:
Hi,
I want to understand the render order of the different objects in an OSG scene.
For example, with this scene :
[Image: http://img4.hostingpics.net/thumbs/mini_829034graph.png ]
Assuming A1, B2, B3, C2, and C3 are all Geodes, then their Drawabl
Hi,
I want to understand the render order of the different objects in an OSG scene.
For example, with this scene :
[Image: http://img4.hostingpics.net/thumbs/mini_829034graph.png ]
Is it true or false ?
1. Root is rendered before all other
2. A is rendered before A1
2. B is rendere
6 matches
Mail list logo