Beta 32, compiled from source on Linux/Ubuntu, amd64.

The random "window display lock" is back.
(as the previous "solution" was to get no window display usable, that's not so bad).

What is it: sometime, when the rendering window is activated, povray just draw the
frame
of the window, paint it black, does not display anything else but seems to perform the
rendering in separate threads. Whenever the mouse move over the frame of the window,
it
unlock the updating process and big parts of the rendered image pop up.

What it is not fine: if you do not move the mouse over the window, povray will just
stall.
This is more a problem for animation rendering, as getting the display might be a
wanted
bonus to monitor the rendering images, and you just fall into that lock: your expected
night rendering could very well be suspended on the first frame.
Moreover, the "move the mouse over" works only for local display. In previous beta
(not
yet checked with 32), with a remote display, there was no way to unlock povray.

Can someone provide some tutorial or samples of the SDL (the library used for the
displaying window) so as to check if there is not some missing function call, or a
re-ordering to perform ?
It seems that the issue might be a concurrency issue, a rendering thread trying to
update
the display before it is fully installed ?(only a plausible hypothesis, it's difficult
to
attach a debugger in such random situation).

Post a reply to this message