Re: flickering skybox (newb question)
- From: "ZMan" <zman@xxxxxxxxxxxxxx>
- Date: Sat, 19 Nov 2005 15:13:10 -0800
Oooops, good catch. Phill is of course correct.
http://www.thezbuffer.com - News and information for Managed DirectX
"punkrock" <punkrock@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> Check your math, ZMan. 1000 / 50 = 20, not 200. And 50ms is usually more
> enough to draw a frame (and do some AI, etc). Most games run ~30fps which
> only 33ms per frame (aren't video cards great?), shared with AI, network
> code, and the rest of the system, of course.
> Now if we're talking about a simple low-framerate app that runs in
> mode, isn't built around the tightest possible loop, and has to share the
> with a few web pages, a media player, five to ten games of Minesweeper,
> then obviously playing nice and giving the rest of the system as much CPU
> it can is more important than frame rates, in which case I totally agree
> what you say about the Timer, it's a great way to go about doing this
> it allows Windows to throttle your app at the message queue level, and in
> that case I wouldn't set the timer's resolution any lower than 100ms.
- Prev by Date: Re: Screensaver project - Compress File
- Next by Date: Re: Caps.MaxActiveLights = 0?
- Previous by thread: Re: flickering skybox (newb question)
- Next by thread: Applying Texture Mapping to a Mesh.Sphere