PS3 Compatibility List - PS2 on PS3

@Rafaelrios It looks like it just skips some performance-intensive effects when needed. Here is a port of it to NTSC-U:

Jade Cocoon 2 (SLUS-20309)
Code: 
3D 00 00 00 57 44 00 00 46 00 00 00 0A 00 00 00
01 00 00 00 18 22 1F 00 44 69 05 0C 00 00 00 00
0A 00 00 00 06 00 00 00 50 3D 96 00 C0 FF BD 27
08 00 E0 03 54 3D 96 00 20 00 BF 7F 00 00 00 00
18 6D 96 00 C8 97 25 0C 00 00 00 00 80 71 96 00
C0 FF BD 27 08 00 E0 03 84 71 96 00 20 00 BF 7F
00 00 00 00 58 7A 96 00 60 9C 25 0C 00 00 00 00
 
Dynasty Warriors 4 (SLUS-20653)
Code: 
3D 00 00 00 57 44 00 00 35 00 00 00 0A 00 00 00
03 00 00 00 A0 F7 1B 00 18 00 03 24 13 00 03 24
C8 86 19 00 15 00 41 28 08 00 41 28 D8 B4 19 00
15 00 41 28 08 00 41 28

Dynasty Warriors 5 (SLUS-21153)
Code: 
3D 00 00 00 57 44 00 00 35 00 00 00 0F 00 00 00
B8 43 11 00 EC 44 11 00
Ports of NET configs to NTSC-U. The PAL Classics have empty configs, so I guess there's no need to port. :)
 
I wanted to report a problem with tales of destiny director'cut, it is something that happens inside the towns/dungeons, somewhat random but happens occasionally, when pressing select to see the skits the ps3 turns off and remains dead without the red light being visible , you have to press the power button twice, once for the red light to come back on and once for it to turn on again, the problem is somewhat minor since it does not always happen but it is occasional and it happens only in towns / dungeons, in the world map has not happened to me, I have not had a chance to try it without the patch in English to see if it is a related problem sorry, even if it is something not so serious it scares me that the ps3 will end up spoilling Xd
 
Lunanabe said:
I wanted to report a problem with tales of destiny director'cut, it is something that happens inside the towns/dungeons, somewhat random but happens occasionally, when pressing select to see the skits the ps3 turns off and remains dead without the red light being visible , you have to press the power button twice, once for the red light to come back on and once for it to turn on again, the problem is somewhat minor since it does not always happen but it is occasional and it happens only in towns / dungeons, in the world map has not happened to me, I have not had a chance to try it without the patch in English to see if it is a related problem sorry, even if it is something not so serious it scares me that the ps3 will end up spoilling Xd
Click to expand...

isn't that a problem with english patch??i remember having a similiar issue with dq v english patch i simple downloaded another one.
 
Perhaps,
The strange thing is that of the few people who have played it on ps3 with a patch I have read them and have not mentioned anything, it happened to me at some point in the story 2 specific times and now that I am almost near the end it is more common, makes me think it's someting related with the hardware running on the towns and dungeons
 
Last edited:
haxxxen said:
someone can port PRIMAL SCUS-97142 to SCES_511.35? @mrjaredbeta ?
maybe explain how to port those commands?
Click to expand...

Did you try the GX config in the database for SCES-51135?
Code: 
3D 00 00 00 57 44 00 00 12 00 00 00 0D 00 00 00
00 00 00 04 00 00 00 00 02 00 03 00 5F 01 00 00
8D BD 6F 2C 67 03 00 00 02 00 03 00 6B 01 00 00
31 35 70 E9 72 03 00 00 03 00 02 00 B8 9C 39 10
70 9D 39 10 00 00 00 00 53 43 45 53 2D 35 31 31
33 35

I understand that you need both executables SCES_511.35 and SCUS_971.42 to compare the offsets.
The commands are little endian codes of 32 bits.
3D 00 00 00 57 44 00 00 <= magic number (identifier) + version
12 00 00 00 0D 00 00 00 <= code 12 + length (0D = 13 codes = 13*4 = 52 bytes)
00 00 00 04 00 00 00 00 02 00 03 00 5F 01 00 00
8D BD 6F 2C 67 03 00 00 02 00 03 00 6B 01 00 00
31 35 70 E9 72 03 00 00 03 00 02 00 B8 9C 39 10
70 9D 39 10
00 00 00 00 <= terminator code
53 43 45 53 2D 35 31 31 33 35 <= title id (SCES-51135)

The codes in bold are the offsets that changed from SCUS to SCES: 0x1399cb8-0x1399d70

The NET config for SCUS has these additional codes that may need to be ported (or not?)
0B 00 00 00 01 00 00 00 47 07 00 00 6C 04 00 00
04 00 00 00 80 5F 03 3C 80 00 03 3C
 
Last edited:
hm, seems I even have converted the config myself correctly, but there is still some problem
https://i.imgur.com/pLjpuVp.mp4

btw, using the gx config does not work well as using your custom one. this is what I have ported. the last bit makes this config work better as the rest is same like gx
Code: 
3D000000653D0000120000000D0000000000000400000000020003005F0100008DBD6F2C67030000020003006B010000313570E97203000003000200B89C3910709D39100B00000001000000470700002C06000004000000805F033C8000033C

edit
the info on wiki is also wrong, as the disc sector is in the main elf itself

maybe someone can look into it?
 
Last edited:
So what's the offset in the SCES version for the 0x0B patch? Remember you have to add an offset correction (+0xC) most of the time for DVD reads. Therefore, if the offset to patch is 0x3A3E2C in the image file (sector: 0x747, offset: 0x62C), you have to add 0xC to the offset (0x62C+0xC=0x638).

The patch is for the main elf file indeed, but it does patch the .vutext section containing the VU microprogram specifically. It is a code for a coprocessor loaded from the main executable file.
 
Last edited:
Agrippa said:
So what's the offset in the SCES version for the 0x0B patch? Remember you have to add an offset correction (+0xC) most of the time for DVD reads. Therefore, if the offset to patch is 0x3A3E2C in the image file (sector: 0x747, offset: 0x62C), you have to add 0xC to the offset (0x62C+0xC=0x638).
Click to expand...

0B00000001000000470700002C06000004000000805F033C8000033C
so same sector but 0x62C offset

the config works fine in the beginning of the game, but shortly after the mill this clipping effect happens

edit
how does this 0xB command even work?
 
Last edited:
Agrippa said:
@aldostools, I confirm, there is an issue with the config file not being applied in the newest webMAN.
Click to expand...

Thank you for the bug report. Could you provide more details about the issue?

1. Does it happen with PS2ISO or PS2 Classics or both?
2. Is the Auto CONFIG option in /setup.ps3 check marked?
3. Is the CONFIG file copied to /dev_hdd0/PS2ISO?
4. Does it work if the CONFIG files is copied manually to /dev_hdd0/PS2ISO with the same name of the ISO?
5. Could you indicate what game and what is the exact file name? Does it happen with all games?

I ask all these questions because the Auto CONFIG is very complex and there various algorithms involved that depends of the type of game, where it is stored, the file name, etc.

For better tracking and more discussion about the subject I suggest to open an issue in github.
 
You must log in or register to reply here.

Similar threads

Back
Top