[osg-users] PixelBufferObject doesn't work in a osgQt::GraphicsWindowQt ?

2012-07-25 Thread Il Furbone

Hi!
I'm doing the porting of my 3d-application from OSG+wxWidgets to OSG+Qt.
My application uses heavily PixelBufferObject (multi pbo) to do the 
readback from GPU to CPU and it works fine.
But during the porting I discovered that the PixelBufferObject doesn't 
work.
As a further test I put the osgscreencapture sample in a 
osgQt::GraphicsWindowQt and I found the same problem. My new sample 
works with --no-pbo (that is with a simple READ_PIXELS) but it doesn't 
work if I use --single-pbo or --double-pbo.
What I have observed is that the buffer returned by glMapBuffer isn't 
NULL but is all black :


...

GLubyte* src = (GLubyte*)ext->glMapBuffer(GL_PIXEL_PACK_BUFFER_ARB,
  GL_READ_ONLY_ARB);
if(src)
{
memcpy(image->data(), src, image->getTotalSizeInBytes());
ext->glUnmapBuffer(GL_PIXEL_PACK_BUFFER_ARB);
}

...

After that the image is all black.

Note: My OS is Windows-7 (32 and 64 bit) and I use an NVidia Quadro 3700 
or  4000.


Anyone has a clue?

Cheers,
Sergio

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] pixelBufferObject

2009-06-20 Thread Alena Bacova
Hi Robert,
there aren't any errors, it works fine on both platforms, I was just curious
what determines what kind of support is there. I'm trying to implement osg
on our cluster running rocks and sage (www.*evl*.uic.edu/cavern/*sage*/) and
I'm looking for warious ways how to make it more efficient, thus the
question.

Thanks
Alena

2009/6/20 Robert Osfield 

> Hi Alena,
>
> On Fri, Jun 19, 2009 at 10:06 PM, Alena Bacova wrote:
> > Hi all,
> > I was recently playing with osgscreencapture and was wandering what is
> > responsible for different PBO support, one of my machines supports
> > single_pbo ( centos) and second one supports double_pbo (windows xp), is
> it
> > driver dependant or hardware dependant, or os dependant? or what am I
> > missing?
>
> I am surprised you are reporting a difference as it should work the
> same on both platforms if you have PBO support.  What is making you
> think there are differences?  Could you give an example of what errors
> you see?  Could you also provide info on the hardware, OS and OpenGL
> drivers you are using?
>
> Robert.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] pixelBufferObject

2009-06-20 Thread Robert Osfield
Hi Alena,

On Fri, Jun 19, 2009 at 10:06 PM, Alena Bacova wrote:
> Hi all,
> I was recently playing with osgscreencapture and was wandering what is
> responsible for different PBO support, one of my machines supports
> single_pbo ( centos) and second one supports double_pbo (windows xp), is it
> driver dependant or hardware dependant, or os dependant? or what am I
> missing?

I am surprised you are reporting a difference as it should work the
same on both platforms if you have PBO support.  What is making you
think there are differences?  Could you give an example of what errors
you see?  Could you also provide info on the hardware, OS and OpenGL
drivers you are using?

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


[osg-users] pixelBufferObject

2009-06-19 Thread Alena Bacova
Hi all,
I was recently playing with osgscreencapture and was wandering what is
responsible for different PBO support, one of my machines supports
single_pbo ( centos) and second one supports double_pbo (windows xp), is it
driver dependant or hardware dependant, or os dependant? or what am I
missing?

any links to this topic are welcome


Thanks

Alena Bacova
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org