Re: [osg-users] how to hide/unhide an object picked
Hi Xinguo, As well as node mask you can also use an osg::Switch node above the subgraph you want to toggle on/off. Robert. On 8/6/07, Xinguo Liu [EMAIL PROTECTED] wrote: Hi, I currently hide an object by removing the corresponding node from the scene graph. Is there any simple way, like -hide(), or -disable()? Thanks! Xinguo PS: Thanks for answers to How to change _usage of BufferObject ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] How to set flag COMPILE_GLOBJECTS_AT_INIT for osgViewer?
How to set flag COMPILE_GLOBJECTS_AT_INIT for osgViewer? ...sceneView-setDefaults (COMPILE_GLOBJECTS_AT_INIT); In osgViewer there is no property getSceneView: ( ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] Small pb with osgviewerWX
SVN from this morning, wxWidgets 2.7.0-1 gtk. Run osgviewerWX (or also osgviewerWXd) and close the window with the right X button. The application exits with the following warning: Warning: deleting still referenced object 0x81b2be8 of type 'PN3osg10ReferencedE' the final reference count was 1, memory corruption possible. The strange thing is that running osgviewerWXd under valgrind reveals problems inside the Qt library (see below)! Warning: deleting still referenced object 0x781e408 of type 'PN3osg10ReferencedE' the final reference count was 1, memory corruption possible. ==10434== ==10434== Invalid read of size 4 ==10434==at 0x6738746: QApplication::notify(QObject*, QEvent*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x6799DB2: QObject::removeChild(QObject*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x679936E: QObject::~QObject() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x6754A0A: QFontCache::~QFontCache() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x674F949: (within /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x51D0203: exit (in /lib/tls/libc-2.3.5.so) ==10434==by 0x51BAEA7: (below main) (in /lib/tls/libc-2.3.5.so) ==10434== Address 0x6DDF314 is 4 bytes inside a block of size 8 free'd ==10434==at 0x401C489: operator delete(void*) (vg_replace_malloc.c:244) ==10434==by 0x673F31D: QPtrListQPostEvent::deleteItem(void*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x6A5392C: QGList::clear() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x673F81C: QPostEventList::~QPostEventList() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x6737B09: (within /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==10434==by 0x51D0203: exit (in /lib/tls/libc-2.3.5.so) ==10434==by 0x51BAEA7: (below main) (in /lib/tls/libc-2.3.5.so) Strange... Anyway, setting the notification level show a problem with GraphicsContext::unregisterGraphicsContext Viewer::~Viewer():: start destructor getThreads = 0 close(1)0x81b4af8 Releasing GL objects for Camera=0x81c4d50 _state=0x81c4968 Closing still viable window 0 _state-getContextID()=0 Doing Flush Done Flush 100 decrementUsageCount()0 GraphicsContext::decrementContextIDUsageCount(0) to 0 Viewer::~Viewer() end destrcutor getThreads = 0 Destructing osg::View Done destructing osg::View close(0)0x81b4af8 Releasing GL objects for Camera=0x81c4d50 _state=0 GraphicsContext::unregisterGraphicsContext 0x81b4af8 Warning: deleting still referenced object 0x81b4af8 of type 'PN3osg10ReferencedE' the final reference count was 1, memory corruption possible. Closing DynamicLibrary osgdb_osg.so Closing DynamicLibrary osgdb_rgb.so ~RegisterWindowingSystemInterfaceProxy() GraphicsContext::setWindowingSystemInterface() 00x403e0e18 Hope could be useful mario -- Ing. Mario Valle Visualization Group | http://www.cscs.ch/~mvalle Swiss National Supercomputing Centre (CSCS) | Tel: +41 (91) 610.82.60 v. Cantonale Galleria 2, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] How to set flag COMPILE_GLOBJECTS_AT_INIT for osgViewer?
HI, osgViewer by defaults does a compile traversal so there is no need to switch it on. For future reference if you absolutely need to get the SceneView that is used under the hood then you'll need to use SVN or 2.1.4 onwards at it now assigned a osgViewer::Renderer to each Camera, and the Renderer has two SceneView, two because of double buffering. Robert. On 8/6/07, GMD GammerMaxyandex.ru [EMAIL PROTECTED] wrote: How to set flag COMPILE_GLOBJECTS_AT_INIT for osgViewer? ...sceneView-setDefaults (COMPILE_GLOBJECTS_AT_INIT); In osgViewer there is no property getSceneView: ( ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] multi-threads
Hi, I need to up to date the scene of graph through several threads, therefore he would like to know if the OSG implements some type of synchronization of threads. Where I can find examples? Thanks, Ronald S. Serrão. São Luís - Brazil. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] invalid conversion from `int*' to `socklen_t*'
On 8/6/07, Martin Spott [EMAIL PROTECTED] wrote: Martin Spott wrote: just wanted to let you know that I'm getting a compile error with current SVN on FreeBSD: Ok, the current state of 2.1.4 compiles fore me on FreeBSD. For this we must thank John Shue :-) ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] multi-threads
Hi Ronald, On 8/6/07, ronaldss [EMAIL PROTECTED] wrote: I need to up to date the scene of graph through several threads, therefore he would like to know if the OSG implements some type of synchronization of threads. Where I can find examples? The OSG is designed to support single threaded update, and multi-threaded rendering. It does not support multi-threaded update. Supporting general multi-threaded update would requires mutexing of most operations on the scene graph, this would utterly destroy performance. It'd also make it a really awkward to write, extended and use. All in all it would be a pretty crappy scene graph, all for a type of usage that is very specialized. So.. where does leave you... we'll not totally high and dry, one can implement high level control over access to the scene graph, this is non longer a scene graph control though, rather an application centric control. What you'll need to do is have a single mutex that each thread acquires before it can do any read/write ops on the scene graph. The main frame loop will have to use this mutex too, so that when it runs the frame() it aquires the lock so that no one else can modifiy it which its doing its update and rendering traversals. Now if you write you code carefully, acquire the lock before writing, and release it, then you should be able to get multi-thread update working safely. Performance won't be ideal, but it at least should work. Another way to tackle it is rather than using a mutex and let each thread acquire it and the modify the scene graph itself, is to do all the operations via an subclassing from osg::Operation, then placing these operations into a osg::OperationQueue that gets flushed on each new frame. The osg::OperationQueue itself can be read/written to multi-threaded so can happily handle the usage model you are looking for. The upside is that performance will be good, no long waits to acquire mutexes, the downside is that the operations are no longer synchronous w.r.t calling threads. Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] DISPLAY
Hi, I'm running an example remotely over ssh. I did ssh -X, and verified that DISPLAY is set. However, when I run, I get: 'unable to open display :0.0' Ideas? ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] compiling on Mac OS X Leopard 64 bit
We have someone trying to build OSG on 64 bit Leopard. He has run into a couple of things: GraphicsWindowCarbon.cpp won't compile. Is anyone doing a Cocoa version? We aren't looking for one, but would like to not have a build issue, and may be able to help out. The quicktime plugin is conflicting with what is on the machine, if I understand it correctly. Anybody working on an update to this? Here's a summary from the guy working on it: === On Leopard 32-bit, all of the APIs are there, but they generate deprecated function compiler warnings. On 64-bit, they generate compiler errors because they're just plain not available. === Is there a way to not compile the quicktime plugin? If we could specify to CMake or somewhere either a list of plugins to not compile, or a list to compile, we could just avoid the quicktime plugin for now. thanks andy ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] invalid conversion from `int*' to `socklen_t*'
Robert Osfield wrote: On 8/6/07, Martin Spott [EMAIL PROTECTED] wrote: Martin Spott wrote: just wanted to let you know that I'm getting a compile error with current SVN on FreeBSD: Ok, the current state of 2.1.4 compiles fore me on FreeBSD. For this we must thank John Shue :-) Herewith I do so ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] osgTerrain Tutorial
Hi, I'm new to OSG and I have a bit of problem wrapping my head around how to use osgTerrain and paged databases in general. I looked at the Quick Start Guide and there's no info. Is there an OSS app I can download to learn how to use osgTerrain? Thanks - Nick - ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] compiling on Mac OS X Leopard 64 bit
Can't say much about Leopard due to the NDA. But there has been public traffic about Carbon and 64-bit. The summary is that there will be no 64-bit path for Carbon. That means GraphicsWindowCarbon will not work and a Cocoa version of GraphicsWindow is the way to go for 64-bit. (I've warned people that this day would come.) There is currently no Cocoa version. You are free to write it. I did write an example called osgviewerCocoa. Basically, the example needs to be turned inside-out for GraphicsWindowCocoa. This might imply certain things to you about QuickTime (and the plugin). What's not under NDA is that QuickTimeKit (QTKit) in Tiger is a ground up reimplementation of the QuickTime SDK which looks a heck of a lot more 64-bit (and also endian) clean than the old QuickTime SDK. So for now, you want to skip building the QuickTime plugin. You can edit your CMakeLists.txt in the src/osgPlugins directory and remove the entry that handles that plugin. I have been privately discussing with somebody to create two new plugins (one for QTKit, the other for ImageIO). But my employment situation has drastically changed recently so I can't make any promises right now. -Eric On 8/6/07, Andy Skinner [EMAIL PROTECTED] wrote: We have someone trying to build OSG on 64 bit Leopard. He has run into a couple of things: GraphicsWindowCarbon.cpp won't compile. Is anyone doing a Cocoa version? We aren't looking for one, but would like to not have a build issue, and may be able to help out. The quicktime plugin is conflicting with what is on the machine, if I understand it correctly. Anybody working on an update to this? Here's a summary from the guy working on it: === On Leopard 32-bit, all of the APIs are there, but they generate deprecated function compiler warnings. On 64-bit, they generate compiler errors because they're just plain not available. === Is there a way to not compile the quicktime plugin? If we could specify to CMake or somewhere either a list of plugins to not compile, or a list to compile, we could just avoid the quicktime plugin for now. thanks andy ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
