Emulator Issues #1279
closed
Vysnc causing speed regression (OpenGL plugin)?
0%
Description
Before you start saying "it's vsync of course it's going to run slow", read
the entire issue first, ask more questions, test it, isolate any
possibilities, then you can state what's on your mind.
What steps will reproduce the problem?
- Open the OpenGL preferences, and enable Vsync and fullscreen (use your
max resolution for good measure) - Close/Reopen Dolphin
- Load a graphically intense game
What is the expected output? What do you see instead?
For a PC as decent as mine, I kinda expect vsync to not have such a big
frame impact as I thought. For example, using vsync in Wind Waker makes it
feel like a PAL50 game, with some normal speeds in areas with less objects.
What version of the product are you using? On what operating system?
Dolphin x64 3950 (for current OpenGL comparisons) and Dolphin x64 3626 with
the last working version of the DirectX plugin. Windows 7 x64 7600.
Please provide any additional information below.
Now here's the meat of the whole issue. Using the old DirectX plugin with
the most recent revision that will work with it - having all the high
settings enabled, fullscreen, with vsync on will cause no speed regression
(or in other terms - no choppyness). Of course, I'm not dumb, I know that
DirectX is old and hasn't worked in ages. However, the whole point of the
issue is to state that having Vsync enabled on the OpenGL causes games to
be a little stuttering even with the most high end machines. For example, mine:
Windows 7 x64 7600
NVidia GeForce 9800 GTX+ (over clocked, 780/2000/2400 (or 1200, I forget))
C2D Wolfdale 8400 series 3.00GHZ (over clocked to 3.80GHZ)
4GB RAM DDR2
nForce 680i lt sli motherboard
SoundBlaster Live! 24Bit (not the external one, the cheap internal one for
like 20 bucks)
This machine can run everything fine/perfect, except Dolphin when you want
to use high end settings. I don't think it was always like this, either,
because I remember once the OpenGL did have AA and stuff it worked fine. I
don't know when/where it happened, but I believe the OpenGL plugin needs to
be seriously looked at some more.
It's difficult to figure out where to begin on this. So please, before
labeling or shuffling (haha, no pun there) this issue away - please ask
questions, and I'll try to bring more information as much as possible.
Hopefully with the more information I bring, you can figure out where the
problem is. :)
Let me know. Thank you!
Updated by knuckles500 over 15 years ago
chaa~
If it helps, here are both 32bit and 64bit version of R3626 with working DX9. Please
don't hurt me if I accidentally included something I shouldn't:
32bit:
http://dl.getdropbox.com/u/38216/dolphin%20r3626%2032bit%20working%20dx9.7z
64bit:
http://dl.getdropbox.com/u/38216/dolphin%20r3626%2064bit%20working%20dx9.7z
Updated by knuckles500 over 15 years ago
Sorry to triple post here, but here's some reassurance to me that it's not my end -
it's the plugin itself:
http://forums.dolphin-emu.com/thread-3027-post-27168.html#pid27168
Well I kinda hinted that it wasn't a core related problem in the beginning - so that
just means that it must be a problem with the OpenGL plugin itself. I hope this get's
looked at soon. :)
Updated by knuckles500 over 15 years ago
Bah, gay.
I tried the earliest revision I could find with vsync and aa finally added to the
OpenGL plugin (R2645) and you know what, it still sucks. In fact, I say it runs WORSE
than what we have today.
I think this means that it's a NVidia driver issue. WSERJG$REJIGHGJHRERJHIEJH
Which could also explain why the high settings worked for the DirectX plugin.
However, I'm not sure if this is because 190.38 itself is bad, or the drivers for
Windows 7/Vista are bad, or the drivers for x64 Windows are bad. I don't know. But
whatever it is, I guess we now know that there's a higher possibility of it being a
driver issue more than a plugin issue. I guess it could still be a plugin issue still
(maybe the plugin just isn't keeping up with the times or something?), but, whatever.
I really don't know what to say. :\
I wish I could've tested Dolphin while I still had the 180 drivers under linux
(Ubuntu 9.04 AMD64) - but I had to go ahead and update to the 190 series drivers once
I reinstalled. God dammit.
Updated by knuckles500 over 15 years ago
Okay, I finally figured something out.
Setting the screen refresh to 60 will make vsync run the way it's supposed to.
Setting it higher than 60 like say 75, will cause the game to either stutter or
bounce around in frame rate. So this takes care of the vsync problem.
Now there's still an issue with AA - and from a friend, I know why. The AA part of
the OpenGL code handles it so that everything that's passed through the video card
has AA - instead of being selective. I don't know if the DirectX plugin did this with
AA, but it might be a lot less intensive to make it so that you only put AA on
specific things rather than the entire image. That's just my guess though, I haven't
actually looked at the code - but it does seem to make sense.
Waiting for a response so I can get confirmation either or not this is still an issue.
Updated by Anonymous almost 15 years ago
- Status changed from New to Invalid
Looks like you figured out it was not really a dolphin bug (turned out to be a driver
bug?)
Updated by wespipes69 almost 15 years ago
I don't know...I can't change my refresh rate on my monitor (always at 59hz) and I
just can't use Vsync because of these slowdowns. There's gotta be something that can
be done, no?
Updated by townnet8 almost 13 years ago
use opengl+vsycn and enable your graphic card Tripple buffering= no stutter.