Dakota Ridge
unread,Oct 18, 2009, 12:12:01 PM10/18/09You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to
I was about to convert my application from DX9 to 10 on a Vista version,
since IDirect3D9::Present is getting a C0262111 error under Vista, which
nobody has ever heard of before, it's 100% undocumented, and everybody is
avoiding the subject like the plague. But now it's looking like this
conversion will kill the entire purpose of the app. I'm reading about half
the people on Earth having major problems with refresh rate locks under DX10.
This app is a more-or-less fringe thing that relies on tearing (incessantly)
to produce visual effects, rotating certain images at very high speeds. The
app is pure assembly language and under XP, which doesn't care about my Intel
Quad Core, with very slow latency 9 memory (only 2 gigs) and a midrange
graphics card, I'm getting frame rates of well over 12,000 fps. This is what
produces the effects that the program produces. But I can't do the refresh
rate lock thing. That would destroy the entire program. I've read about the
-DX9 switch and that might save me since this mysterious PRESENT error is not
going to be identified, much less resolved; I really need to do the
conversion over to DX10 for Vista but if I can't control the refresh rate,
there is no point. Any thoughts?