Re: OpenGL driver consumes 100% CPU
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: Wed, 3 Dec 2008 22:21:48 -0800 (PST)
On Dec 3, 6:16 pm, David Barrett-Lennard <davi...@xxxxxxxxxxxx> wrote:
Are you double-buffering?
Yes.
There are a lot of issues now. One is that the timer may fire while
you're waiting for the vertical refresh. As a result, you'll wind up
never waiting for the timer to fire and always having something for
your code to do. If there's no vertical retrace interrupt on your
hardware, this will burn CPU like crazy.
You need to turn off vsync. If you're getting tearing, you need to
figure out why -- the vsync is solving the problem the wrong way.
DS
.
- References:
- Re: OpenGL driver consumes 100% CPU
- From: David Schwartz
- Re: OpenGL driver consumes 100% CPU
- From: David Barrett-Lennard
- Re: OpenGL driver consumes 100% CPU
- From: David Schwartz
- Re: OpenGL driver consumes 100% CPU
- From: David Barrett-Lennard
- Re: OpenGL driver consumes 100% CPU
- From: David Schwartz
- Re: OpenGL driver consumes 100% CPU
- From: David Barrett-Lennard
- Re: OpenGL driver consumes 100% CPU
- Prev by Date: Windows, read/write mutex with semaphore + event.
- Next by Date: Re: Windows, read/write mutex with semaphore + event.
- Previous by thread: Re: OpenGL driver consumes 100% CPU
- Next by thread: Re: Multithreaded queue with wait event
- Index(es):
Relevant Pages
|