Re: [osg-users] The OSG SIGGRAPH BOF train is leaving the station
hi John, I think robert will not come to SIGGRAPH this year! Regards zhuwan 03,24,2015 在2015-3-24 5:18:30，John Richardson richa...@spawar.navy.mil 写道: -原始邮件- 发件人: John Richardson richa...@spawar.navy.mil 发送时间: 2015-3-24 5:18:30 收件人: osg-users@lists.openscenegraph.org 主题: [osg-users] The OSG SIGGRAPH BOF train is leaving the station AND WILL ARRIVE AT SIGGRAPH… Birds of a Feather Session Title: OpenScenegraph BOF Date: Wednesday August 12 Location: Los Angeles Convention Center Time: 10:00 - 11:00 am Note: and yes, I still am on the hook for pictures of past BOF’s and materials…. EXCUSE INSERT EXCUSE HERE /EXCUSE EXCUSE, the only XML tag you will ever need. Last note: TRIP OVER YOURSELF RUSHING TO MAKE OSG BOF PRESENTATIONS / TRIP OVER YOURSELF RUSHING TO MAKE OSG BOF PRESENTATIONS TRIP OVER YOURSELF RUSHING TO MAKE OSG BOF PRESENTATIONS. Not the only necessary and sufficient XML tag, but occasionally useful as a supplemental and vicarious standards based enumeration… John___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] Android ART
Hi, Does OSG 3.2.1 support Android ART? Android Lollipop is around the corner and it only supports ART now :( Thank you! Cheers, Colin -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=63189#63189 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Register object wrapper for osg::Geode
Hi John and Rui, Well spotted. I am not sure what to do about this one. I think fixing the REGISTER_OBJECT_WRAPPER to include osg::Group may well break the parsing of .osgb files as the current serializers aren't versioned for the associates list. Having two separate wrappers might be the way forward. Or adding some for of versioning for the associate list. Any thoughts Rui? Cheers, Robert. On 24 March 2015 at 08:33, John Ivar Haugland john.haugl...@gmail.com wrote: Hi, I notice that osg::Geode now inherits osg::Group instead of osg::Node. However, in the corresponsing serializer osg::Group is not mentioned in REGISTER_OBJECT_WRAPPER( Geode, new osg::Geode, osg::Geode, osg::Object osg::Node osg::Geode ) Is this correct ? or should it be changed to REGISTER_OBJECT_WRAPPER( Geode, new osg::Geode, osg::Geode, osg::Object osg::Node osg::Group osg::Geode ) Kind regards John Ivar Haugland ___ 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
Re: [osg-users] Register object wrapper for osg::Geode
Hi Robert and John,
As Geode and Group serializers both contain only one user macro for storing
children nodes, I think we can simply rewrite the Geode serializer like this:
REGISTER_OBJECT_WRAPPER( Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Node osg::Geode )
{
ADD_USER_SERIALIZER( Drawables ); // _drawables
{
UPDATE_TO_VERSION_SCOPED( 115 )
REMOVE_SERIALIZER( Drawables );
ADD_USER_SERIALIZER( Children ); // _children
}
}
Similar work should be done on osg::Drawable serializers as well to support
some important attributes like NodeMask and CullingActive. This is the fastest
way to update serializers and keep back-compatibility in my opinion, without
changes to the core modules.
An alternative way is to have a new REGISTER_VERSIONED_OBJECT_WRAPPER macro to
submit a new ObjectWrapper to the registry, in which only wrapper with newer
version number can be accepted, such like:
REGISTER_VERSIONED_OBJECT_WRAPPER( 115, Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Group osg::Geode )
{
...
}
The second way might be easier and more readable for further use.
Cheers,
Wang Rui
-- Original --
From: Robert Osfield;robert.osfi...@gmail.com;
Date: Tue, Mar 24, 2015 05:37 PM
To: OpenSceneGraph Usersosg-users@lists.openscenegraph.org; Wang
Ruiwangra...@gmail.com;
Subject: Re: [osg-users] Register object wrapper for osg::Geode
Hi John and Rui,
Well spotted. I am not sure what to do about this one. I think fixing the
REGISTER_OBJECT_WRAPPER to include osg::Group may well break the parsing of
.osgb files as the current serializers aren't versioned for the associates list.
Having two separate wrappers might be the way forward. Or adding some for of
versioning for the associate list.
Any thoughts Rui?
Cheers,
Robert.
On 24 March 2015 at 08:33, John Ivar Haugland john.haugl...@gmail.com wrote:
Hi,
I notice that osg::Geode now inherits osg::Group instead of osg::Node.
However, in the corresponsing serializer osg::Group is not mentioned in
REGISTER_OBJECT_WRAPPER( Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Node osg::Geode )
Is this correct ? or should it be changed to
REGISTER_OBJECT_WRAPPER( Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Node osg::Group osg::Geode )
Kind regards
John Ivar Haugland
___
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
Re: [osg-users] Register object wrapper for osg::Geode
HI Rui,
Thanks for your input. I think the version wrapper would be the best way
forward.
Robert.
On 24 March 2015 at 14:39, Wang Rui wangra...@gmail.com wrote:
Hi Robert and John,
As Geode and Group serializers both contain only one user macro for
storing children nodes, I think we can simply rewrite the Geode serializer
like this:
REGISTER_OBJECT_WRAPPER( Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Node osg::Geode )
{
ADD_USER_SERIALIZER( Drawables ); // _drawables
{
UPDATE_TO_VERSION_SCOPED( 115 )
REMOVE_SERIALIZER( Drawables );
ADD_USER_SERIALIZER( Children ); // _children
}
}
Similar work should be done on osg::Drawable serializers as well to
support some important attributes like NodeMask and CullingActive. This is
the fastest way to update serializers and keep back-compatibility in my
opinion, without changes to the core modules.
An alternative way is to have a new REGISTER_VERSIONED_OBJECT_WRAPPER
macro to submit a new ObjectWrapper to the registry, in which only wrapper
with newer version number can be accepted, such like:
REGISTER_VERSIONED_OBJECT_WRAPPER( 115, Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Group osg::Geode )
{
...
}
The second way might be easier and more readable for further use.
Cheers,
Wang Rui
-- Original --
*From: * Robert Osfield;robert.osfi...@gmail.com;
*Date: * Tue, Mar 24, 2015 05:37 PM
*To: * OpenSceneGraph Usersosg-users@lists.openscenegraph.org; Wang
Ruiwangra...@gmail.com;
*Subject: * Re: [osg-users] Register object wrapper for osg::Geode
Hi John and Rui,
Well spotted. I am not sure what to do about this one. I think fixing the
REGISTER_OBJECT_WRAPPER to include osg::Group may well break the parsing of
.osgb files as the current serializers aren't versioned for the associates
list.
Having two separate wrappers might be the way forward. Or adding some for
of versioning for the associate list.
Any thoughts Rui?
Cheers,
Robert.
On 24 March 2015 at 08:33, John Ivar Haugland john.haugl...@gmail.com
wrote:
Hi,
I notice that osg::Geode now inherits osg::Group instead of osg::Node.
However, in the corresponsing serializer osg::Group is not mentioned in
REGISTER_OBJECT_WRAPPER( Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Node osg::Geode )
Is this correct ? or should it be changed to
REGISTER_OBJECT_WRAPPER( Geode,
new osg::Geode,
osg::Geode,
osg::Object osg::Node osg::Group osg::Geode )
Kind regards
John Ivar Haugland
___
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] Render into a QQuickFramebufferObject (osg / osgEarth)
Hi, I'm trying to render a scene node in a QtQuickItem. For this I used the Qt example Scene Graph - Rendering FBOs as a base template: qtquick-scenegraph-textureinsgnode-fboinsgrenderer-cpp @ qt.io Additionally I found a Gists which does nearly the same thing I'm trying to achieve: gist:9bf4cec0aee18fc6e27b On construction I create an EmbeddedWindow and a Viewer, and setup my scene. Afterwards the createFramebufferObject is used to allocate the FBO and resize the EmbeddedViewer and the Viewport. Rendering is triggered with a frame() call inside the render function and the osg::Viewer is set up to run SingleThreaded. As long as I use/add a simple osg::Node to the scene, e.g. cow.osg, everything seems to work fine. As soon I start to change the CameraManipulator to osgEarth::Util::EarthManipulator and use a osgearth::MapNode instead, the first drawn frame is black, and changes only on re-sizing and recreating the FBO, but only once. Afterwards, the render function is called, but frame() seems to not render anything anymore. I suppose something gets messed up with the OpenGLContext or osgEarth does not work SingleThreaded, but I'm currently not able to understand the problem as a whole. I even tried to create a new shared context like rickyviking/qmlosg at github did, but could not get it to render a propre scene. Any help would be appreciated! Thank you! Cheers, Sascha p.s.: I've tried different other approaches in advance, where many of them seem to be outdated or lacking simple re-sizing functionality. My current implementation uses a QQuickItem which has a re-implemented QSGSimpleTextureNode which shares an FBO with an osg::Camera. But i cannot manage to resize the fbo texture ... p.p.s.: Sorry for not posting the links directly, but You must have 2 posts before you can post URL's/Links. ... -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=63192#63192 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Android ART
Thanks Jan, I swear I remember a while back (about 6 months ago) ppl were having trouble getting OSG to run on ART here on the forums, but I can no longer find that topic. Maybe I was just imagining it... -C -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=63195#63195 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Android ART
Hello, On Tue, Mar 24, 2015 at 2:34 PM, Colin Cochran co...@terminaleleven.com wrote: Hi, Does OSG 3.2.1 support Android ART? Android Lollipop is around the corner and it only supports ART now :( OSG is a native code library on Android, so it shouldn't make any difference which Java runtime (whether Dalvik or ART) is the system running. J. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] Register object wrapper for osg::Geode
Hi, I notice that osg::Geode now inherits osg::Group instead of osg::Node. However, in the corresponsing serializer osg::Group is not mentioned in REGISTER_OBJECT_WRAPPER( Geode, new osg::Geode, osg::Geode, osg::Object osg::Node osg::Geode ) Is this correct ? or should it be changed to REGISTER_OBJECT_WRAPPER( Geode, new osg::Geode, osg::Geode, osg::Object osg::Node osg::Group osg::Geode ) Kind regards John Ivar Haugland ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Render into a QQuickFramebufferObject (osg / osgEarth)
Hi, you could have a look at the OSG-integration into our rendering framework gloperate (github/hpicgs/gloperate), where I have implemented a very similar setup. The OpenGL context is managed from the outside, and OSG rendering is set up with setUpViewerAsEmbeddedInWindow, which means that the OSG does not really know about the context and you have to make sure the context is made current before rendering. I also had the problem that it worked with OSG but not osgEarth, which I tracked down to the following problem: On the first frame, osgEarth initializes itself and queries its capabilities (see osgEarth/Capabilities.cpp). To do that, it initializes a temporary OpenGL context, queries OpenGL version and available functions, and then releases the context. With a typical OSG setup, we have an OSG context object that will be made current before rendering, so this makes no problems. But when using setUpViewerAsEmbeddedInWindow, the OSG has no way to make your context current, because it does not know about it. So, after osgEarth is initialized, you have lost your OpenGL context and have to make it current again before rendering. Hope this helps, Stefan On 24/03/15 15:49, Sascha Voth wrote: Hi, I'm trying to render a scene node in a QtQuickItem. For this I used the Qt example Scene Graph - Rendering FBOs as a base template: qtquick-scenegraph-textureinsgnode-fboinsgrenderer-cpp @ qt.io Additionally I found a Gists which does nearly the same thing I'm trying to achieve: gist:9bf4cec0aee18fc6e27b On construction I create an EmbeddedWindow and a Viewer, and setup my scene. Afterwards the createFramebufferObject is used to allocate the FBO and resize the EmbeddedViewer and the Viewport. Rendering is triggered with a frame() call inside the render function and the osg::Viewer is set up to run SingleThreaded. As long as I use/add a simple osg::Node to the scene, e.g. cow.osg, everything seems to work fine. As soon I start to change the CameraManipulator to osgEarth::Util::EarthManipulator and use a osgearth::MapNode instead, the first drawn frame is black, and changes only on re-sizing and recreating the FBO, but only once. Afterwards, the render function is called, but frame() seems to not render anything anymore. I suppose something gets messed up with the OpenGLContext or osgEarth does not work SingleThreaded, but I'm currently not able to understand the problem as a whole. I even tried to create a new shared context like rickyviking/qmlosg at github did, but could not get it to render a propre scene. Any help would be appreciated! Thank you! Cheers, Sascha p.s.: I've tried different other approaches in advance, where many of them seem to be outdated or lacking simple re-sizing functionality. My current implementation uses a QQuickItem which has a re-implemented QSGSimpleTextureNode which shares an FBO with an osg::Camera. But i cannot manage to resize the fbo texture ... p.p.s.: Sorry for not posting the links directly, but You must have 2 posts before you can post URL's/Links. ... -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=63192#63192 ___ 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
Re: [osg-users] Android ART
On Tue, Mar 24, 2015 at 4:26 PM, Colin Cochran co...@terminaleleven.com wrote: Thanks Jan, I swear I remember a while back (about 6 months ago) ppl were having trouble getting OSG to run on ART here on the forums, but I can no longer find that topic. Maybe I was just imagining it... -C They probably just had general problems with Android - the compilation is not really that straightforward thanks to the crappy Google tools and the need to interface Java code to OSG via JNI is an enormous pain ... But not of that is really ART specific. J. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
