[osg-users] Problem with OpenSceneGraph.xcodeproj in 2.3.9 (and earlier)

Trying to do a Clean all targets in the OpenSceneGraph Xcode project results in some undefined build variable errors on the target SDLdependentStuff. Using Get Info to examine SDLdependentStuff causes Xcode to crash. I first found this on 2.3.8 and have just checked a clean copy of 2.3.9 and it is

[osg-users] Clearing RenderLeaf ref_ptrs

Hi Robert -- I recently discovered that if I remove a subgraph from the scene graph during the update traversal, most parts of that subgraph clean up (ref count goes to zero and memory is deallocated), but not everything. In particular, RenderLeafs in the OSG backend appear to maintain ref_ptrs

Re: [osg-users] Problem with OpenSceneGraph.xcodeproj in 2.3.9 (and earlier)

Roger James schrieb: Trying to do a Clean all targets in the OpenSceneGraph Xcode project results in some undefined build variable errors on the target SDLdependentStuff. Using Get Info to examine SDLdependentStuff causes Xcode to crash. I first found this on 2.3.8 and have just checked a

Re: [osg-users] Clearing RenderLeaf ref_ptrs

Hi Paul, The rendering backend - the StageGraph and RenderLeaf objects both used ref_ptr to references to StateSet and Drawables respectively. These are used to ensure when osgViewer is running DrawThreadPerContext and CullThreadPerCameraDrawThreadPerContext the objects don't get deleted by the

Re: [osg-users] Problem with OpenSceneGraph.xcodeproj in 2.3.9 (and earlier)

Hi Roger, On Sat, Apr 19, 2008 at 1:54 PM, Roger James [EMAIL PROTECTED] wrote: Trying to do a Clean all targets in the OpenSceneGraph Xcode project results in some undefined build variable errors on the target SDLdependentStuff. Using Get Info to examine SDLdependentStuff causes Xcode to

Re: [osg-users] Clearing RenderLeaf ref_ptrs

Thanks, Robert. On second thought, forcing OSG to stop threading and flush its backend structures would certainly cause a frame stall; handling this some other way would produce better results. For now, waiting a few frames to unload the DLL is a good solution. -Paul -Original