(06-01-2013, 02:52 AM)Koji Wrote: I think you misunderstand... VU cycle stealing will NOT give you results like a real PS2, it will give you WORSE results since it's akin to emulating an underclocked PS2.
The reason why VU cycle steal works so well for SotC is because it has an unlocked framerate. Because of that, an underclocked state allows for frame skipping (most PS2 games are hard coded to a frame rate and thus, if the system can't keep up causes slowdowns instead of frame skips).
Yes, SotC pushed the PS2, but if you can't emulate it without using EE and VU cycle hacks, you're not even getting on par performance.
Not wanting to make a case, just to help understanding what VU cycle stealing does.
EE (the actual PS2 CPU) communicates with the VUs passing the bulk of floating point data (mainly the vectors for graphics processing). If the VU becomes idle it still has to wait for the new data batch from the EE which may be processing something else or even waiting response from some module till the time to return the attention to VU comes again.
VU cycle stealing changes this force interrupting EE to send it data wherever the VUs module needs them. This helps increasing FPS because graphics (vector processing) is normally more demanding than common integer and logic operations.
If not in excess (and this depends greatly on the game), those cycles stolen from EE don't prevent it from doing it's job in due time and little to no collateral effects come from VU cycle stealing hack. Yet, it may interrupt EE when shouldn't and so this may cause the general game flow to slowdown.
The "curious" thing is when that hack is too much the game's flow slows down. The PCSX2 FPS is still increased but the pace the action happens in each frame decreases and may be too much to be compensated by the FPS increase... when this happens the game becomes sluggish or/and laggy, a known phenomenon from excess VU cycle stealing and leads people to call it fake FPS (albeit the FPS is what is seen... just the pictures on each frame are being drawn slower than should).
So, VU cycle stealing is not about changing processor clocks... just does what it claims... steals cycles from EE that EE would be using to do something else so to force EE to send data for the VUs to crunch.
PS: What makes things more confuse is because that 60 FPS needed by PCSX2 are indeed an emulation of what would be the PS2 refresh rate, not directly related with the actual FPS on PS2 which can't be directly emulated as FPS but emulated as painting the actual picture to go with each PCSX2 frame. If the (motion in the) pictures are being painted too slowly on the frames, the FPS is high but the "images motion" is reduced.