Sign in to follow this  

ati radeon 7000 cards directx 7.0

This topic is 4015 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

When rendering in DX7.0 on an ATI Radeon 7000, there is a slight to severe delay in updating the Rendering with the keyboard input. This only happens when the FPS goes down to 5-10 frames per second, and it only happens on the ATI RADEON 7000 card. For instance, I am drawing a full screen textured rectangle 15x per game cycle. THe FPS drops to around 7FPS, and the mouse/keyboard input is several seconds behind. Why does this happen?

Share this post


Link to post
Share on other sites
If you use a single loop for your application then the performance of all parts (e.g. rendering and input) will be tied together - if one is slow they'll all be slow.

It might well be worth seperating the main components into multiple threads..

hth
Jack

Share this post


Link to post
Share on other sites
Assuming you're using Windows events for the mouse input, try consuming all of them before moving to the next frame. Otherwise if you get more than one event per frame they'd accumulate.

Share this post


Link to post
Share on other sites
The problem is not that it's slow. I made it intentionally slow. The problem is, there is an unsynchronized effect between INPUT and What you see.

The input occurs inside the Draw function. Right before it draws, I get the input, either keyboard or mouse. If I move left, even if the FPS is 7frames per second, I'd expect the image to move instantly. But it moves 2 seconds later.

This also happens in Blitz3D, which uses D3D and DX 7.0. I think this might be a driver issue, because this doesn't happen on TNT cards, or Intel.

But this doesn't happen on my other cards.

Share this post


Link to post
Share on other sites
Problem solved.

There was a bug with RADEON driver that was buffering draws, causing draws to be behind input.

Locking and unlocking primary surface emptied the buffer, fixing this bug.

Share this post


Link to post
Share on other sites

This topic is 4015 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this