Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 5 of 5

Thread: Read back problem.. MX 440

  1. #1
    Intern Newbie
    Join Date
    Aug 2008
    Posts
    35

    Read back problem.. MX 440

    I have another problem on MX 440 card.

    We try to save a few rendered frames into a video stream.

    We first do off-screen rendering to a hidden window and read back from it. The read back data is wrong or corrupted only on MX440 so far. It seems as if the hidden window area of the desktop (frame buffer) gets read back. As a result, if I move another window (e.g. taskmgr or notepad) over the hidden window area while it is saving, those windows are seen in the saved result. What's more, if screen saver starts while the application is saving, that portion of the screen saver corresponding to the hidden window gets saved as well.


    So, I made the hidden window SHOWN. It's shown upon creation and I can see the rendering works fine while it's saving. But, if I still move another window over my rendering window, it's reflected in the read back or saved result. Based on this, I guess it's a read back issue on MX 440 card.

    Any suggestions? Thanks!

  2. #2
    Super Moderator OpenGL Lord
    Join Date
    Dec 2003
    Location
    Grenoble - France
    Posts
    5,655

    Re: Read back problem.. MX 440

    Unless you use pbuffers or FBO, this is normal behaviour.

  3. #3
    Senior Member OpenGL Pro Zengar's Avatar
    Join Date
    Sep 2001
    Location
    Germany
    Posts
    1,979

    Re: Read back problem.. MX 440

    To further explain ZbuffeRs answer: the OpenGL specification states that hidden/overlapped parts of a window contain undefined data.

  4. #4
    Super Moderator OpenGL Lord
    Join Date
    Dec 2003
    Location
    Grenoble - France
    Posts
    5,655

    Re: Read back problem.. MX 440

    Sorry, my reply was indeed too terse for the beginner board, I have to be more carefull

  5. #5
    Intern Newbie
    Join Date
    Aug 2008
    Posts
    35

    Re: Read back problem.. MX 440

    Thanks guys. This problem is solved. Something messed up when we create the pbuffer (wglCreatePbufferARB()).

    By the way, pbuffer is supported as long as the extension "WGL_ARB_pbuffer" is present on Windows (since OpenGL v1.1), correct?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •