Re: [osg-users] OpenSceneGraph-3.6.5 release candidate 2 tagged, please test

On Wednesday, January 29, 2020 at 11:02:48 AM UTC+1, Robert Osfield wrote: > > Hi Fabian, > > On Wednesday, 29 January 2020 00:24:35 UTC, Fabian Roth wrote: >> >> Hi Chris, >> I am using the latest openmw master with the compatibility patch from the >> pull request cherry picked, my build change

Re: [osg-users] OpenSceneGraph-3.6.5 release candidate 2 tagged, please test

Hi Robert, That commit does indeed seem to have fixed my minimal reproducible example, and, unlike with my other minimal reproducible examples, it's fixed the issue with the OpenMW-CS, too. Thanks for getting that sorted. Now I just have to remember what my favourite workaround for 3.4.1 was...

[osg-users] OpenScenGraph-3.6.5-rc3 tagged, please test :-)

Hi All, I have merged a couple of fixes since rc2 so it's time for another release candidate: https://github.com/openscenegraph/OpenSceneGraph/tree/OpenSceneGraph-3.6.5-rc3 If there aren't any issues reported by I'll go ahead a tag 3.6.5 tomorrow. Thanks in advance for testing, Robert. --

Re: [osg-users] OpenSceneGraph-3.6.5 release candidate 2 tagged, please test

Hi Robert, Compiling and a few simple runs worked fine, using windows 10 Enterprise 1909 18363,592 Visual Studio 15.9.19 CMake 3.15.5 Regards, Laurens. On Thu, Jan 30, 2020 at 5:30 PM OpenSceneGraph Users < osg-users@lists.openscenegraph.org> wrote: > Hi Chris et. al, > > On Thursday, 30 January

Re: [osg-users] Cannot render and load OBJ when using QOpenGLWidget with osgViewer::GraphicsWindowEmbedded on OSG 3.5.6 rc2 and 3.6.4

I will try, but I doubt it would be of insight, I am not running two different code, it's just launching the application using debugger or without (that's it), with the debugger application always is able to render the obj file, otherwise nothing is rendered. On Thursday, January 30, 2020 at 5

Re: [osg-users] Cannot render and load OBJ when using QOpenGLWidget with osgViewer::GraphicsWindowEmbedded on OSG 3.5.6 rc2 and 3.6.4

Maybe you can try to write out the Node to .osgt just after you read it, and compare the result between the working and non working version. Also to try: write out the options string; maybe other options have changed as well? The change in options suggests that you are somehow running different cod

Re: [osg-users] OpenSceneGraph-3.6.5 release candidate 2 tagged, please test

Hi Chris et. al, On Thursday, 30 January 2020 14:39:08 UTC, OpenSceneGraph Users wrote: > > I slowly closing in on the cause of the Font issue, currently it looks > like the removeView() is behaving differently form the CompositeViewer > destructor and not handling clean up of contexts correctly

Re: [osg-users] Cannot render and load OBJ when using QOpenGLWidget with osgViewer::GraphicsWindowEmbedded on OSG 3.5.6 rc2 and 3.6.4

Hi laurens, I've tried osgDB::Options("noTriStripPolygons") and now I can see VertexCacheVisitor searching all triangles but nothing is rendered. -- You received this message because you are subscribed to the Google Groups "OpenSceneGraph Users" group. To unsubscribe from this group and sto

Re: [osg-users] Cannot render and load OBJ when using QOpenGLWidget with osgViewer::GraphicsWindowEmbedded on OSG 3.5.6 rc2 and 3.6.4

Hi Laurens, thanks for the reply, I've noticed that also, that mean the Qt creator along with is triggering something (OpenGL related maybe) that in turns triggers this option switch in both cases. On Thursday, January 30, 2020 at 3:49:22 PM UTC+1, OpenSceneGraph Users wrote: > > Hi Mohamed, >

Re: [osg-users] Cannot render and load OBJ when using QOpenGLWidget with osgViewer::GraphicsWindowEmbedded on OSG 3.5.6 rc2 and 3.6.4

Hi Mohamed, there seems to be a difference in options between "works.txt" and "doesntwork.txt", doesntwork seems to run with "noTriStripPolygons" option, NOT generating a message "VertexCacheVisitor searching all triangles" Laurens. On Thu, Jan 30, 2020 at 2:59 PM OpenSceneGraph Users < osg-us

Re: [osg-users] OpenSceneGraph-3.6.5 release candidate 2 tagged, please test

Hi Chris, I slowly closing in on the cause of the Font issue, currently it looks like the removeView() is behaving differently form the CompositeViewer destructor and not handling clean up of contexts correctly. I need to refactor how things are done internally, but expect to have a solution chec

[osg-users] Cannot render and load OBJ when using QOpenGLWidget with osgViewer::GraphicsWindowEmbedded on OSG 3.5.6 rc2 and 3.6.4

When using *QOpenGLWidget *with *osgViewer::GraphicsWindowEmbedded *to render and load *OBJ *file nothing is being rendered, I am using latest osg 3.6.5 rc2 on ubuntu 19.10 with Inel graphics Card hd 620 using Mesa 19.3. When I create a passive osgViewer::GraphicsWindowEmbedded along QOpenGLWid

Re: [osg-users] DefaultFont crash issue

I too have seen thread-related issues when creating Text from multiple threads. I was never able to find the time to debug it to conclusion; but I suspect that a shared Font object that needs to create new Glyph textures isn't doing so in a thread-safe manner. For example, Font::assignGlyphToGlyphT

Re: [osg-users] DefaultFont crash issue

Hi Anna, On Wed, 29 Jan 2020 at 22:38, OpenSceneGraph Users < osg-users@lists.openscenegraph.org> wrote: > In relation to the DefaultFont crash issue, I noticed that my code would > occasionally crash on creation of osgText::Text. > Most of my osgText::Text is not created on the main thread. > In

Re: [osg-users] Bug with applying global default attributes?

Hi Rob, Have you tried the 3.6 branch? Is the issue a regression? Could you provide a test model and screenshot of the results your are getting vs expecting if possible. Cheers, Robert. On Wed, 29 Jan 2020 at 19:41, OpenSceneGraph Users < osg-users@lists.openscenegraph.org> wrote: > > I have