Thanks for all the answers. I feared that nobody will be interested, but it's nice to see that so many people contribute to it.
@R. Belmont:
Now that I've understood microstuttering a bit better thanks to Firehawke, I doubt that this is the phenomenon in my case. As Calamity already said: The delay is pretty constant. For Direct3D I did it 20 times, 10 times with SMB and 10 times with SF2. And it was always a pretty constant rate. Also, is microstuttering limited to vsync and triple buffering? Because without that, Direct3D works perfectly fine.
Another interesting thing: I believe that Direct3D and vsync work fine in windowed mode. Only in fullscreen do I feel a delay. In the moment it's just a feeling, but I will do more tests about it. Last time I only used fullscreen mode, so this time I will check with window mode also. That means my next tests will be:
Direct3D with no filter, with vsync and with triple buffering in fullscreen mode (for reference purposes and to see that the results are still the same as last time)
Direct3D with no filter and with vsync in windowed mode
I won't do DirectDraw anymore because we already know that it doesn't produce lag on my system. And the combination window + triple buffer doesn't remove any tearing, so it's unnecessary.
I will post the results as soon as I'm finished.
@smf:
> I'd test it with an NVidia card and if that doesn't suffer from direct3d vsync lag
> then report the problem to ATI.
I will have access to an NVidia card in two weeks. I'll do tests with it too and post it here.
Additionally, I can check the stuff on an Intel card.
|
Index 
Flat 
Re: Flip Queue Size
Reply
Re: Flip Queue Size
