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 breaking the model into parts, this is only really useful if you implement a paged database, as loading them all separately without paging will just result in all the models being loaded at start up any way. As for limits, well this totally depends upon your hardware, the OSG itself doesn't have any predefined limits. Robert. On Thu, Jun 19, 2008 at 3:57 PM, Kiff Loh <[EMAIL PROTECTED]> wrote: > 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 osgviewer, > the same thing happen. I'm using osg 1.2, but I guess 2.4 will have the same > problem. > > 1) Is there a maximum size (eg ive) that can be loaded into osg? Could the > limit be on my graphics card memory or system RAM? > 2) Is there advantage to have 1 big ive, or a few smaller ive files? > 3) Is the limit more on textures size, or number of triangles? > > Kiff > > ________________________________ > Enrich your blog with Windows Live Writer. Windows Live Writer > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
