(05-30-2010, 11:59 PM)darkshadw Wrote: [ -> ] (05-30-2010, 03:41 PM)boogerlad Wrote: [ -> ]no you fools!
vps is the emulated cpu, and fps is emulated gpu. The speed counter is calculated through vps.
So you mean when you have like 4 280 GTX and a AMD Athlon 5600+ you will have full speed in every game oO, cuz that's bullshit ya know
No. VPS is the speed of virtual processor (that imitates the ibm chip on real wii). FPS is throughput of gpu emulation that imitates the ATI graphics chip input/output of real wii measured in frames per second. A wii game invokes dozens of cpu/gpu calls every second after you start it. You can see this in debugger.
That's why for example a game that isn't working fully will blackscreen & show active vps rates since it boots as normal, but fps is zero because it can't render anything on the screen since the game is trying to demand dx9, opengl or software renderer plugin to draw something it isn't programmed to do.
[
attachment=3423]
Example, where a new wii game is started on older revision, which invokes calls that were not emulated at the time. VPS speeds will be active but fps stays at zero
I really have no idea about WHAT IS VPS... maybe something like Video Processed per Second, since when it's at full speed, the game runs smoother (even though FPS is low, it just SLOWS DOWN), and if it's low, it starts to stutter the emulation... But one thing i'm sure about is: If your FPS is lower than VPS (except for 30/25 FPS limited games, like ZELDA TP) it's because something is slowing your system or you don't have enough graphic power to sync them both...
Since the 55xx updates, i've had this same kind of issue you're having.. and I found out 2 things: My download manager (Free Download Manager) was somehow slowing my system, even though it didn't consume any CPU % or more than 20mb RAM (out of my 3gb ¬¬), so Mario Kart Wii was running on 30fps/60vps as 100% speed and still slowing down (with auto frame limiter... if i disabled it, it would go up the speed, but it would be something like 40fps/80vps and supposedly 200% speed, which sucked anyway... After i turned off the FDM, i got an average of 50fps/vps with 81% speed on windowed 640x480 resolution... but when i go to my monitor resolution (1280x960) full screen, it would drop down to 30FPS....
So make sure to turn off ANY unnecessary program while running the emulator and also try lowering the resolution (if going Full Screen) in order to increase FPS...
The frame limiter uses a weird base to limit the FPS... When my games run under 20fps stable, it limits the FPS to 30... but if the game gets through those 30fps (at least 5 fps over 30FPS), and the audio plugin is limiting the speed (audio throttling), it takes the FPS limit to 60fps automatically, if the game is supposed to run at those speeds.... amazing... but weird... xD
@Ocean
Then why would the VPS be measured just as FPS, with a limit of 60 (or 50 for pal o.O)?! I really doubt it is the speed of any processor...
(06-01-2010, 12:53 PM)frango0010 Wrote: [ -> ]@Ocean
Then why would the VPS be measured just as FPS, with a limit of 60 (or 50 for pal o.O)?! I really doubt it is the speed of any processor...
VPS is "video per second" which refers to the refresh rate of the screen that is controlled by the ibm CPU on the wii and emulated by JIT recompiler or interpreter on dolphin.
It is a direct indicator of the speed of the emulated cpu. What boogerlad said is 100% correct.
FPS rate is controlled by the game (for example twilight princess 30, nsmb 60). VPS is always 60 on the real wii by default regardless of region, so if you have that, your rig has no problem emulating the game. If it goes higher, the virtual cpu is being emulated faster than on real wii and it causes absurdly fast gameplay which is not usable. You will then need to use either audio throttle or framelimiter to lower the speed to normal output of the game.
Also directx9 is incapable of field detection so it has no idea where your current frame ends or begins. FPS shown is therefore never 100% accurate when you use it on that plugin (unless you have full speed, and it's irrelevant). OpenGL has implemented field detection but it's much slower and uglier on dolphin so I prefer not to use it.
So is there a way to get an 100% acurate FPS display, maybe with FRAPS?
So what would, say, 50% FPS and 100% VPS mean? What about the other way around?
(06-01-2010, 10:35 PM)Chris8282 Wrote: [ -> ]So what would, say, 50% FPS and 100% VPS mean? What about the other way around?
Sometimes games deliberately run at a half framerate.
I'm not sure of the reasons where FPS would be higher than VPS.
Okay, but this was happening to me sometimes, and sometimes dont.... It's like the program was choosing what to make its priority... How could this happen??
(06-03-2010, 11:28 AM)Runo Wrote: [ -> ]Okay, but this was happening to me sometimes, and sometimes dont.... It's like the program was choosing what to make its priority... How could this happen??
The game sets fps rate for dolphin, not the other way around. So it can change depending on which games you play. Dolphin just obeys that by trying to render 30/60/50 frames per second.
Dolphin polls two different speeds: Amount of GL buffer swap and amount of XFB copy per second. When you start a game, it tells dolphin to copy data from XFB at a certain rate. Buffer swaps are controlled by dolphin and are defined in the source of
VideoInterface.
Unlike on the real wii, xfb and bufferswap is not correctly synced 100% of the time on dolphin. That's why you should enable framelimiter in dolphin options to imitate the real framerate the game is intended to be played at.
One think i know they can´t give a dam on FPS and VPS to work on 100% what's why the game never comes fixed and somethimes the emu frezzes at all. On Demul, PCSX2, Supermodel 3 and Model 2 have that problem solved.
Grow up Dolphin Deployments! Thanks a lot!
Bumping a two year old thread for no reason?
Check
Using grammar so poor that nobody can understand what you're trying to say?
Check
Complaining about issues that have been fixed for over a year?
Check
Spouting a bunch of nonsense that doesn't make any sense?
Check
Insulting the developers because you're having problems with beta software?
Check
This may just be a legitimate candidate for the dumbest post this year. It certainly meets all of the requirements.