Thanks Conan!
Nick
On Thu, Oct 23, 2014 at 3:08 PM, Conan Doyle wrote:
> +1 on gDEBbugger.. very useful tool... also look into AMD CodeXL, which I
> believe, is an updated version of gDEBugger.
>
>
> Trajce Nikolov NICK wrote:
> > Thanks Sebasitian . I have heard of it but never tried. Now
+1 on gDEBbugger.. very useful tool... also look into AMD CodeXL, which I
believe, is an updated version of gDEBugger.
Trajce Nikolov NICK wrote:
> Thanks Sebasitian . I have heard of it but never tried. Now seam the time
> comes. Thanks again!
>
> Nick
>
>
> On Thu, Oct 23, 2014 at 1:
Thanks Sebasitian . I have heard of it but never tried. Now seam the
time comes. Thanks again!
Nick
On Thu, Oct 23, 2014 at 1:50 PM, Sebastian Messerschmidt <
sebastian.messerschm...@gmx.de> wrote:
> Hi Nick,
>
> I usually use GDebugger or similar tools which can hook into the
> OpenGLDrive
Hi Nick,
I usually use GDebugger or similar tools which can hook into the
OpenGLDriver. There you can get the stack-trace telling you the
provoking OpenGL call.
Good tools might like GDebugger will also allow you to see the actual
code (e.g. the OSG call) where the error stems from
Thanks
doing it.
>
> -Original Message-
> From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On
> Behalf Of Trajce Nikolov NICK
> Sent: Thursday, October 23, 2014 7:36 AM
> To: OpenSceneGraph Users
> Subject: Re: [osg-users] invalid enumerant error
&g
: Thursday, October 23, 2014 7:36 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] invalid enumerant error
Thanks Karl,
I set this in my code:
std::ostringstream oss;
oss << "OSG_GL_ERROR_CHECKING=ON";
_putenv(oss.str().c_str());
still getting the same output, nothing extra. I
Thanks Karl,
I set this in my code:
std::ostringstream oss;
oss << "OSG_GL_ERROR_CHECKING=ON";
_putenv(oss.str().c_str());
still getting the same output, nothing extra. I am using TextureRectangle
as well so might be the same issue. Any further hints?
Thanks a bunch!
Nick
On Thu, Oct 23, 2014
Robert had a suggestion in the past that helped me track down a similar issue
in the past. From an earlier post from him:
One way of pinpointing the error better is to enable fine grained error
checking in the osg::State by setting the env OSG_GL_ERROR_CHECKING to ON, on
my Linux system this is
8 matches
Mail list logo