PS3 Compatibility List - PS2 on PS3

Hmmm, i just realized the problem in what i wrote in my previous post, the codes with the 0x29 (background fog) and 0x2A (motion blur) are using an offset not aligned to 4 bytes boundary (but the config always patchs 4 bytes) so when using them individually are overwriting each other, the best way is what mrjaredbeta did by using all them together, but in the bloom, this way:

Code: 
POSITION|ORIGINAL|PATCHED

205F6600 00000000 00000001 // Cars environment maps
285F6600 00000000 01010101 // Bloom + Background fog + Motion blur + Unknown
305F6600 FFFFFFFF 00000000 // Lower car detail
3C5F6600 FFFFFFFF 00000000 // Lower traffic detail

E8511300 A8BA40AC A8BA43AC // Slow motion fix (crash fix)
80531300 A8BA60AC A8BA43AC // Slow motion fix (crash fix)
BCCD1300 A8BA60AC A8BA43AC // Slow motion fix (crash fix) doubtful, we are not sure if is needed

This is well alligned, it implyes we need to to have control of all that 3 switches together in a single code (either if we want to enable or disable something we need to indicate the value of all them in the code)

And btw, we dont know if there is another switch located at 0x2B5F6600 (to complete the group of 4 consecutive switches at 0x28, 0x29, 0x2A, 0x2B)... incase there is another switch in 0x2B we are overwriting it without knowing what it does
 
Last edited:
@Vika23 can you try this config in burnout 3 SLUS-21050 ?
Code: 
3D 00 00 00 57 44 00 00 0A 00 00 00 04 00 00 00
28 5F 66 00 00 00 00 00 01 01 01 01 30 5F 66 00
41 70 00 00 00 00 00 00 3C 5F 66 00 41 A0 00 00
00 00 00 00 E8 51 13 00 A8 BA 40 AC A8 BA 43 AC
00 00 00 00

Is something mrjaredbeta was trying in his last config, we are trying to figure the original data (that is going to be patched) for this 3 codes
Code: 
POSITION|ORIGINAL|PATCHED

285F6600 00000000 01010101 // Bloom + Background fog + Motion blur + Unknown
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail
E8511300 A8BA40AC A8BA43AC // slow motion fix (crash fix)

If the original data of the code is correct... then that code is going to work in HEN
There are 4 in total, we are sure the last one is right, but we have doubts about the others
 

Attachments

Last edited by a moderator:
sandungas said:
@Vika23 can you try this config in burnout 3 SLUS-21050 ?
Code: 
3D 00 00 00 57 44 00 00 0A 00 00 00 04 00 00 00
28 5F 66 00 00 00 00 00 01 01 01 01 30 5F 66 00
41 70 00 00 00 00 00 00 3C 5F 66 00 41 A0 00 00
00 00 00 00 E8 51 13 00 A8 BA 40 AC A8 BA 43 AC
00 00 00 00

Is something mrjaredbeta was trying in his last config, we are trying to figure the original data (that is going to be patched) for this 3 codes
Code: 
POSITION|ORIGINAL|PATCHED

285F6600 00000000 01010101 // Bloom + Background fog + Motion blur + Unknown
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail
E8511300 A8BA40AC A8BA43AC // slow motion fix (crash fix)

If the original data of the code is correct... then that code is going to work in HEN
There are 4 in total, we are sure the last one is right, but we have doubts about the others
Click to expand...

for check im use cfw 4.55 (yes so old))) and after then im try check hen\ han! im will try check config if just need converted via ps2classics GUI
 
Vika23 said:
for check im use cfw 4.55 (yes so old))) and after then im try check hen\ han! im will try check config if just need converted via ps2classics GUI
Click to expand...
Ok, dont worry, thx anyway, i asked because i thought you was ready to try it in a fast way, but now im realizing it was a bit soon to ask you about it because there are a few details that we are not sure, but in few days im guessing we wil have full control of all that commands for burnout 3
From that point... we need to decide what to enable or disable (mrjaredbeta can do a nice selection of codes)

But at some point we need to make a couple of test to "port" all this to the standard ps2_netemu.self (the ones without the kozarovv patch that bypasses the original data check)... this way the config will work in HAN, HEN, CFW, OFW, etc...

And btw, the config i posted for you is not going to work in your firmware version 4.55 im going to explain you why incase it happens again to you, take the bytes 5th and 6th of the config (5744), flip them (4457), and convert them to decimal with a calculator (17495), then compare that number with the table most at right in this link
https://www.psdevwiki.com/ps3/Talk:PS2_Emulation#PS2_Emulator_Types_and_Revisions

It means the config is only valid for firmware versions 4.78 or newer (so your firmware 4.55 is going to ignore it)

If you want the config to work in 4.55 then you need to change that number to 17277 or smaller (437D converted to hexadecimal... and 7D43 when bytes flipped)
So in plain word... in the config i posted you would need to replace the 5744 by 7D43
Or you can request to the person that is making the config to downgrade that number for your firmware version (or maybe even older to make it more standard)

Is just some of the commands that exists in the configs are only available since some firmware versions... so downgrading the configs could "break" some commands
 
sandungas said:
Ok, dont worry, thx anyway, i asked because i thought you was ready to try it in a fast way, but now im realizing it was a bit soon to ask you about it because there are a few details that we are not sure, but in few days im guessing we wil have full control of all that commands for burnout 3
From that point... we need to decide what to enable or disable (mrjaredbeta can do a nice selection of codes)

But at some point we need to make a couple of test to "port" all this to the standard ps2_netemu.self (the ones without the kozarovv patch that bypasses the original data check)... this way the config will work in HAN, HEN, CFW, OFW, etc...

And btw, the config i posted for you is not going to work in your firmware version 4.55 im going to explain you why incase it happens again to you, take the bytes 5th and 6th of the config (5744), flip them (4457), and convert them to decimal with a calculator (17495), then compare that number with the table most at right in this link
https://www.psdevwiki.com/ps3/Talk:PS2_Emulation#PS2_Emulator_Types_and_Revisions

It means the config is only valid for firmware versions 4.78 or newer (so your firmware 4.55 is going to ignore it)

If you want the config to work in 4.55 then you need to change that number to 17277 or smaller (437D converted to hexadecimal... and 7D43 when bytes flipped)
So in plain word... in the config i posted you would need to replace the 5744 by 7D43
Or you can request to the person that is making the config to downgrade that number for your firmware version (or maybe even older to make it more standard)

Is just some of the commands that exists in the configs are only available since some firmware versions... so downgrading the configs could "break" some commands
Click to expand...

If im try that config on HAN 4.82? Will work?
2020-05-13_21-37-05.png
 
Vika23 said:
If im try that config on HAN 4.82? Will work?
View attachment 25851
Click to expand...
The emulator is going to load it, but im not sure about the results, is better if i explain it by looking at this:
Code: 
POSITION|ORIGINAL|PATCHED

285F6600 00000000 01010101 // Bloom + Background fog + Motion blur + Unknown
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail
E8511300 A8BA40AC A8BA43AC // slow motion fix (crash fix)

In the first code in guessing the original data is 00000000, this ones are 4 switches, so im enabling all them with 01010101

The second and third code is what mrjaredbeta was trying in his last config, he is guessing the orginal datas are 41700000 and 41A00000 (because this is what can be seen in the comments of the pnach), but i have doubts if the endianess is right (so we need to flip the bytes 00007041 and 0000A041)

And the last code is the (awesome) fix found by mrjaredbeta that solves the huge problem that had this game... but in his last configs he was using 2 codes for fix this problem, and im using only 1 because im trying to catch the winner
I mean... we know one of that codes is doing the magic (or are both together ?)... we are not sure but i think is better to find which one is the responsible of the fix and play the game only with that one
And if at some point the problem returns... yeah then it means we need both
 
Last edited:
sandungas said:
The emulator is going to load it, but im not sure about the results, is better if i explain it by looking at this:
Code: 
POSITION|ORIGINAL|PATCHED

285F6600 00000000 01010101 // Bloom + Background fog + Motion blur + Unknown
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail
E8511300 A8BA40AC A8BA43AC // slow motion fix (crash fix)

In the first code in guessing the original data if 00000000, this ones are 4 switches, so im enabling all them with 01010101

The second and third code is what mrjaredbeta was trying in his last config, he is guessing the orginal datas are 41700000 and 41A00000 (because this is what can be seen in the comments of the pnach), but i have doubts if the endianess is right (so we need to flip the bytes 00007041 and 0000A041)

And the last code is the (awesome) fix found by mrjaredbeta that solves the huge problem that had this game... but in his last configs he was using 2 codes for fix this problem, and im using only 1 because im trying to catch the winner
I mean... we know one of that codes is doing the magic (or are both together ?)... we are not sure but i think is better to find which one is the responsible of the fix and play the game only with that one
And if at some point the problem returns... yeah then it means we need both
Click to expand...
ok im understand that is really hard) even u try speak russian)...ok im think im will be just tester but create configs not my faith)
 
kozarovv said:
His config seems to be fine, i looked into it.
Click to expand...

I wish I could test it myself and finally close this dispute but unfortunately my PS3 at an another apartment. But if this memory address works in PCSX2 then it should work in ps2_netemu and the problem on his side, right?
 
lex3a said:
I wish I could test it myself and finally close this dispute but unfortunately my PS3 at an another apartment. But if this memory address works in PCSX2 then it should work in ps2_netemu and the problem on his side, right?
Click to expand...
Yeah, mipmap is so specific thing, that unpatched affect all emus that not emulate it. That how i test my mipmap patches since i no longer own ps3. I just prefer to test in hardware mode with turned off mipmaps, but software mode with turned off mm should bring the same result.
 
So im run burnout 3 on my CFW 4.55. Im think its work becouse as im remind if config not work, you cant save game and menu is corrupt
Game work great and full speed as im think. Im try just first race. Im will leave config that im was use for convert
 

Attachments

@sandungas @Vika23
The correct config should be:
Code: 
POSITION|ORIGINAL|PATCHED

285F6600 01010101 00000101 // Bloom + Background fog
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail
E8511300 A8BA40AC A8BA43AC // slow motion fix (crash fix)
The first code originally looks like "01010101" since everything is enabled. Disabling the first two "00000101" makes it so the bloom and background fog is disabled. I kept the motion blur on because I think it is important for the game and doesn't cause a noticeable difference in performance.

Anyways, I am going to test it out with unpatched emu sometime today, so if @Vika23 doesn't get to it then I will!
 
mrjaredbeta said:
@sandungas @Vika23
The correct config should be:
Code: 
POSITION|ORIGINAL|PATCHED

285F6600 01010101 00000101 // Bloom + Background fog
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail
E8511300 A8BA40AC A8BA43AC // slow motion fix (crash fix)
The first code originally looks like "01010101" since everything is enabled. Disabling the first two "00000101" makes it so the bloom and background fog is disabled. I kept the motion blur on because I think it is important for the game and doesn't cause a noticeable difference in performance.

Anyways, I am going to test it out with unpatched emu sometime today, so if @Vika23 doesn't get to it then I will!
Click to expand...
2020-05-13_21-53-20.png

Im was use that config
Also will share u pkg in message if you want
 
@mrjaredbeta im reading again our talk and im realizing i missed some important info you wrote, sorry, it looks im going late, lol
So the complete list of speedhacks is like this, right ?, this would be like the "top speed" config (and the most invasive too because maybe is disabling visual effects that are not needed to be disabled)
Code: 
POSITION|ORIGINAL|PATCHED
205F6600 01000000 00000000 // Cars environment maps OFF
285F6600 01010101 00000001 // Bloom OFF + fog OFF + blur OFF + hud ON
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail

So some of your commands in the old burnout configs patching an 1 on top of the original data, and my misunderstanding where i said some features was disabled by overwriting them with the value 1 was wrong, everything is disabled with zeroes, right ?
And the 1 at the end of the value 0000001 is because we dont want to "kill" the hud, right ?

And from the critical codes this one was the winner, nice :encouragement:
Code: 
POSITION|ORIGINAL|PATCHED
E8511300 A8BA40AC A8BA43AC // slow motion fix (crash fix)
 
Last edited:
@sandungas
These whole past few pages of this thread have been a blur...

Anyways, I messed up again about the environment maps and was right the first time...here's the correct code:
Code: 
POSITION|ORIGINAL|PATCHED
205F6600 01010101 00010101 // Cars environment maps OFF
285F6600 01010101 00000001 // Bloom OFF + fog OFF + blur OFF + hud ON
305F6600 41700000 00000000 // Lower car detail
3C5F6600 41A00000 00000000 // Lower traffic detail

I will test soon and see if it works on unpatched netemu.
 
You must log in or register to reply here.

Similar threads

Back
Top