[osg-users] SIGGRAPH BOF Summary
Hello, The BOF was a success and well attended. I will post a photo of smiling faces. Robert's slides were presented. The attendees consensus was that they were more interested in Robert's thought's on the Vulcan future. His slides gave some thoughts and some metrics on some preliminary tests that were very nice. The slides on how OSG will still be supported was pleasing to the multitude. Steve Satterfield from NIST gave some results of a concrete simulation versus real physical tests visualizing via OSG. The simulation was on a supercomputer cluster at NIST I believe. David presented his "Wally Pack" which is a backpack VR/AR affordable and rugged solution using Windows Mixed Reality SDK [Hololens HMD I believe]. John ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] Re-purposing the performance graph
Hi folks, I'm sure this has been asked before but is there an example for using the performance graph to render custom statistics? Cheers, Brad -- Brad Colbert Renaissance Sciences Corporation (four eight zero) two nine zero - three nine nine seven <14802903997> ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Core Profile: glEnable/glDisable GL_POINT_SPRITE
On Wed, 22 Aug 2018 at 12:54, Daniel Emminizer, Code 5773 wrote: > It's on my list to swap over to 3.6-TexStorage to make sure it doesn't break > anything. I'll do that in the next couple of days and test this out. Thanks. > The change looked good from a quick review on 3.6 branch. But on master > branch you have "if (false)" around the code block. I'll point out on github > to make it easier to find. Looks unintentional and does not match 3.6 branch. I'm a bit confused by this assertion as I don't see the if (false) in the master branch. The if (false) was added to help test whether the GL warnings were visible with/without the fix. I checked in removal of this. Master shouldn't have this, and I removed this from the 3.6 and 3.6-TexStorage where it was unintentionally checked in. Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] OpenSceneGraph-3.6-TexStorage branch created, needs community testing :-)
On Wed, 22 Aug 2018 at 11:19, michael kapelko wrote: > Hi. Who's the audience of the change? (i.e. should I care?) With my focus on new feature dev to the VSG project for the next year the next major OSG release (4.0) is pushed a bit further out, so availability of new features that are in master in a stble release will take longer, so if there are features in master that can be pulled into the 3.6 branch without affect the public API and without risking stability then I'm open to do this. The glTexStorage functionality is a possible candidate for this as it only changes the implementation, it doesn't affect the API. However, the "risking stability" is an open question, this can only be properly answered by wider testing in the community. Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Core Profile: glEnable/glDisable GL_POINT_SPRITE
Disregard, looks like you already got it! Thanks. > -Original Message- > From: Daniel Emminizer, Code 5773 > Sent: Wednesday, August 22, 2018 6:37 AM > To: OpenSceneGraph Users > Subject: RE: [osg-users] Core Profile: glEnable/glDisable GL_POINT_SPRITE > > Hi Robert, > > It's on my list to swap over to 3.6-TexStorage to make sure it doesn't break > anything. I'll do that in the next couple of days and test this out. > > The change looked good from a quick review on 3.6 branch. But on master > branch you have "if (false)" around the code block. I'll point out on github > to > make it easier to find. Looks unintentional and does not match 3.6 branch. > > - Dan > > > > -Original Message- > > From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On > > Behalf Of Robert Osfield > > Sent: Wednesday, August 22, 2018 6:23 AM > > To: OpenSceneGraph Users > > Subject: Re: [osg-users] Core Profile: glEnable/glDisable GL_POINT_SPRITE > > > > Hi Dan et. al, > > > > To resolve this issue I have added a mode validity setting to > > State::nitializeExtensionProcs(), this resolves the GL warning > > generated by the checkvalidity_bug test program. The fix is checked > > into master, 3.6 branch and 3.6-TexStorage. > > > > Cheers, > > Robert. > > ___ > > 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] Core Profile: glEnable/glDisable GL_POINT_SPRITE
Hi Robert, It's on my list to swap over to 3.6-TexStorage to make sure it doesn't break anything. I'll do that in the next couple of days and test this out. The change looked good from a quick review on 3.6 branch. But on master branch you have "if (false)" around the code block. I'll point out on github to make it easier to find. Looks unintentional and does not match 3.6 branch. - Dan > -Original Message- > From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On > Behalf Of Robert Osfield > Sent: Wednesday, August 22, 2018 6:23 AM > To: OpenSceneGraph Users > Subject: Re: [osg-users] Core Profile: glEnable/glDisable GL_POINT_SPRITE > > Hi Dan et. al, > > To resolve this issue I have added a mode validity setting to > State::nitializeExtensionProcs(), this resolves the GL warning > generated by the checkvalidity_bug test program. The fix is checked > into master, 3.6 branch and 3.6-TexStorage. > > Cheers, > Robert. > ___ > 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] Core Profile: glEnable/glDisable GL_POINT_SPRITE
Hi Dan et. al, To resolve this issue I have added a mode validity setting to State::nitializeExtensionProcs(), this resolves the GL warning generated by the checkvalidity_bug test program. The fix is checked into master, 3.6 branch and 3.6-TexStorage. Cheers, Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] OpenSceneGraph-3.6-TexStorage branch created, needs community testing :-)
Hi. Who's the audience of the change? (i.e. should I care?) On Tue, 21 Aug 2018 at 15:48, Robert Osfield wrote: > > HI All, > > I have created a OpenSceneGraph-3.6-TexStorage branch to allow > glTexStorage support that was just in the master branch to be ported > back onto 3.6. There isn't any public API changes so it should drop > in OK compile wise, runtime wise it's a different matter though. > > We need testing across a wide range of platforms/hardware and > application usage cases to know whether this change is safe. If it > all looks OK then I'll merge 3.6-TexStorage into the main 3.6 branch > and then we can start working towards a 3.6.3 release in September. > > So please test if you can. Many thanks, > Robert. > ___ > 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] Using Light without LightSource in OSG 3.4.0
Hi Chenyanlin,
OpenGL lights are a form of positional state, positional state uses
the current modelview matrix to compute the values in eye space that
are passed to the graphics card to do the maths required within the
shaders.
If you just place the Light into the scene graph as you'd do with non
positional state then it's value will change as the eye point is
moved.
The LightSource node exists to fix a Light into a particular position
in space - with a particular modelview matrix, which is how the OSG
resolves the correct position of Light in the scene.
Because positional state has to have a specific position in space to
work correctly there are limits on how they are handled - you can't
have different state in different subgraph, instead the OSG has apply
the same Light at the same position for the whole rendering stage.
This coupled with OpenGL's own limits on the number of glLights that
can be active at once with the fixed function pipeline means that to
have larger numbers of lights you need to start thinking about using
shaders or using multiple stages of rendering, which each stage
handling a different region of the scene with it's own sets of lights.
Robert.
On Wed, 22 Aug 2018 at 04:28, chenyan...@fulongtech.cn
wrote:
>
> Hi,
>
> I want to add light to my scene and I want the different light which have
> same Number can be used at the same time.Thus , I use light as a Attribute to
> set it to stateset. There is no problem when the model is not rotate.But when
> model is rotated, the light seemed rotated by the matrix.There is my source
> code:
>
> int main()
> {
> osg::ref_ptr root = new osg::Group;
> osg::ref_ptr light = new osg::Light;
> light->setLightNum(0);
> light->setPosition(osg::Vec4(0, 0, 1, 0));
> light->setAmbient(osg::Vec4(0,0, 0, 1));
> light->setDiffuse(osg::Vec4(0, 1, 0, 1));
> light->setSpecular(osg::Vec4(1, 0, 0, 1));
> auto stateSet = root->getOrCreateStateSet();
> stateSet->setAttributeAndModes(light);
> osg::ref_ptr hints = new osg::TessellationHints;
> hints->setDetailRatio(0.1);
> osg::ref_ptr geode1 = new osg::Geode;
> osg::ref_ptr shape1 = new osg::ShapeDrawable(new
> osg::Box(osg::Vec3(0, 0, 0), 10, 10,10), hints.get());
> geode1->addDrawable(shape1);
> osg::ref_ptr geode2 = new osg::Geode;
> osg::ref_ptr shape2 = new osg::ShapeDrawable(new
> osg::Box(osg::Vec3(20, 20, 20), 10, 10, 10), hints.get());
> geode2->addDrawable(shape2);
> osg::ref_ptr mt = new osg::MatrixTransform;
> osg::Matrix mat;
> mat = mat.rotate(180, osg::Vec3(0, 1, 0));
> mt->setMatrix(mat);
> mt->addChild(geode2);
> root->addChild(mt);
> root->addChild(geode1);
> osgViewer::
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Core Profile: glEnable/glDisable GL_POINT_SPRITE
Hi Dan, On Tue, 21 Aug 2018 at 23:15, Daniel Emminizer, Code 5773 wrote: > Still a low priority because I am able to work around in my own code. But > wanted to make sure this doesn't get lost in the traffic about texture modes > in other threads. The original message had an example .cpp that demonstrated > the issue. > > Is it worthwhile to create an issue on the github issue tracker? If I am not able to address the problem right away then it would make sense to put it into the Issue tracker to make it easier to find, a reference back to any associated thread on osg-users ML/forum would help too. I will spend some time on it this morning, so no need to add it to Issue right away, hopefully I'll have a fix before you get online! Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] New glTexStorage code is disrupting FBO initialization
On Tue, 21 Aug 2018 at 20:43, Paul Levy wrote: > Seems to be working now. Yesterday I submitted a PR to change GL_RGBA16F and > GL_RGBA32F to GL_RGBA16F_ARB and GL_RGBA32F_ARB, but you only changed > GL_RGBA32F. Both are undefined on Windows so I re-submitted a PR to get the > Windows build building again. Thanks for the test and build fix, now merged. Cheers, Robert, ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
