Re: [osg-users] EXTERNAL: Re: Read Image from RTT

Did you allocate storage for your osg::Image* before using it (i.e. osg::Image* img = new osg::Image)? That doesn't make sense why it would only work on a osg::ref_ptr. Marlin Rowley Software Engineer, Staff Missiles and Fire Control 972-603-1931

Re: [osg-users] Read Image from RTT

Solved the problem! Perhaps readImageFromCurentTexture() works only with osg::ref_ptr instead of osg::Image*. ... Thank you! Cheers, Rômulo -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=74986#74986

Re: [osg-users] EXTERNAL: Re: Read Image from RTT

I just noticed that. You'll have to check and see what line it's crashing on in the debugger. I just noticed that you get a graphics context but never check to see if it's NULL. A NULL pointer can't access any methods of the class it's referring to. Good Luck!

Re: [osg-users] Read Image from RTT

Hi Martin, I never faced with this problem. Do you have some tip to solve it? ... Thank you! Cheers, Rômulo -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=74984#74984 ___ osg-users mailing list

Re: [osg-users] EXTERNAL: Read Image from RTT

What if your gfxc returns NULL? You assume that gfxc->getTraits() should always have a valid reference pointer. Marlin Rowley Software Engineer, Staff Missiles and Fire Control 972-603-1931 (office) 214-926-0622 (mobile) marlin.r.row...@lmco.com

[osg-users] Read Image from RTT

Hi, I have tried to read image from RTT (where the image is "not attached", but available on buffer) using a osg::Camera::DrawCallback, the compilation is working, however the executable brings me a segmentation fault during image rendering. How can I solve this? Code:

[osg-users] Value of a variable in shaders?

All, Is there a way to examine variable values in shader code? I can't figure out this problem that we are having unless I can see the values in the shaders. Any help would be appreciated Marlin Rowley Software Engineer, Staff

Re: [osg-users] issues compiling 3.0.1

Hi Lonni, Laurens suggested fix is what I would have suggested too so I'd recommend you just apply these locally. For updating to the latest version, given that you are jumping from 3.01 to 3.6.x would be a big jump. Both are still part of 3.x series so broadly similar w.r.t public API, so for

Re: [osg-users] issues compiling 3.0.1

Hi Lonni, Both were fixed in 2012 by replacing false with NULL. Regards, Laurens. Revision: 5743d30dc1614ce4ee809cbc96d1b09c3778c4c2 Author: Robert Osfield Date: 2/9/2012 4:54:13 PM Message: >From Olaf Flebbe, "there are two ocurrences where pointer to bool is mixed with bool. Fixes warnings on