PS3 Compatibility List - PS2 on PS3

Other values, or another additional commands, you have been trying with what is inside gxemu but maybe is needed to add another ingredient to the recipe :/

Actually netemu 0x48 (used to change IPU settings) maybe does something positive
There is another command ilke that btw... netemu 0xC note how it uses 2 values (like main menu and submenu), like the one for IPU settings
 
I tried directly with the patched ISO, I have same result. The command 0x1D / 0x20 is probably important to make it working. I tried with different value 0x3C 0x64 0xF0...

I surrender !

:'(
 
Zar said:
I tried directly with the patched ISO, I have same result. The command 0x1D / 0x20 is probably important to make it working. I tried with different value 0x3C 0x64 0xF0...

I surrender !

:'(
Click to expand...
For now I can confirm that patched iso still hangs. Keep in mind that 0x20 also can not work as both patches can exclude some GS code parts that was unneeded on gxemu. But I will try tomorrow some options, just for research purposes.
 
Guys, could you help me with 0x00 GX cmd?
I'm trying to port SLUS-21180 3cc13d914d Onimusha: Dawn of Dreams CONFIG to fix texture issues.

I have cropped ps2_gxemu.elf by 0x10000 bytes.
Jumped to 0x33E858 offset
7dH_LvDt-CA.jpg
Then to 0x33B528 offset
WN6j1DP6V9A.jpg

And now I don't know what to do next.
 
lex3a said:
Guys, could you help me with 0x00 GX cmd?
I'm trying to port SLUS-21180 3cc13d914d Onimusha: Dawn of Dreams CONFIG to fix texture issues.

I have cropped ps2_gxemu.elf by 0x10000 bytes.
Jumped to 0x33E858 offset
7dH_LvDt-CA.jpg
Then to 0x33B528 offset
WN6j1DP6V9A.jpg

And now I don't know what to do next.
Click to expand...
Config will be:
3D 00 00 00 57 3D 00 00 01 00 00 00 04 02 3C 00
FF 00 00 00 00 00 00 00

Where FF is value from 00 to 3B. Sadly I didn't figured out this yet so you need to try by yourself.
Here is what I got so far: http://www.psdevwiki.com/ps3/Talk:P...mu_commands_compared_to_ps2_netemu_0x01_table
And FYI 0x00 is different that other commands. First is offset, then subcommand
 
Onimusha 2: Samurai's Destiny uses the same command, and the second value is 0x34224 (what mysis named function_id)
Im mentioning it because this ID is another one missing
 
Yeah, it finally fixed those pesky textures!
gpljU77d8-E.jpg
lj2H85D4E7E.jpg

0x2C = 0x36FC8

Onimusha: Dawn of Dreams (SLUS-21180 3cc13d914d) Fixes all texture bugs
Code: 
00000000 3D 00 00 00 57 3D 00 00 01 00 00 00 04 02 3C 00 =...W=........<.
00000010 2C 00 00 00 00 00 00 00                         ,.......
 
lex3a said:
0x2C = 0x36FC8
Click to expand...
Nice :)
I noticed you added it to the long table in wiki, i was thinking in changing the font size to x-small and splitting that table in 3 (like the other table in that page at top but this one needs 20 rows per table and splitted in 3 instead of 4)
I will do it later, but if someone wants to practise a bit with wiki tables go for it, if something goes wrong there is no harm
 
Here is another CONFIG:

Metal Gear Solid 3: Subsistence Disc 1 (SLUS-21359 4cb14de1a5) Fixes crash after intro sequence.
Code: 
00000000 3D 00 00 00 57 3D 00 00 12 00 00 00 07 00 00 00 =...W=..........
00000010 00 00 00 00 00 00 00 00 01 00 04 00 10 00 D7 0D ................
00000020 49 00 5F 0D 08 00 E7 0D 59 00 EB 0D 15 00 00 00 I._.....Y.......
00000030 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 
lex3a said:
Yeah, it finally fixed those pesky textures!
gpljU77d8-E.jpg
lj2H85D4E7E.jpg

0x2C = 0x36FC8

Onimusha: Dawn of Dreams (SLUS-21180 3cc13d914d) Fixes all texture bugs
Code: 
00000000 3D 00 00 00 57 3D 00 00 01 00 00 00 04 02 3C 00 =...W=........<.
00000010 2C 00 00 00 00 00 00 00                         ,.......
Click to expand...
Nice find!

@sandungas looks like offsets are the same for every emu revision, I try to confirm this after work.
 
Last edited:
kozarovv said:
Nice find!
Click to expand...
Although, it is strange. Textures look very pixelated, but atleast I can see them now

Edit:
kozarovv said:
fix for Turok Evolution - SLUS-20333
Code: 
00000000 3D 00 00 00 89 3D 00 00 26 00 00 00 50 14 31 00 =...‰=..&...P.1.
00000010 F4 1E 31 00 00 00 00 00 ô.1.....
Click to expand...
This config does not work. It fixes freezes in first ingame cutscene, but game still freezes

EDIT2: Jak 1 has the same issue. When you collect precussor orbs game freezes. It is like 1 frame in 5 seconds. Then suddenly everything is ok. Same with the Turok
 
Last edited:
kozarovv said:
@sandungas looks like offsets are the same for every emu revision, I try to confirm this after work.
Click to expand...
My guess is everytime the emu .self is compiled the offsets could change because the whole size of the .elf could change, maybe some offsets matches in latest revisions of gxemu but if we take a look at the most ancient one the differences could be bigger
Also, the way i modifyed the table allows to add that same offset info from softemu
I think adding all them from all versions is a massive amount of work and probably a bit pointless but when you started the table i realized is good to have that offsets of the latest version of gxemu fully indentifyed (used in firmwares 4.82, 4.81, and maybe others before)
 
lex3a said:
Although, it is strange. Textures look very pixelated, but atleast I can see them now

Edit:
This config does not work. It fixes freezes in first ingame cutscene, but game still freezes

EDIT2: Jak 1 has the same issue. When you collect precussor orbs game freezes. It is like 1 frame in 5 seconds. Then suddenly everything is ok. Same with the Turok
Click to expand...

Its similar than Valkyrie Profile 2. The config fixed the black screen after start but the game still freeze at certain points.
 
I been looking at all the game Title IDs that uses command 0x0E inside gxemu from firmwares 4.82
There is a total of 8 title IDs for 3 games
-Gran turismo 4 (EUR, JAP, KOR, USA)
-Tourist Trophy (EUR, JAP, USA)
-Singstar ABBA (EUR)

Instead of writing a long explain at all the data related with this command, i made the 8 config files and zipped them together with a .TXT where you can see all that data, incase someone wants to follow my procedure you can copypaste to search for that values, and use it to verify the data
I cant test them, so if someone have this games please try and report back if success or failure, the usage of this command is new, at least for me

https://www.sendspace.com/file/nn1o7w



------------------------
Resume of how works gxemu command 0x0E (a.k.a. netemu 0x10)
At the second level of the structure there are two unit32_t values (in the TXT are called "data_1" and "data_2")
Initially looks like offsets of gxemu itself, specially if you start looking at gran turismo 4 (there is one that matches with a weird area that looks like a huge array), but when you look at singstar ABBA it doesnt makes sense at all, so if there is something i can say is this values are not absolute offsets of gxemu
Still... if you compare the values of all them you will realize the second one is always bigger than the first one... that difference is noted in the TXT (in the second one where it tells "... 0x??? bigger", and are consecutive, that difference is very small
So yeah... looks like offsets but i think are offsets of other stuff (some area of the game), not offsets of gxemu itself
In other words... we dont need to search for more data, everything seems to be here

So i think the conversion to config files should be as simple as what i did
I hope it works... if it doesnt i hope this is going to be an start point to continue digging with this command :)
About the singstar ABBA config... yeah... shame on me, if that one works dont give me credit for it, i made it just for completionism because appears on the list :P



Edit:
Please test the games with, and without the config file to identify if the config does some improvement
You can see the problems reported for that games here: http://www.psdevwiki.com/ps3/PS2_Classics_Emulator_Compatibility_List
 
Last edited:
lex3a said:
This config does not work. It fixes freezes in first ingame cutscene, but game still freezes

EDIT2: Jak 1 has the same issue. When you collect precussor orbs game freezes. It is like 1 frame in 5 seconds. Then suddenly everything is ok. Same with the Turok
Click to expand...
My guess is the config data was specific to fix a problem, like the cutscene/s you are mentioning
And the other problem that we can call... lagging, or frameskip, or hertz, or frequency or freezing, or this kind of things is because performance
gxemu is for PS3 models with partial ps2 hardware so that components was dealing with the problem... in netemu we dont have that so the problem appears

So the solution is to "fine tune" netemu to improve performance... but at this point is like a roulette because there are too much unknown commands and we cant even be sure if there is worthy to try to achieve this goal because maybe is not posible
But personally... if i had to bet i would say that sony thought in this and they probably added some commands to solve this kind of problems in one way or another

When searching for this unknown commands i would try with the bigger IDs... the last ones used by softemu... and first ones added for netemu
In other words.... netemu commands bigger than 0x3D has more chances to succeed fixing the performance problems caused by the missing PS2 components ;)
 
nifengyuexia said:
Thank you for your reply, my version is NTSC-J, can I help test the NTSC-J game?
Click to expand...
There are 2 version for japan, SLPM-74232 (using gxemu command 0x0), and SLPM-66275 (using gxemu command 0x4)

gxemu comand 0x4 doesnt exists in netemu, to fix SLPM-66275 is going to be needed some malabarism, this one is a "no way" by now until someone imagines a way to bypass this problem

But SLPM-74232 is easy, and is going to work for sure, in the same way did work the USA version :)
Well... to be fair, is not so easy... the config file needs two values, one can be copypasted, and the other is an identifyer that could go up to 0x3B... thats a lottery game of 60 options, the ones here:
http://www.psdevwiki.com/ps3/Talk:P...mmand_0x01_function_ID_compared_to_other_emus
So in the worst scenario (incase the identifyers doesnt appears in that table in wiki) is going to be needed to prepare 50+ config files, and you are going to need to boot the game 50+ times until you find the correct one

*There are a couple more versions for EUR and other for USA btw... i have not took a look at them but probably are going to need an specific config each
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top