Closed GoogleCodeExporter closed 9 years ago
How do you know your game's clock frequency? By some plugins told you?
PRO has to cheat about the actual frequency to avoid some games like Tekeen 6
freezing. So the frequency the plugins told you is not real. If you are still
unrelieved, try to set 75/33 and see if your game are still running smoothly.
Original comment by outma...@gmail.com
on 4 Sep 2011 at 1:09
I'm quite surprised by that subtle technical detail you provided. Indeed, even
though PSP-Hud reports 222 MHz in-game, but after setting CPU CLOCK GAME to
75/37, the game slowed down to a crawl.
The point of comparison I made, which eventually led me to thinking this might
be a bug, was with LME, where the plugin accurately reports speed setting, thus
WYSIWYG-ing with the VSH menu.
I guess other CFWs implementation are straightforward, whereas PRO tries to be
"smart" about it.
This ticket can now be closed.
Original comment by c0d3r5unltd@gmail.com
on 4 Sep 2011 at 1:48
Another way to find this out is by installing the plug-in CWcheat.prx then set
the CPU CLOCK GAME to 333/166 in the VHS menu, load the game and load your save
or whatever,
hold select for 3 second to open CW Cheat in-game menu, go to setting and
select yes to both frame counter and show current cpu load, even though CWcheat
and any other plug-in reports the cpu speed is set to 222/111 try changing the
speed to 33/16 then CWcheat and any other plug-in should now report 33/16 at
what point when you return to the game, the game should crawl and the frame
counter should drop compared to before and the current cpu load should go to
max right wrong, the speed and everything would be unaffected so the VHS menu
speed setting does work but in a different way
hope this helped
Original comment by cid...@hotmail.com
on 12 Sep 2011 at 2:30
This is perfectly working (verified in the pro C 6.20 fix 2).
Original comment by devnonam...@gmail.com
on 15 Jun 2012 at 3:46
Issue 287 has been merged into this issue.
Original comment by devnonam...@gmail.com
on 15 Jun 2012 at 4:17
Issue 377 has been merged into this issue.
Original comment by piotrekhenry
on 23 Jan 2015 at 6:35
Original issue reported on code.google.com by
c0d3r5unltd@gmail.com
on 4 Sep 2011 at 10:16