Hello Michael,
On 05/11/2011 10:10 AM, Michael Raab wrote:
> I'm trying to write several smaller parts of my scene graph in one OSB file.
> Therefore I created to dummy OpenSG classes named MeshCollection and
> MeshDesc. The Meshcollection inherits Node to form to root of my OSB file
> pointing to several MeshDesc instances. MeshDesc simply holds an mesh
> identifier (std::string) and a pointer to the node of one single (sub graph).
> When reading a so written OSB file, the loader crashes with bad alloc
> exception, but we are far away from any memory limitations.
> I'm attaching the two fcd files I have used. Is there anything I need to
> consider. Any ideas?
hmm, the fcd files look ok to me. Deriving from Node may be a bit
problematic (it's not normally done and code may not be prepared to deal
with this possibility), but I don't have a concrete idea where the bad
alloc would come into play.
You could make MeshCollection an attachment with a MFString and
MFNodePtr and just attach that to a Node (so you can write it to OSB).
That would be a more usual use case for the OSB IO and may avoid
problems with deriving from Node - assuming that is the problem.
Sorry, I'd need something I can debug to get a better idea where the
problem is.
Cheers,
Carsten
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
