Hi Steven,
On 6/09/09 1:53 AM, Steven Saunderson wrote:
I'm using OSG 2.8.0 and trying to synchronise my video frame generation with the
vertical retrace frequency so I get a smoother display. Update on vertical
retrace is
enabled. If I call viewer.frame() too early processing is stalled
Hi Ulrich,
Ulrich Hertlein wrote:
In general I don't believe it would benefit your ultimate goal (smoother
display): yes,
the display thread waits for retrace and thereby wastes some cycles. On the
other hand if
you call 'frame()' too late you might miss the next retrace altogether and
Steven Saunderson wrote:
My problem with using another thread is that the display thread loops busy
rather than idling so it's hard to share the processing time without taking
valuable time from the display thread.
How do you mean the display thread loops busy rather than idling? My
Chris wrote:
Chris 'Xenon' Hanson wrote:
How do you mean the display thread loops busy rather than idling? My
experience with
OSG running on a proper video driver is that wait for vblank should be a
mostly-idle
operation, not a spin-wait. What OS, driver, hardware, etc are you running
Steven Saunderson wrote:
Thanks for the ATI hint. I do have an old ATI card in this PC. I've just
tested the program in a PC with an nVidia card and it does wait-idle
somewhere in the frame() call. I'll setup another thread for my input
processing.
This was our original ATI-scragging
Hi,
I'm using OSG 2.8.0 and trying to synchronise my video frame generation with
the vertical retrace frequency so I get a smoother display. Update on vertical
retrace is enabled. If I call viewer.frame() too early processing is stalled
until the next retrace.
Is there any way for my
6 matches
Mail list logo
