[osg-users] --tile-terrain-size in VPB
robert.osfield at gmail.com
Mon Mar 23 10:06:19 PDT 2009
Jikes, some days I regret making osgdem quite so flexible...
A 1024x1204 grid weights in at million vertices, and near two million
triangles. Normally graphics cards should be able to handle this, but... it
would seem that your's doesn't, perhaps it just doesn't have the memory to
handle such a big geometry. The other chance might be that numerical
precision is becoming an issue, although I'd be surprised by this one.
I really would very strongly recommend that you stick to defaults unless you
really know what you are doing, the defaults are chosen for a good
performance and scalability.
2009/3/23 Martins Innus <minnus at ccr.buffalo.edu>
> I'm using the --tile-image-size and --tile-terrain-size options to
> tweak the generation of the dataset. The image option works great, but when
> I try to use the terrain option I get the results attached.
> If I zoom in, it seems like a lot of overlapping geometry like the
> y-coordinate is not being updated properly, but I dug through the code and
> could see any obvious causes.
> I'm using the following command-line:
> osgdem --tile-image-size 4096 --tile-terrain-size 1024 -t ../input_ims/ -d
> ../input_terrain/ -e 1065536 1043840 8192 8192 -o output/vpb_out.ive
> I even added --no-terrain-simplification to see if that was the problem,
> but no help there.
> I'm not using the --TERRAIN option, since I need to post-process the
> geometry using an existing tool.
> osg-users mailing list
> osg-users at lists.openscenegraph.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the osg-users