Hi Curtis,
Good to hear the OSG svn/trunk is working fine for you now. The OSG-3.4
branch and OSG-svn/trunk are in sync right now except for the version
numbers.
Robert.
On 10 August 2015 at 16:16, Curtis Rubel cru...@compro.net wrote:
Hi Robert,
I updated to the latest in the trunk this
Hi Robert,
I updated to the latest in the trunk this morning, version reporting it as 3.5.0
So far everything appers to be working flawlessly. The example I gave you
for the segv is working for me as well as all of our OSG applications seem
to be working perfectly
I think I even see a few
Hi Robert,
OK I will update my copy of the OSG trunk and let you know as soon
as I have a minute. Probably something I will have to do in my
off time at home as work time is pretty much taken up right now.
I would not consider myself a QT expert either, but will see if I can find
anything that
Hi Curtis,
On 5 August 2015 at 18:19, Curtis Rubel cru...@compro.net wrote:
Just tested the trunk from a svn co from about 1 hour ago,
with my test osgviewerQT.cpp source.
Still getting a segv when running it. I was running in release
mode for this test so cannot verify if its exactly the
HI Curtis,
On 5 August 2015 at 17:42, Curtis Rubel cru...@compro.net wrote:
I noticed some references to this reported issue in the latest Changelog
for the trunk
checking for the proper setup of the number of contexts in the osgText
area.
Do you think this entire issue is now resolved or
Hi Robert,
I noticed some references to this reported issue in the latest Changelog for
the trunk
checking for the proper setup of the number of contexts in the osgText area.
Do you think this entire issue is now resolved or is the possible issue with
QtOSG and it not reporting the number of
Robert,
Just tested the trunk from a svn co from about 1 hour ago,
with my test osgviewerQT.cpp source.
Still getting a segv when running it. I was running in release
mode for this test so cannot verify if its exactly the same fault
or notbut it would seem that there is still some sort of
Hi,
Any chance the fix for this was included in the 3.3.8 release
and I just did not see any notice of it?
...
Thank you!
Cheers,
Curtis
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=64098#64098
Hi Robert,
I compiled and tested the code to make sure it failed the same
way before posting it, so that is sort of strange to find this
type of thing now.. I was testing on 64bit Linux here..
Well I am glad it did not waste to much of your time, I know you
have been really busy lately from
Hi Curtis,
I have just tried your modified example, had to fix a compile error with
the #includeosgcamera.h, did you even compile the code?
Anyway the code seg faults in osgText as you suggest.
I haven't had a chance to look into why this happening, my guess is that
osgQt isn't initializing the
Hi Everyone,
Attached to this post is an example that causes the segv to occur that I am
referring to in my first post on the subject. This example is the combination
of portions the osgviewerQT and osgText examples as provided with this same
release of OpenSceneGraph.
Hopefully with this
Hi,
Just updated the attachment, had an extra include file that was not
present listed in the source that was not needed. My apologies if this caused
anyone any issues before I caught the problem.
...
Thank you!
Cheers,
Curtis
--
Read this topic online here:
Hi Robert,
Thank you for looking in to this for us...
I did a quick test against the 3.3.3 release and it appears to be working OK.
So seems this has something to do with changes that occurred after that
release.
...
Best Regards!,
Cheers,
Curtis
--
Read this topic online
Hi Curtis,
I'm currently looking at other bugs right now, coincidently in
osgText, but once these are addressed I'll try to have a look at the
crash you have. This should be early next week.
Robet
On 1 May 2015 at 15:14, Curtis Rubel cru...@compro.net wrote:
Hi Everyone,
Attached to this
Hi Robert,
After getting the small example to fail today, I was looking some more and came
up with a few changes here that allows me to run.
I am relatively sure that this will not be the final fix, but I am hoping that
it will at least get you closer to what is causing the problem. Here is
Hi Curtis,
I haven't had a chance to look at the code yet but from your
description of the fix you've applied it suggests to me that the
normal scene graph mechanism used to inform the scene graph that the
number of contexts and hence range of ContextID's has changed is not
happening as it should
Robert,
One other thing to mention, I have another application that is pure OSG that is
to say it is NOT using an QT widgets and it is doing basically the same thing
as the QT app that I have and it runs OK as far as I can tell. The example
code I sent you that is failing is also based on the
HI Curtis,
I don't recall any chances to osgText that might cause a crash in this
particular bit of code. The particular data structure that is causing
the problem is a one that should be the same size as the number of
contexts that are active in your application. Are you changing the
number of
Hi Robert,
The application that is having this issue is very large, so I will have to
dig into it and see about finding the exact location of the segfault. The
author of the app no longer works with us so this will take some time to
investigate.
The application is one where OSG is an object
Hi,
We have an application that is outputting a number of osgText::Text objects as
well as some osgLabel objects.
Everything appears to be working fine when compiled against OSG 3.3.1
On the current trunk as of yesterday, I am getting a segfault in osgText
Text.cpp drawImplementation()
20 matches
Mail list logo