Hi,
I had Emailed a while back about a problem we have when loading 3DS
files. The problem seems to remain present in the OSG 1.2 release. I am
still investigating to determine if the problem is caused on my side or
if it is really something that relates to OSG. Here are the observations
so far:
- Whenever I load a 3DS file (windows platform, OSG 1.2 and VRJuggler
2.0), once the render window appears, it remains black and the task
manager reports that RAM usage keeps increasing (memory leak?) for as
long as I let the application run.
- The application can load FLT files without any problems (same geometry
as the 3DS).
- The problem initially showed on OSG releases past 1.0 (1.1 and 1.2
cause the problem in my app.)
- osgviewer (osg 1.2) does load the same 3DS file (yes, it indeed points
to my code but I am still keeping the final vote pending until I can
find what is going on)
The lib3ds module did change a bit from 1.0 to later versions, but not
significantly. I saw a few changes like removing the long attribute on
some variables as well as the addition of a big-endian related function.
Since it works with osgviewer, it more points to a memory corruption /
memory overrun condition. A change on the OSG code could have pushed
some memory address space just so that it now falls where a bad pointer
is corrupting memory. I hope I am wrong here... This could be nasty to
track down.
Did anyone else witness such behaviors with 3DS files since OSG 1.1 and
up? If you have any suggestions on what to try and check first, please
drop me a line.
Thanks
--
=====================================
Marc Bernatchez
Candidat au Ph.D.
Ecole Polytechnique de Montreal
Montreal, QC, CANADA
=====================================
Virtual Reality web site, VResources:
http://vresources.org
=====================================
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
