But base on my experience, most of the datasets created have higher
weightage on the texture side.
You can do a simple experiment, just take note of the orginal flt file size,
before and after it is being
converted to ive format consisting of the textures. Take note of the
increase in
Hi, I'm in the midst of converting a very large database of openflight files
and textures into ive to be loaded in osgviewer. It seems that when my ive
files are close to 1 Gb of size, my osgconv will crash from a windows error.
When I break my flt files into a few ive files and load them with
Hi Kiff,
There is a good chance that if you model is too big to fit in memory
then you are going to have problems. The best you can do is compress
your textures, and possible swtich off display lists. To compress
textures try:
osgconv --compressed-dxt1 mymodel.flt mymodel.ive
As for
Dear Kiff,
This is my answers to your question
1) For non paging terrain, the limit will be on the RAM. You can do a simple
experiment, just launch the task manager that monitor the physical memory
available. You will see the available physical memory decreases as you load the
database. More
4 matches
Mail list logo
