Hacking 6.xx PRO CFW Release Thread

[zygie]

Changing up to 333mhz removes the slowdown in Burnout's menus, and lowering the clock speed in-game makes it all laggy.

It looks like it's just B9's settings for it and are non-functional.

Apparently PRO's supposed to work like that. They did fix the 300/150 cap in the recovery menu though, but it's probably in the nightly builds. I was confused about this as well at first, might as well try it.

 

[xist]

So can anyone confirm that if you decrease the clockspeed in the VSH or recovery menu down to the very minimum, and then start a game, that the changes are just ignored?

I can check 6.35PRO B5 a bit later (yes my Go is still on the first CFW i put on it...deal with it) but B9 would be a nice place to start.

 

[zygie]

I'm on 6.20 PRO-B9 on a Go, and although I don't have any plugins that let me see the clock speed in-game, here's what I did:

Test 1:
1) Set CPU CLOCK GAME to 75/37. (VSH menu)
2) Run Burnout Legends.
3) Start race.

The game slowed down so much I could barely do anything, while it wasn't as choppy as I would expect it was really, really slow.

Test 2:
1) Set CPU CLOCK GAME to 333/166. (VSH menu)
2) Run the same game.
3) Start race.

The game ran wonderfully without any slowdowns that could be noticed at the default clock speed.

So while my tests lack some information (in-game display of clock speed) I would say changing it via the VSH menu affects the clock speed of the game.

 

[trance]

I keep CWCheat activated, to control CPU rate, but that's just me

 

[xist]

So while my tests lack some information (in-game display of clock speed) I would say changing it via the VSH menu affects the clock speed of the game.

Which contradicts the gist of that solution posted on the PRO project page in the closed topic posted earlier.

 

[Rydian]

Yup, lowering the clock speed to 100mhz and then running Burnout Dominator results in a slow game (it's even laggy and has screen tearing in the menus).

Makes sense.

 

[xist]

Yup, lowering the clock speed to 100mhz and then running Burnout Dominator results in a slow game (it's even laggy and has screen tearing in the menus).

Makes sense.


Well logically but...

QUOTEHow 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.

...by a PRO team member clouds matters. If you reduce the clockspeed and then check using the cheat engine what does it report?

 

[zygie]

Which contradicts the gist of that solution posted on the PRO project page in the closed topic posted earlier.

Actually, it supports it. According to outmatch (the PRO team member) that if you set it via the VSH/recovery menu it would affect the clock speed of the game, but it wouldn't reflect in the information provided by plugins ("PRO has to cheat about the actual frequency to avoid some games like Tekeen 6 freezing.") What's missing in the tests Rydian and I did was what clock speed the plugins would show. If by any chance it was still the clock speed set by the game, then outmatch's explanation would be perfect; however, if it did reflect the clock speed we selected, we'd have some inconsistencies.

EDIT: Put CWCheat in and checked in-game clock speed while VSH menu game clock speed is set at 75/37: CWCheat reports it at 222/111 even though the game's laggy as hell.

 

[Rydian]

If you reduce the clockspeed and then check using the cheat engine what does it report?

It still reports the native clock speed for the game/program, which is why I assumed it wasn't working when I tried and posted earlier, however now that I read that link and tried lowering the clock speed I could see that it worked (I had only tried raising it for the first test).

 

[realveemon]

Ok... 2 questions.... both pops related...

1. With a psp 2k that is running m33... Will the 4.01 pops on m33 work the exact same as 4.01 pops on pro? I know its a port but i use that psx-psp wiki.

2. What would be better with the pops, 6.39PRO or 6.60PRO ? I hear 6.60 is unstable but would like to hear peoples thoughts and stuff...

Thanks to the people keeping the scene alive of course

 

[ars25]

Ok... 2 questions.... both pops related...

1. With a psp 2k that is running m33... Will the 4.01 pops on m33 work the exact same as 4.01 pops on pro? I know its a port but i use that psx-psp wiki.

2. What would be better with the pops, 6.39PRO or 6.60PRO ? I hear 6.60 is unstable but would like to hear peoples thoughts and stuff...

Thanks to the people keeping the scene alive of course

1 yes it's the same

2 depends on you likes as popsloader works like a charm with both firmwares

 

[squall14716]

I bought a PSP 1000 (haven't gotten it yet). Is there any reason to use 6.20/6.39 over 6.60, or should I just go with the latest?

 

[Rydian]

I bought a PSP 1000 (haven't gotten it yet). Is there any reason to use 6.20/6.39 over 6.60, or should I just go with the latest?

On a 1000 not really since the other 6.x versions can have a different method of permanent patch.

 

[KevFan]

6.20/6.35/6.39/6.60 PRO-B10 released
http://code.google.com/p/procfw/downloads/list

 

[Creqaw]

So how exactly do you update from B9 to B10?

 

[Augusta]

So how exactly do you update from B9 to B10?

Delete anything PRO-B9 related, place PRO-B10 files on your stick.

 

[Creqaw]

So how exactly do you update from B9 to B10?

Delete anything PRO-B9 related, place PRO-B10 files on your stick.

But do you need to go back to official 6.20 again before re-doing the B10 update?

 

[pokefloote]

I just updated straight from B9.

 

[Creqaw]

I just updated straight from B9.

So just these steps from the softmod guide?

Now to install the 6.20 hack!

Download 6.20 PRO (Latest Version).
Copy the 620PRO_Permanent and PROUPDATE folders to /PSP/GAME/.
Run the 6.20 PRO Updater on your PSP and when it runs press X to install and launch the temporary 6.20 hack.
After the PSP restarts, run the 6.20 PRO Permanent Patch.
Press X once to choose to install, then press X again to choose to test it.
If your PSP successfully rebooted after the test, then run the permanent patch again, but this time press X and then Circle to install.
If your PSP did not successfully test, remove your /seplugins/ folder from your memory stick and try again (because not all 5.x plugins work on 6.x).

When you're done, you can delete the files off of your memory stick, since the hack is stored on the PSP itself.

 

[pokefloote]

I just updated straight from B9.

So just these steps from the softmod guide?

Now to install the 6.20 hack!

Download 6.20 PRO (Latest Version).
Copy the 620PRO_Permanent and PROUPDATE folders to /PSP/GAME/.
Run the 6.20 PRO Updater on your PSP and when it runs press X to install and launch the temporary 6.20 hack.
After the PSP restarts, run the 6.20 PRO Permanent Patch.
Press X once to choose to install, then press X again to choose to test it.
If your PSP successfully rebooted after the test, then run the permanent patch again, but this time press X and then Circle to install.
If your PSP did not successfully test, remove your /seplugins/ folder from your memory stick and try again (because not all 5.x plugins work on 6.x).

When you're done, you can delete the files off of your memory stick, since the hack is stored on the PSP itself.

Yup! But since I already had the perm patch I didn't need to run it again, I just ran the updater. Takes like 3 seconds.