PS4 [Research]PS2 emulator configuration on PS4

@cfwprophet, does CUSA is necessary as tittle ID for PS2 games? I mean, I'm using PS2 game ID as PS4 tittle ID and it works for me :
SQQqZbZ9Sy21bSDtguHdPQ.png


In add, I made a small and simple icon0 template for PS2 game covers. Use it as you like.
icon0_template.png
 
No the TitleID of the PKG is a PS4 one "CUSA" the PS2 TitleID is after it.
"EP1006-CUSA03492_00-SLES503660000001"

And if it works, we don't care . ^^
Better for us. I just keeped that format for the first to get something running and what we need or not need we will see now by playing with it.
You guys tell me and i change it then. :)
 
cfwprophet said:
No the TitleID of the PKG is a PS4 one "CUSA" the PS2 TitleID is after it.
"EP1006-CUSA03492_00-SLES503660000001"

And if it works, we don't care . ^^
Better for us. I just keeped that format for the first to get something running and what we need or not need we will see now by playing with it.
You guys tell me and i change it then. :)
Click to expand...

I just think it is a bit weird to use a random/custom PS4 CUSA TitleID where we can use only PS2 TitleID from the iso. Then the second part of the content id used for game name short string for a more readable package file name .
I find it simpler and may avoid to overwrite existing content if same CUSA used by mistake.
Anyway, nothing important. It's just a idea to even simplify your app.
LutHrlVAQ6yLov5COIdpiQ.png
 
Uhm...about the TitleID...this one is from orig PodRacer PS2 PKG:
EP1006-CUSA03492_00-SLES503660000001

That's the one from MaxPayne:
EP1004-CUSA04488_00-SLES503260000001

Also the sfos have an PS4 TitleID and not an PS2 one. So i am not sure what you mean by that.
The ContentID is a fixed format and hase to be this length. But you can rename the pkgs after you builded them to avoid overwriting.

If i have something misunderstood let me know and we talk about. :)

PS: a pic of the nptitle.dat of PodRacer
 

Attachments

  • image7.png
    image7.png
    76.8 KB · Views: 733
cfwprophet said:
Uhm...about the TitleID...this one is from orig PodRacer PS2 PKG:
EP1006-CUSA03492_00-SLES503660000001

That's the one from MaxPayne:
EP1004-CUSA04488_00-SLES503260000001

Also the sfos have an PS4 TitleID and not an PS2 one. So i am not sure what you mean by that.
The ContentID is a fixed format and hase to be this length. But you can rename the pkgs after you builded them to avoid overwriting.

If i have something misunderstood let me know and we talk about. :)

PS: a pic of the nptitle.dat of PodRacer
Click to expand...

Ok, I reformulate:

Sony assigned official "CUSA" PS4 Title ID to those PS2 games ported to PS4. ok fine.
But to make our own PS2 game port, we don't know wich "CUSA" PS4 title ID to use, so we must define a random unofficial one for each. This can conflict with official PS4 content.
Instead, I propose to use the "SLES/SLUS..." PS2 Title ID as PS4 tittle ID. This way no risk of conflict with official PS4 content.
I'm sending to you a package I made following this rule. So you can see what I made by yourself.
 
Pretty amazing to see the ps2 emulator has been unlocked, it makes me sad that sony has changed so much into removing all the cool features that the older systems had. Any likely hood of a psx emulator?
 
Possible objects to call by "lua bridge". Lua bridge is internal emulator mechanism to hook game functions with use of conditions.

  • Hook.GsCustomShader
  • getEEObject
  • getIOPObject
  • getEmuObject
  • getTrophyObject
  • getDmaObject
  • getGLSObject
  • getRemotePlayObject
  • getScreenShotObject
  • getVideoRecordingObject
  • getSharePlayObject
  • getGsObject

Looks like emu have the same Game Disc patch system like ps2_netemu. In net emu is 0xB. Here is info I found in eboot.

MECHA PATCH : sec=%d(%x), ofs=%d(%x) size=%s

Sector on disc, offset in selected sector, patch data size. But I Didn't found any command related to it.
Also you can find there info about LIMG, which is surprising as LIMG is not used in PS4 as far as I know.
 
Last edited:
Has anyone yet tried to use the PS2 BIOS (PS20190AC20030623, ps1_rom.bin) which is used on the PS3 for the PS1 emulator to play a PS1 game using the PS2 emulator on the PS4? (Just include the BIOS, alter the --rom parameter and try a PS1 game iso instead of a PS2 one.)
 
M4j0r said:
Has anyone yet tried to use the PS2 BIOS (PS20190AC20030623, ps1_rom.bin) which is used on the PS3 for the PS1 emulator to play a PS1 game using the PS2 emulator on the PS4? (Just include the BIOS, alter the --rom parameter and try a PS1 game iso instead of a PS2 one.)
Click to expand...
PS2 emu with PS1 bios? I doubt it.. Try to run pcsx2 with ps1 bios. BTW. Looking at ps2 bios from ps4 emu is not stripped from ps1 stuff.
 
kozarovv said:
PS2 emu with PS1 bios? I doubt it.. Try to run pcsx2 with ps1 bios. BTW. Looking at ps2 bios from ps4 emu is not stripped from ps1 stuff.
Click to expand...

The PS1 emu on the PS3 is using a (stripped) PS2 BIOS, as I said before. I will try to run it using pcsx2.

Update: The BIOS works, however booting a PS2 game fails (for obvious reasons) and PS1 games are not yet support by pcsx2.
 
Last edited:
M4j0r said:
The PS1 emu on the PS3 is using a (stripped) PS2 BIOS, as I said before. I will try to run it using pcsx2.

Update: The BIOS works, however booting a PS2 game fails (for obvious reasons) and PS1 games are not yet support by pcsx2.
Click to expand...
I'm aware that ps1 emu use ps2 bios mod. But anyway I doubt it will run PS1 games just like that on ps4.
 
kozarovv said:
I'm aware that ps1 emu use ps2 bios mod. But anyway I doubt it will run PS1 games just like that on ps4.
Click to expand...
That's my guess too because the ps1/ps2 emulator is different, but no one actually tried it.

The BIOS does only contain the following modules: RESET, ROMDIR, EXTINFO, ROMVER, SBIN, LOGO, TBIN, KROMG, KROM, VERSTR.
 
M4j0r said:
That's my guess too because the ps1/ps2 emulator is different, but no one actually tried it.

The BIOS does only contain the following modules: RESET, ROMDIR, EXTINFO, ROMVER, SBIN, LOGO, TBIN, KROMG, KROM, VERSTR.
Click to expand...
And fake IOPBOOT. Anyway don't trust it too much, is probably just used like that because ps2 strip is latest version of ps1 bios. I doubt it contain more ps2 code that is needed to set ps1 mode on real/emulated hardware of ps2.
 
kozarovv said:
@M4j0r I added info to wiki about bios used in PS4 if you are interested. Is EXACTLY the same BIOS used in ps2_netemu on PS3.
Click to expand...
I've seen that too.

There're definitely more emulation BIOS' out there:
This is a version 0 padlog, and it requires the v1.90 BIOS ROM in order to be replayed.from boot. Devs can manually specify the legacy v1.90 ROM via config/CLI: --rom=../roms/PS20190AC20030623_nordram_miniOSD.bin
Click to expand...
ROM image not found: %s.See accompanying /roms/rom_notes.txt for information on selecting and symlinking a PS2 rom
Click to expand...
There's also a check for PS20220WD2005062.
 
M4j0r said:
I've seen that too.

There're definitely more emulation BIOS' out there:


There's also a check for PS20220WD2005062.
Click to expand...
Yeah there is also config variable to select OSD: --host-osd= [0,off,minimal,verbose] not sure we can do something with this. But emu use modified debug bios, maybe we can use full debug bios + osd on?
 
You must log in or register to reply here.

Similar threads

Back
Top