On 03/30/2012 09:48 AM, Ian Romanick wrote:
On 03/30/2012 03:12 AM, Jose Fonseca wrote:
----- Original Message -----
Certain applications don't call SwapBuffers before exiting. Yet,
we'd
really like to see a bitmap containing the final rendered image even
if
they choose never to present it.
In particular, Piglit tests (at least with -auto -fbo) fall into this
category. Many of them failed to dump any images at all.
Dumping one final image at context destruction time seems to solve
the
issue.
Another alternative would be for piglit and mesa should use/implement
http://www.opengl.org/registry/specs/GREMEDY/frame_terminator.txt , so
that the whole stack has a precise knowledge of where frames are.
Sounds like a handy extension!
Would having the piglit framework call glFrameTerminatorGREMEDY after
calling piglit_display be sufficient? That ought to be easy enough.
I was thinking that piglit_present_results() would call it, but yeah,
that sounds like it'd work too.
One the Mesa side, I think most apps only use glFrameTerminatorGREMEDY
in debug builds, so it might not be that helpful here.
*shrug*
That is the concern I have. We would like this to work for apps which
don't use this extension, so...we'll probably end up having to resort to
hacks anyway. :/
Oddly, it doesn't look like there's a way to detect whether or not an
application is planning to use this extension until the first
glFrameTerminatorGREMEDY call...
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
