Hi Rob,
Be sure that if you’re using cloning that everything in the scene supports
cloning. If you have custom (non-OSG) nodekit elements in the scene, cloning
may only be partially supported. That can certainly cause issues with that
approach. Though OSG nodes supports cloning, not all
Hi Robert,
So far so good here with initial testing. I had been concerned about Laurens's
update on text, but it looks like it turned out without problems. I was able
to adjust back one of the text scaling options so now we're back to consistent
between 3.4.1, 3.6.2, and 3.6.3-rc2, with
Hi Brian,
This might be fixed by:
https://github.com/openscenegraph/OpenSceneGraph/commit/e8b56c5c9735e70
It's documented on the mailing list thread:
http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2018-August/008829.html
- Dan
> -Original Message-
> From:
2018 9:29 AM
> To: OpenSceneGraph Users
> Subject: 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'l
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 Ro
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
on the github issue tracker?
Thanks.
- Dan
> -Original Message-
> From: Daniel Emminizer, Code 5773
> Sent: Wednesday, August 01, 2018 7:25 AM
> To: OpenSceneGraph Users
> Subject: RE: [osg-users] Core Profile: glEnable/glDisable GL_POINT_SPRITE
>
> Hi Robert,
>
t; Behalf Of Robert Osfield
> Sent: Friday, August 17, 2018 4:03 AM
> To: OpenSceneGraph Users
> Subject: Re: [osg-users] VAO Resource Leak in OSG 3.6.2
>
> Hi Dan,
>
> On Fri, 17 Aug 2018 at 07:04, Daniel Emminizer, Code 5773
> wrote:
> > Hi Robert, thanks for the upd
Hi Robert, thanks for the update. I'm happy to test my side against whatever
you decide, once I'm in the office.
Thanks,
- Dan
> -Original Message-
> From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On
> Behalf Of Robert Osfield
> Sent: Thursday, August 16, 2018
Hi Guy,
I attached to the original issue a use case that reproduces the problem.
glDeleteVertexArrays() is never called on many of the arrays, although the
associated geometry is destroyed. This goes until exit. The VAOs leak. This
can be verified by running a profiler on GL and examining
O Resource Leak in OSG 3.6.2
>
> Hi Dan,
>
> I'll be focusing on Vulkan work today so won't look into this right
> away. Next week I'll set aside a day for OSG maintenance and
> hopefully will be able to look at this then.
>
> Robert.
> On Thu, 2 Aug 2018 at 15:49,
Hi Robert,
I think I've found a resource leak in OSG 3.6.2. Attached is a contrived
sample application that demonstrates the behavior.
What appears to be happening is that the VAO is being created with
glGenVertexArrays(), but does not get deleted with glDeleteVertexArrays().
Using the open
Hi Robert,
I just started seeing something similar at the end of the day yesterday. I am
using osg::PointSprite, not using GL_POINT_SPRITE directly. I have some more
background too and I think I see the cause, but not the solution.
PointSprite::checkValidityOfAssociatedModes() is great, and
Emminizer, Code 5773
mailto:dan.emmini...@nrl.navy.mil>> wrote:
Hello All,
I've found what appears to be unbounded growth in the OpenFlight loader. I
have a work-around but wanted to run it past the community since there are many
here who are more familiar with the format and the loader t
Hello All,
I've found what appears to be unbounded growth in the OpenFlight loader. I
have a work-around but wanted to run it past the community since there are many
here who are more familiar with the format and the loader than me.
I'm seeing uncontrolled memory growth when using the
Hi Robert,
Thanks for the merge! It helps.
A little explanation, if you have any interest. It's a little long, but I hope
to explain why we're looking at Core Profile. I'd like to think it's for good
reason.
I'm with you on the OSX issues. I think it's a shame about what's going on
over
Hi Robert,
Tl;dr: I think I found a bug in OpenFlight's FltExportVisitor::isTextured()
when FFP is disabled. This email explains PR 568 more thoroughly.
I am having problems saving out OpenFlight models and was hoping someone could
point out what I'm doing wrong. I think I might have
Hi Robert,
I can vouch that it compiles on MSVC 2015, MSVC 2010, and g++ 4.4. I did not
test 2012 or 2013, since I figured 2010 and 2015 ought to cover (2015 is
_MSC_VER 1900). I only tested 64 bit variants. I do not have MSVC 2017 to
test against.
I am also not familiar with the code in
Hi Robert,
I have found a minor bug with image scaling. I have a texture that is 1024x768
that is being resized to 1024x1024 for a Texture2D.
Texture::applyTexImage2D_load() detects the need to resize and tries to do so
through gluScaleImage(), which is implemented in
Hi Maxim / Robert,
I am using GL3 on Windows. I had to download and slightly modify the Khronos
glcorearb.h file, to get it working right with the declspec or dllimport or
whatever it was. It was not trivial or obvious by any means. But it works
now, after supplying that file.
I understand
to fit in the
release if desired.
- Dan
From: Daniel Emminizer, Code 5773
Sent: Monday, June 25, 2018 5:37 AM
To: OpenSceneGraph Users
Subject: RE: [osg-users] OpenSceneGraph-3.6.2-rc1 tagged, please test
Hi Robert,
I’ve built and have been running OSG 3.6.2-rc1 on several MSVC versions and g
s-boun...@lists.openscenegraph.org] On
> Behalf Of Robert Osfield
> Sent: Monday, June 25, 2018 5:46 AM
> To: OpenSceneGraph Users
> Subject: Re: [osg-users] OpenSceneGraph-3.6.2-rc1 tagged, please test
>
> Hi Dan,
>
> On Mon, 25 Jun 2018 at 10:37, Daniel Emminizer, Code 5773
> wrote:
> &g
Hi Robert,
I’ve built and have been running OSG 3.6.2-rc1 on several MSVC versions and g++
4.4 without problems since Wednesday. Success all around so far.
- Dan
From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf
Of Robert Osfield
Sent: Wednesday, June 20, 2018
Hi Robert,
I agree that your solution here seems to cover the common failure case
(assigning by-vertex too late). I think given the system constraints and time
constraints, that is the best solution.
Your solution does work in all my testing.
Regarding a 3.6.2 release, that sounds great. At
Hi Robert,
That would cover our primary use cases. We've already done the same in all of
our application code.
Catching the failure instead of crashing is very much preferred, even if it
leads to a bad display.
I'm on board with this solution and can help test my end.
- Dan
>
Hi Robert,
I agree with your analysis on all points. I did not see a quick solution that
was "proper" either.
I agree that creating temporary VBOs doesn't seem like a wise solution.
I don't know enough about the inner workings to know if this is a dumb idea --
but could you perhaps detect
Hi Robert,
Thanks for this change. Unfortunately it does not look like it fixes my issue.
I'm building GL3 core profile mode against OpenSceneGraph-3.6. I use the
main.cpp and CMakeLists.txt from my 6/1/18 email. I'm using NVidia card with
NVS 510, driver 388.19, OpenGL version 3.3.0 (due
fferObject assigned.
>
> If you have made a commit for this fix against your own git clone of
> the OSG just pointing me at this commit should help me understand what
> is going on better.
>
> Cheers,
> Robert.
> On Mon, 11 Jun 2018 at 14:44, Daniel Emminizer, Code 5773
>
s\OpenFlight\GeometryRecords.cpp )
Regards, Laurens.
On Mon, Jun 11, 2018 at 3:37 PM, Daniel Emminizer, Code 5773
mailto:dan.emmini...@nrl.navy.mil>> wrote:
Hi Robert,
I am back from travel and looking at this again. Didn't get a response on last
set of questions about this crash. Sorr
age-
> From: Daniel Emminizer, Code 5773
> Sent: Monday, June 04, 2018 8:45 AM
> To: OpenSceneGraph Users
> Subject: RE: [osg-users] VBO Bug with 3.6.1 and Normal Arrays
>
> Hi Robert,
>
> The file you sent is identical to the one I sent. Was that intentional? You
> also
alf Of Robert Osfield
> Sent: Sunday, June 03, 2018 6:11 AM
> To: OpenSceneGraph Users
> Subject: Re: [osg-users] VBO Bug with 3.6.1 and Normal Arrays
>
> Hi Dan,
>
> On 1 June 2018 at 16:01, Daniel Emminizer, Code 5773
> wrote:
> > Attached is a demo of the probl
Hi Robert,
Oops -- I sent this earlier today but apparently to the bounces list; that
explains the confusion on GitHub -- my mistake. This was supposedly sent right
before I posted the PR. Here's the original text:
I think I found a bug in 3.6.1. I am loading a FLT model and it's causing a
Hi Brad,
Check to make sure your Geometry has setDataVariance(osg::Object::DYNAMIC).
That solved the problem for most of our similar cases.
- Dan
From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf
Of Brad Colbert
Sent: Friday, June 01, 2018 10:20 AM
To:
Hi Robert,
Latest changes from you on OpenSceneGraph-3.6 branch work good for me, my error
gone on Render Leaf printout. All display looks good.
Thanks,
- Dan
> -Original Message-
> From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On
> Behalf Of Robert Osfield
>
Robert, Glenn,
I am seeing this problem too in a different application than Glenn.
I have not yet reported it yet because I've moved forward to upgrading another
part of my application, and only then started to see the problem. I figured it
was something on my own end and haven't investigated
Hi Robert,
Looks good on my side. I ran it through all of my applications and I do not
spy any regressions from this change. Phew!
Thanks for the support. I'm actually getting pretty excited about the Text now
with our update to OSG 3.6.
If it's helpful -- I am also seeing the problem
tio varies as user resizes the window; the example
starts at 800x300 (8:3).
The screenshot is against OpenSceneGraph-3.6, most recent push.
- Dan
> -Original Message-
> From: Daniel Emminizer, Code 5773
> Sent: Monday, May 21, 2018 11:09 AM
> To: OpenSceneGraph Users
>
Hi Robert,
I'm using the latest OpenSceneGraph-3.6 with the scaling changes that just got
pushed out.
I'm getting a bad scaling on a label that is rotated that used to work in OSG
3.4, and used to work prior to
https://github.com/openscenegraph/OpenSceneGraph/commit/76d1b85
Note that 76d1b85
2018 8:15 AM
> To: OpenSceneGraph Users
> Subject: Re: [osg-users] Please test OpenSceneGraph-3.6
>
> Hi Dan,
>
> On 21 May 2018 at 12:42, Daniel Emminizer, Code 5773
> <dan.emmini...@nrl.navy.mil> wrote:
> > Seems like a reasonable approach. I'll rebuild on my
TEMINTERFACE
> implementation back to what it was and either introduce a new macro
> that adds the OSGVIEWER_EXPORT or just have the
> GraphicsWindowWin32.cpp not use the this help marco at all, and just
> have it declare the extern and proxy objects directly in the code.
>
>
>
Hi Robert,
Getting a Windows build error on osgQt from the change on
REGISTER_WINDOWINGSYSTEMINTERFACE() macro from last week. Are you the right
person to report the problem to?
osgQt's GraphicsWindowQt.cpp includes the line:
#if 1
REGISTER_WINDOWINGSYSTEMINTERFACE(Qt, QtWindowingSystem)
Hi Robert,
No problem. I thought that might be the answer, but I figured it was worth
passing along the example just in case.
Thanks for the fast response.
- Dan
> -Original Message-
> From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On
> Behalf Of Robert Osfield
Hi Robert,
I hope you're not sick of hearing from me yet. I have uncovered a difference
of behavior between 3.4 and 3.6 in osgText::Text's bounding box calculation.
The attached program attempts to demonstrate the difference.
In one place in our application, we are trying to determine the
Hi Robert,
Tested out on my apps and everything regarding window resizing and text size is
completely fixed now. Thanks a lot.
I spent several hours yesterday going over the code and trying to understand
the transforms and shortcuts that were being taken. I was not able to come up
with
Hi Chris,
Not sure if this is what you’re looking for, but you can give a hint to the
drivers by exporting variables in your code. In my main.cpp I do something
like:
#ifdef WIN32
extern "C" {
/// Declare this variable in public to enable the NVidia side of Optimus -
size2" (or resize the view to be short), that the text is all
readable and you can clearly see "330 000 030 060" in the display with no
significant overlap?
Thanks,
- Dan
-Original Message-
From: Daniel Emminizer, Code 5773
Sent: Thursday, May 10, 2018 11:42 AM
To: 'OpenScene
Hi Robert,
Thanks for trying the example. I'm perplexed why it's OK for you but not me.
In case you're curious, I'm attaching the screenshots of the output.
I should note again that I am running with OPENGL_PROFILE="GLCORE" / GL3 mode.
Would that make a difference?
I will rebuild
Hi Robert,
Attached is an osgtext.cpp that demonstrates the problem I'm seeing in our
application with text in SCREEN_COORDS scaling improperly.
In this particular app, we're using a FIXED projection matrix mapping (-1,-1)
to the lower-left corner, and (+1,+1) to the upper-right corner (ortho
Hi Robert,
Thanks for the update. I rebuilt today and retried. It does fix the problem
in the test app I sent. It also fixed scaling problems in one of our primary
applications. But it does not fix the problem in my other full-scale
application. But two out of three apps isn't bad!
I
Hi Robert,
Responding this time with a reproducible example. Attached is a minimal
osgtext.cpp that attempts to demonstrate a problem with text scaling.
There is 1 osgText::Text in screen coordinates. I would expect the text to be
the same size regardless of window dimensions. For most
-Original Message-
From: Daniel Emminizer, Code 5773
Sent: Thursday, May 03, 2018 11:42 AM
To: OpenSceneGraph Users
Subject: RE: [osg-users] OpenSceneGraph-3.6.1 release candidate 2 tagged
Hi Robert,
I'm trying to track down a problem now with osgText. There's a behavior change
that we're
Hi Robert,
I'm trying to track down a problem now with osgText. There's a behavior change
that we're seeing that I'm trying to narrow down. I have not yet attempted to
replicate in the osgtext example (but that's coming up soon).
In this application, we basically are doing a 2D plotting
release candidate.
Thanks,
- Dan
-Original Message-
From: Daniel Emminizer, Code 5773
Sent: Thursday, April 26, 2018 6:11 AM
To: OpenSceneGraph Users
Subject: RE: [osg-users] Please test OpenSceneGraph-3.6 branch in prep for 3.6.1
Hi Robert,
Sorry, was already out for the day yesterday
Hi Robert,
Sorry, was already out for the day yesterday by the time this was sent. It
looks like you already took care of it.
I will be rebuilding the 3.6.1 RC then I'll coordinate with my colleague who
has the Intel machine when he's in for testing confirmation. Will report back
in a few
Hi Robert,
> Head in hands moment...
Tell me about it! Took quite a long time to narrow down the crash to this one
issue.
> If it is a case that a driver update fixes it so that very few machines out
> there will ever hit this issue then perhaps just telling users to update
> drivers is the
Hi Terry,
Hey I might know this one. Thanks for that additional info about your driver.
Do you mind retesting with a change?
See references:
-
https://devtalk.nvidia.com/default/topic/971330/opengl/bug-report-crash-in-glcompileshader-if-using-pragma/
-
OpenSceneGraph-3.6 branch in prep for 3.6.1
Hi Daniel,
On 23 April 2018 at 20:46, Daniel Emminizer, Code 5773
<dan.emmini...@nrl.navy.mil> wrote:
> I also added a status display text to the lower left that is similar to
> something we're doing in our HUD. In arial you can see the text bouncing
Hi Robert,
> I am not at my dev system right now
No problem, I just didn't want to miss the window for bug reporting. I'm about
to head out for the day so I'll put together that PR for the version tomorrow
morning.
> Given it's just a debug feature it only using the inner text bounding box
Hi Robert,
> Please let me know of success and failures, or any bugs you've seen in
> 3.6.0 but haven't reported yet :-)
We've had a lot of success, and a couple of minor issues. Most of our issues
are with either running in GL Core 3.3, or using osgText. I'm trying to narrow
down the scope
the and the
OpenSceneGraph-3.6 branch.
https://github.com/openscenegraph/OpenSceneGraph/commit/6bfca1582efae9606e18883971c95eb734d70058
If this works OK then I'll tag a rc7.
Cheers,
Robert.
On 6 April 2018 at 17:08, Daniel Emminizer, Code 5773
<dan.emmini...@nrl.navy.mil> wrote:
> Hi Robert,
Hi Robert,
I've been testing the RC5 and I have a problem with text. I saw PR # 523 and
thought it might be the same problem. It looks quite similar to the issue I'm
seeing. I updated to RC6 (includes PR 523) and things look a lot better, but
not completely fixed.
I have finally been able
osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf
Of Robert Osfield
Sent: Thursday, April 05, 2018 9:23 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] OpenScenGraph 3.6 release candidate 5 tagged
Hi Dan,
On 5 April 2018 at 13:18, Daniel Emminizer, Code 5773
&
Hi Robert,
Looking good so far here with testing on GL Core 3.3. Main concerns is that
it's noisy on the console. You just pushed a commit that helps with this in
DisplaySettings::setShaderHint(). But I still see:
1) osgText prints errors about "Error reading file shaders/text.frag: file
Hello,
I've been working on testing the 3.6.0-rc3 OpenSceneGraph in an application
that was previously using 3.4.1. I found what I think is a bug with the
GUIEventAdapter::SCROLL handling when using a CompositeViewer. I also come
with a potential fix.
The symptom I'm seeing is that when I
Hi Robert,
I was able to test your patch and it works great. Thank you for the support.
- Dan
-Original Message-
From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf
Of Robert Osfield
Sent: Monday, April 02, 2018 11:24 AM
To: OpenSceneGraph Users
Subject:
Hi Robert,
This morning I tried the OSG 3.6.0-rc3 tag and started getting errors. I
tracked down the problem to the commit you reference in this email below:
https://github.com/openscenegraph/OpenSceneGraph/commit/9d5a22a0aa88125c3d41fc05bff72ae188b1a00b
Specifically the shader lines:
66 matches
Mail list logo
