PS3 Compatibility List - PS2 on PS3

from compatability list for parappa the rapper 2:

NTSC-U version hangs on loading screen but works with ManaGunZ Config file (*GX*). PAL version boots but hangs after a short amount of play time.
 
from compatability list for parappa the rapper 2:

NTSC-U version hangs on loading screen but works with ManaGunZ Config file (*GX*). PAL version boots but hangs after a short amount of play time.
At this point that report about the PAL version smells fishy, the reason why im saying this is because the configs for EURO/USA are identical

This was a "feature" of the internal structure used to store this configs inside the .self
It looks in this case there are 2 entries in the "config table" and everyone have a pointer... but both pointers are the same value (so the same config data can be loaded by 2 different game ID's)

Compare them for GXemu .self, the value Commands offset : 345790 is the pointer:
Code:
Title : Parappa the Rapper 2
Game ID : SCUS_971.67
Hash : 0x3E8995D89D
Hash Offset : 33F1A0
Commands offset : 345790
Commands count : 0x2
	[GX] Command ID : 0x09
	[Net] Command ID : 0x0B
		Data Offset : 003457C0
		Data Number : 00000001
			Sector : 0000026A
			Offset : 000004DC
			Size : 00000004
			Patched data offset : 0x51D338
			Patched data : 00000000
			Original data offset : 0x51D330
			Original data : 0A008014
	[GX] Command ID : 0x13
	[Net] Command ID : 0x15
Param : 00000004
Code:
Title : PaRappa the Rapper 2
Game ID : SCES_504.08
Hash : 0x895149007D
Hash Offset : 340A48
Commands offset : 345790
Commands count : 0x2
	[GX] Command ID : 0x09
	[Net] Command ID : 0x0B
		Data Offset : 003457C0
		Data Number : 00000001
			Sector : 0000026A
			Offset : 000004DC
			Size : 00000004
			Patched data offset : 0x51D338
			Patched data : 00000000
			Original data offset : 0x51D330
			Original data : 0A008014
	[GX] Command ID : 0x13
	[Net] Command ID : 0x15
Param : 00000004




Edit:
In SOFTemu .self happens the same, but here the pointer is Commands offset : 579DD8
Code:
Title : Parappa the Rapper 2
Game ID : SCUS_971.67
Hash : 0x3E8995D89D
Hash Offset : 39EA20
Commands offset : 579DD8
Commands count : 0x1
	[SOFT] Command ID : 0x13
	[Net] Command ID : 0x15
Param : 00000014
Code:
Title : PaRappa the Rapper 2
Game ID : SCES_504.08
Hash : 0x895149007D
Hash Offset : 39FC80
Commands offset : 579DD8
Commands count : 0x1
	[SOFT] Command ID : 0x13
	[Net] Command ID : 0x15
Param : 00000014
 
Last edited:
I think that's placebo effect. 0x12 is per offset config, on VU, and on EE. So this need a lot of luck to work, because config work only when CTC2, or CFC2 opcode is found at EE offset. That's not all, because CRC need match to make config work. So there is actually no chance all that hits correct offsets, and CRC match.
You can check what code is on
0x399cb8
0x399d70

@kozarovv Yes I think that you have reason, because this config not solve that "freeze or crash" in Digimon Rumble Arena 2 PAL, because i while was tested the game for example yesterday can the game run "perfectly", but the next day this game returns to the same problem, sorry friends I'm begin to belive that this game not have a "true solution", the same problem in NTSC version I tested with sponge bob config but the same, the game run perfeclty for example yesterday, and the next day the game freeze.

I test this config form game Shin Megami Tensei Nocturne PS2 Classic Version (NPUD20911) with Digimon Rumble Arena 2 NTSC version, for now the game run perfectly but I'll wait tomorrow and see if the problem is already solved or not =(

Code:
3D 00 00 00 F6 41 00 00 46 00 00 00 00 00 00 00
53 4C 55 53 2D 32 31 30 36 37
 
Wich ID is your game ?
The config is selected based on it (and some configs are dependant of it, because applyes patches on top of the ISO or memory areas that differs by ID/region or the game)

Take a look at the log.txt files from this links and compare them:


Inside GXemu there are 3 "Parappa the Rapper 2" configs for: SCUS_971.67, SCPS_150.17, SCES_504.08
Inside SOFTemu there are 3 "Parappa the Rapper 2" configs for: SCUS_971.67, SCPS_150.17, SCES_504.08
But... the configs are different because are using different commands, and are patching different things at different offsets



Edit:
This game is tricky.. it looks sony was "porting" the configs between regions of the game, also most probably the config was originally made for GXemu... and later ported to SOFTemu

The ID is SCUS_971.67. And I don't get it what you mean sending me this log.txt files.

I am using the gx_emu config for SCUS-97167 and everything works perfectly. Are you using ps2 classic gui to make your pkg?

Yes, but i'm using only to encrypt the ISO. PS2 Classics Manager won't work on my PS3 too.


from compatability list for parappa the rapper 2:

NTSC-U version hangs on loading screen but works with ManaGunZ Config file (*GX*). PAL version boots but hangs after a short amount of play time.

As I said, I used ManaGunz and still crashes at the opening and in random parts of the game.
 
The ID is SCUS_971.67. And I don't get it what you mean sending me this log.txt files.
I just was trying to show you that the configs for this game are different in between GX emu and SOFT emu, and for every region where the game was published... and the best way to see the differences (in a human readable format) is by looking at that log.txt files

Additionally, i was derrailing a bit because some of the commands used in some configs are still unknown, and the configs for this game are a bit weird

I have a PS3 SuperSlim
Yes, but i'm using only to encrypt the ISO. PS2 Classics Manager won't work on my PS3 too.
When you create a "PS2 classic" package you need to encrypt both, the ISO and the CONFIG
Otherway (if you dont encrypt them) the emulator is not able to load them

The problem in HEN is that is not posible to patch the PS2 emulator to disable the encryption (of the ISO and the CONFIG), so the only thing that works is to encrypt them and use the "PS2 classic" format where both the ISO and the CONFIG are encrypted

As I said, I used ManaGunz and still crashes at the opening and in random parts of the game.
The way how the actual manaGunZ mounts the PS2 games doesnt works in HEN. This features was intended to be used with CFW where the ISO and the CONFIG are not encrypted

The only known way to add PS2 HEN support in manaGunZ is by using an additional "PS2 launcher" installation, that works as a fake "PS2 classics" placeholder where we can swap the ISO and CONFIG to replace the game... but this is not implemented yet in ManaGunZ
 
I just was trying to show you that the configs for this game are different in between GX emu and SOFT emu, and for every region where the game was published... and the best way to see the differences (in a human readable format) is by looking at that log.txt files

Additionally, i was derrailing a bit because some of the commands used in some configs are still unknown, and the configs for this game are a bit weird



When you create a "PS2 classic" package you need to encrypt both, the ISO and the CONFIG
Otherway (if you dont encrypt them) the emulator is not able to load them

The problem in HEN is that is not posible to patch the PS2 emulator to disable the encryption (of the ISO and the CONFIG), so the only thing that works is to encrypt them and use the "PS2 classic" format where both the ISO and the CONFIG are encrypted


The way how the actual manaGunZ mounts the PS2 games doesnt works in HEN. This features was intended to be used with CFW where the ISO and the CONFIG are not encrypted

The only known way to add PS2 HEN support in manaGunZ is by using an additional "PS2 launcher" installation, that works as a fake "PS2 classics" placeholder where we can swap the ISO and CONFIG to replace the game... but this is not implemented yet in ManaGunZ


Oooh, I didn't know that needs a CONFIG, where I can read a tutorial about that?
 
Oooh, I didn't know that needs a CONFIG, where I can read a tutorial about that?
In the PC tool "PS2 classics GUI" made by aldo there is an option to add a config to the PKG, and are included all the known configs, so you dont need to download the config or search for it

Btw, remember to select the GX config for this game, we know the GX is "the good one" because mrjaredbeta reported it


The other EURO/USA configs from SOFT emu for this game are missing a patch (the reason why that patch is not applyed in the SOFTemu configs is unknown, but im guessing we need it)
There is another unknown value that differs in this configs (the net command ID 0x15 with value 0x4 or 0x14), at some point someone should make some tests to see what is doing that one, we are just using it blindly but the game is not completly fixed as far i understood ?

And then there is the weird detail of the JAP configs for this game that uses a very different patch (applyed to the EE memory on runtime instead of statically applyed to the ISO... not sure if the result is the same, but i dont get why they did it this way, this is another mistery)
 
In the PC tool "PS2 classics GUI" made by aldo there is an option to add a config to the PKG, and are included all the known configs, so you dont need to download the config or search for it

Btw, remember to select the GX config for this game, we know the GX is "the good one" because mrjaredbeta reported it


The other EURO/USA configs from SOFT emu for this game are missing a patch (the reason why that patch is not applyed in the SOFTemu configs is unknown, but im guessing we need it)
There is another unknown value that differs in this configs (the net command ID 0x15 with value 0x4 or 0x14), at some point someone should make some tests to see what is doing that one, we are just using it blindly but the game is not completly fixed as far i understood ?

And then there is the weird detail of the JAP configs for this game that uses a very different patch (applyed to the EE memory on runtime instead of statically applyed to the ISO... not sure if the result is the same, but i dont get why they did it this way, this is another mistery)

Alright, thanks for the patience and for the learning. I'll do this right now, can't wait to play PaRappa again.
Just one last question, is possible to add a config to an encrypted ISO without creating a PKG file?
 
Alright, thanks for the patience and for the learning. I'll do this right now, can't wait to play PaRappa again.
Just one last question, is possible to add a config to an encrypted ISO without creating a PKG file?
Yes, by replacing the files in the "PS2 classics" installation path
Is the method i mentioned before... we just install 1 "PS2 classics placeholder" and then we swap the files inside it... so... the game is different but the PS3 thinks is the same :D
The same applyes to the CONFIG

Use a filemanager and take a look at path dev_hdd0/game/<TITLE_ID> of the game
The <TITLE_ID> is the ID of the game... whatever ID was given to the PKG by the "PS2 classics GUI"
Inside that instalation path you could have 2 files:
dev_hdd0/game/ABCD12345/USRDIR/ISO.BIN.ENC <----- this is the ISO encrypted
dev_hdd0/game/ABCD12345/USRDIR/CONFIG <----- this is the CONFIG encrypted
 
Yes, by replacing the files in the "PS2 classics" installation path
Is the method i mentioned before... we just install 1 "PS2 classics placeholder" and then we swap the files inside it... so... the game is different but the PS3 thinks is the same :D
The same applyes to the CONFIG

Use a filemanager and take a look at path dev_hdd0/game/<TITLE_ID> of the game
The <TITLE_ID> is the ID of the game... whatever ID was given to the PKG by the "PS2 classics GUI"
Inside that instalation path you could have 2 files:
dev_hdd0/game/ABCD12345/USRDIR/ISO.BIN.ENC <----- this is the ISO encrypted
dev_hdd0/game/ABCD12345/USRDIR/CONFIG <----- this is the CONFIG encrypted

Already played the game and beat it, good as I remeber. Thanks again, I gonna use this on future games. :encouragement::encouragement:
 
@nictse Please test, some minor issues are known. But report all you will find wrong.

Code:
3D 00 00 00 57 44 00 00 0B 00 00 00 01 00 00 00
93 01 00 00 8C 06 00 00 20 00 00 00 4B 00 60 2C
48 49 88 00 4B 00 68 2C 48 4A 88 00 4B 0C 68 2C
48 4B 88 00 4A 00 02 FF 4A 00 02 FF 4B 00 60 2C
4B 00 68 2C 4B 0C 68 2C 4A 00 02 FF 4A 00 02 FF
48 49 88 00 48 4A 88 00 48 4B 88 00 0A 00 00 00
03 00 00 00 90 BB 15 00 DE 01 AF 15 00 00 00 00
A0 BB 15 00 0D 00 02 45 00 00 00 00 14 C6 15 00
15 00 00 45 00 00 00 00 00 00 00 00
 
At beggining of Mission 1 cutscene,a very little black block on the ground.very ignorable.
Mission 7 during take off, take the camera under the plane, then the camera back to normal a very little slower.
Mission 10 at the end of the cutscene,a little wrong texture on the ground.
Mission 16 take off same as 7,after take off a little slower.
The other mission no notable issue.

Some missions has shake issue,I think it'll happen on ps2 machine too.

@kozarovv
 
Last edited:
And it was working 100% perfect ? (SCUS_971.67 with the config from GX)
100% unfortunately no. However it's only FPS drops (that doesn't muddle the gameplay) and one graphic bug. I can't take a screenshot of the game so I will reproduce the error by edition.
upload_2020-7-21_14-29-0.png

It appears a grey color in the openning transition.
 

Similar threads

Back
Top