Hi,
thank you for your reply!
Actually, culling was not the reason but my understanding of how the LOD node
works. I thought that the LOD node applies the distance calculation of the LOD
to each child's bounding sphere center. But it seems to be that the distance
calculation is done for the ce
Hi Hartwig,
Given the odd behavior, and the fact that the LOD implementation doesn't
have any code that is sensitive to number of children, I would suspect
something like small feature culling introducing issues.
Small feature culling doesn't require any nodes to be inserted in the scene
graph, i
Hi,
I have two LOD nodes. One LOD node has one child node the other one has - for
example - 1000 children. All children of both nodes have the same range
settings (0 - maxValue).
The single child of the LOD node is shown on the scene. Children in the
vicinity of this single child - but part of
On 4/3/2011 10:59 AM, Martin Haffner wrote:
> I think I know what you mean. You said a LOD node is meant to be used with
> roughly the same geometry and I feared it would be a problem to add the
> geometry of a road segment and all the trees under the same node since the
> tree bounding spheres
I think I know what you mean. You said a LOD node is meant to be used with
roughly the same geometry and I feared it would be a problem to add the
geometry of a road segment and all the trees under the same node since the tree
bounding spheres differ a lot from the road segment bounding sphere.
On 4/3/2011 10:25 AM, Martin Haffner wrote:
> I see. One more little question: I have a lot of objects (for example trees)
> along a road segment.
> Sure, I could give each tree an LOD node (one LOD node for each tree) but I
> guess it would be smarter if I did use the same LOD node for the segme
I see. One more little question: I have a lot of objects (for example trees)
along a road segment.
Sure, I could give each tree an LOD node (one LOD node for each tree) but I
guess it would be smarter if I did use the same LOD node for the segment. As I
said I want to make a LOD node for each r
On 4/3/2011 9:38 AM, Martin Haffner wrote:
> The question I am asking this: I have a long road (lets say 3km) and I want
> to divide the road in segments (say 200m per segment). Now I want to use LOD
> for the segments. For example if the camera is close to segment 2, segment 2
> should be rende
The question I am asking this: I have a long road (lets say 3km) and I want to
divide the road in segments (say 200m per segment). Now I want to use LOD for
the segments. For example if the camera is close to segment 2, segment 2 should
be rendered with high poly count. The adjacent segments 1 a
On 4/3/2011 9:27 AM, Martin Haffner wrote:
> Thanks for your fast reply!
> Ok, lets say I have 2 matrix transform nodes. One makes a huge translate to
> the right (x axis) and the other a huge translation fo the left. Each matrix
> transform node has one geode as a child, which renders a tree.
>
Thanks for your fast reply!
Ok, lets say I have 2 matrix transform nodes. One makes a huge translate to the
right (x axis) and the other a huge translation fo the left. Each matrix
transform node has one geode as a child, which renders a tree.
If I add these 2 matrix transform to a LOD node (at
On 4/3/2011 8:36 AM, Martin Haffner wrote:
> The values 0.0f, 5.0f and FLT_MAX are all camera distances, but I wonder from
> which reference point? Are these values the distance from the camera to the
> bounding sphere center of the individual geodes? Or are these the distances
> from the camera
Hello,
I have a question about the LOD node:
Lets say I have 2 Geods and add them to a LOD node:
Code:
osg :: ref_ptr < osg :: LOD > lod = new osg :: LOD ;
lod->addChild(geode1, 0.0f, 5.0 f);
lod->addChild(geode2, 5.0f, FLT_MAX );
The values 0.0f, 5.0f and FLT_MAX are all camera distances, bu
13 matches
Mail list logo
