Monday, December 8, 2008

Aaaaaarrrrggghhhhh!!!

Advice to Microsoft re: Direct 3D (slight return)...

WHY ON EARTH does the default presentation interval (D3DPRESENT_PARAMETERS::PresentationInterval) use the default system timer resolution? This has, like, very poor granularity, resulting in ultra-jerky screen updates. D3DPRESENT_INTERVAL_IMMEDIATE or D3DPRESENT_INTERVAL_ONE would be much more sensible options, IMO. OK, I'm sure that there's antiquated 1995-vintage hardware that only supports D3DPRESENT_INTERVAL_DEFAULT, but I'm also sure that it's possible to check for this at device creation (in the runtime, don't make stuff like this a developer requirement, we've enough to be doing without having to cope with this kind of thing) and fallback to default if the requested interval is unavailable.

It's not 1995 any more, folks! Ultra-caution gone mad, I tells ya!

How many people learning D3D must have given up when they hit this one, and didn't know how to proceed?

0 comments: