Re: [osg-users] [Any feedback welcome] lack of robustness of the VAO path

Arg it doesn't crash with Mesa 18.0.5/intel chipset!? mp3butcher wrote: > Hi > I think the first step to fix this issue is first to reproduce it > I crash osg3.6 with a GT440 on Ubuntu NVIDIA driver 390.87 > https://github.com/openscenegraph/OpenSceneGraph/issues/697 > I'll check if mesa

Re: [osg-users] [Any feedback welcome] lack of robustness of the VAO path

Hi I think the first step to fix this issue is first to reproduce it I crash osg3.6 with a GT440 on Ubuntu NVIDIA driver 390.87 https://github.com/openscenegraph/OpenSceneGraph/issues/697 I'll check if mesa fails too tonight But if anyone have the time to confirm it, I would be very glad

Re: [osg-users] Loading osgt from string / Compile resources into binary

Hi Michael, The portable way is to define a byte array. See this stackoverflow for more detail: https://stackoverflow.com/questions/7288279/how-to-embed-a-file-into-an-executable Sent from my iPhone > On Jan 21, 2019, at 4:02 AM, Michael Maurus wrote: > > Hi guys, > > is it possible to

Re: [osg-users] [Any feedback welcome] possible lack of robustness of the VAO path

HI Julien, On Mon, 21 Jan 2019 at 14:51, Julien Valentin wrote: > This mod fix the issue but it's surely not clean enough for you > > Code: > void VertexArrayState::generateVertexArrayObject() > { > _ext->glGenVertexArrays(1, &_vertexArrayObject); > if(_vertexArrayObject ==

Re: [osg-users] [Any feedback welcome] possible lack of robustness of the VAO path

This mod fix the issue but it's surely not clean enough for you Code: void VertexArrayState::generateVertexArrayObject() { _ext->glGenVertexArrays(1, &_vertexArrayObject); if(_vertexArrayObject == _state->getCurrentVertexArrayObject()) _state->setCurrentVertexArrayObject(-1); }

Re: [osg-users] [Any feedback welcome] possible lack of robustness of the VAO path

I admit the fix is kind of hacking :/ Haven't find a proper way to fix it yet but you keep closing issues pointing the bug... I debugged a lot to find this issue so please respect that. I reopened an issuemay this one is clean enough not to be treated as garbage robertosfield wrote: > On

Re: [osg-users] [Any feedback welcome] possible lack of robustness of the VAO path

On Mon, 21 Jan 2019 at 10:56, Julien Valentin wrote: > If you have any real argument against this change, please expose it > publically. The Issue code your wrote is a mess of bad programming practices. How would we know where a problem is when the Issue code has so many problems of it's own.

[osg-users] Loading osgt from string / Compile resources into binary

Hi guys, is it possible to somehow compile resources like models/nodes into an executable? How about putting the content of an osgt file as a string into my source code? But as far as I've seen, there is no readNodeFromString method in osgDB. Any ideas/suggestions? Thank you! Cheers, Michael

Re: [osg-users] [Any feedback welcome] possible lack of robustness of the VAO path

Hi I'm pretty outraged about the way everyone seems to close eyes on the bug i spot. Further Robert keep closing all my issue and pr with fallascious reason. Do you even see the problem? When a vao is deleted and a new one is regenerate, they may have the same name and so pass as the same for

[osg-users] 'EarthManipulator', how to manage to get the view of invisible underground part of the model in course of rotating operation?

Hi, In setting up the roaming scene model of 'EarthManipulator', how to manage to get the view of invisible underground part of the model in course of rotating operation? Thank you! Cheers, Mirro -- Read this topic online here: