PS3 ps1_netemu - External Configs and Ad Hoc Params

Hello
I've read some posts and decided to test BLOODY ROAR 2
I created three PKGs using pop-fe v1.3
BLOODY ROAR 2 - BRINGER OF THE NEW AGE (SLES01722) PAL works the best. I haven't experienced any audio problems or frame rate issues.
BLOODY ROAR 2 - BRINGER OF THE NEW AGE (SCUS94424) NTSC USA. There are some frame rate problems as the game slows down sometimes.
BLOODY ROAR 2 - BRINGER OF THE NEW AGE (SLPS01842) NTSC JAPAN. This version is running in slow motion.
If I use the "Force NTSC" on the USA and the Japanese versions, would it help with the frame rate issues?
 
Temperature said:
I know this isn't new, however, I thought I'd draw attention to the fact hard coded TitleIDs in the three emulators are very different. For example, ps1_newemu is the only one with Medal of Honor.
Click to expand...
Yup, the three emulators use different settings when needed. That particular config command for Medal of Honor just tries to force netemu when booted through newemu, though, most likely due to the black void issue in ps1_emu/newemu. Funny thing is that command fails to switch back to netemu, so game will still play in newemu regardless of config or not. Maybe it would be worth a test to force newemu for that game and see if black void issue also happens on that emulator.


nydalap said:
BLOODY ROAR 2 - BRINGER OF THE NEW AGE (SLPS01842) NTSC JAPAN. This version is running in slow motion.
If I use the "Force NTSC" on the USA and the Japanese versions, would it help with the frame rate issues?
Click to expand...
The config fixes the slowdown issue (or at least most of it, judging by NTSC-U performance), but I must have missed that version. Config was only ported for SCPS-45374 and not for SLPS-01842.

@Ronnie Sahlberg Can you add Bloody Roar 2 config for this SLPS-01842 version? Same config as the others.
 
mrjaredbeta said:
Yup, the three emulators use different settings when needed. That particular config command for Medal of Honor just tries to force netemu when booted through newemu, though, most likely due to the black void issue in ps1_emu/newemu. Funny thing is that command fails to switch back to netemu, so game will still play in newemu regardless of config or not. Maybe it would be worth a test to force newemu for that game and see if black void issue also happens on that emulator.



The config fixes the slowdown issue (or at least most of it, judging by NTSC-U performance), but I must have missed that version. Config was only ported for SCPS-45374 and not for SLPS-01842.

@Ronnie Sahlberg Can you add Bloody Roar 2 config for this SLPS-01842 version? Same config as the others.
Click to expand...
done
 
Hello, it appears the file "pop-fe-psp.ui" is missing from the _internal folder. It's simple to fix by just getting it from the proper release page, but may confuse someone so I thought I'd give the heads up.
 
Um Jammer Lammy (SCUS-94448)
Code: 
00 00 20 00 00 00 00 00 38 00 00 00 00 00 00 00
13 00 00 00 01 00 00 00
This cancels out the internal config that forces newemu and should in theory fix whatever netemu's issue is with the NTSC versions of this game (which I haven't tested enough to know).
 
mrjaredbeta said:
Um Jammer Lammy (SCUS-94448)
Code: 
00 00 20 00 00 00 00 00 38 00 00 00 00 00 00 00
13 00 00 00 01 00 00 00
This cancels out the internal config that forces newemu and should in theory fix whatever netemu's issue is with the NTSC versions of this game (which I haven't tested enough to know).
Click to expand...
added
 
nekketsu oyaku.jpg
NEKKETSU OYAKO NTSC-J
When I try to create a PKG I get this error.
 
@mrjaredbeta
do you know if it is possible to modify official configs and add stuff (if so, how?)? I have tried it and recalculated the signature with sign3, but the resulting config cannot be loaded.

and about the decrypted config patch, is there a patch that works on PS3?
 
haxxxen said:
@mrjaredbeta
do you know if it is possible to modify official configs and add stuff (if so, how?)? I have tried it and recalculated the signature with sign3, but the resulting config cannot be loaded.

and about the decrypted config patch, is there a patch that works on PS3?
Click to expand...
So the decrypted config patch fails on PS3 due to some extra checks I think. It works on RPCS3, though. So, the only way to insert custom configs would be to resign them (with sign3), and re-encrypt the DAT to EDAT (with something like TrueAncestor EDAT Resigner).

Luckily, Ronnie made a really easy tool that inserts new config, resigns, and reencrypts for you to just drop in game folder to replace current ISO.BIN.EDAT here: https://github.com/sahlberg/pop-fe/actions/runs/6165170040

Otherwise, pop-fe automatically does all of the current config insertion when making the package, so all configs posted here are included and auto-enabled in current pop-fe build.
 
ok and thanks for answering.

so if I try to build a classic from an official available game, pop-fe will use the official config as base and add additional patches @mrjaredbeta ? just asking, cause this video mode patch is really great and replaces Cobra's force_video+elf patch. 'have to find out, what and how it is done
 
haxxxen said:
so if I try to build a classic from an official available game, pop-fe will use the official config as base and add additional patches?
Click to expand...
Yes, absolutely. It uses the internal config table first and also loads the PAL->NTSC config command in addition to the internal/external config when "Force NTSC" is checked in pop-fe-ps3.
 
nydalap said:
View attachment 41434 NEKKETSU OYAKO NTSC-J
When I try to create a PKG I get this error.
Click to expand...

The issue with this game is that is has an unusual structure.
Almost all games have a SYSTEM.CNF file that indicates which file it should boot and which also contains the disc-id.
This game does not so I will need to try a different way to determine the disc id.
I think I might be able to read the disc-id based on the cdrom volume label that is stored at 0x8028 but I will not have time to test this until sunday.
 
PS1_Emulation page on PS3 Dev Wiki.

This was last updated on August 16th. Does new information about what's being learned here need to be added?
 
Ronnie Sahlberg said:
The issue with this game is that is has an unusual structure.
Almost all games have a SYSTEM.CNF file that indicates which file it should boot and which also contains the disc-id.
This game does not so I will need to try a different way to determine the disc id.
I think I might be able to read the disc-id based on the cdrom volume label that is stored at 0x8028 but I will not have time to test this until sunday.
Click to expand...
Additionally, all games that have to fall back on this method of obtaining title ID may also need Demo One's PPF to fix boot issue if it is a non-JP region title.


Temperature said:
PS1_Emulation page on PS3 Dev Wiki.

This was last updated on August 16th. Does new information about what's being learned here need to be added?
Click to expand...
https://www.psdevwiki.com/ps3/Talk:PS1_Emulation#External_Configs
 
Ronnie Sahlberg said:
The issue with this game is that is has an unusual structure.
Almost all games have a SYSTEM.CNF file that indicates which file it should boot and which also contains the disc-id.
This game does not so I will need to try a different way to determine the disc id.
I think I might be able to read the disc-id based on the cdrom volume label that is stored at 0x8028 but I will not have time to test this until sunday.
Click to expand...
maybe having no ID at all, cause of PSX.EXE being main executable, which gets loaded by bios automatically without any SYSTEM.CNF. how about region detection by scanning SYSTEM.CNF instead of executable? though, this won't help with games having no .CNF file. I also will look for another title and region detection, cause I am rebuilding all my PSX isos with Xploder added, named PSX.EXE. on Cobra side, I have fixed it, but would be nice, if your app would also work with PSX.EXE
 
mrjaredbeta said:
So the decrypted config patch fails on PS3 due to some extra checks I think. It works on RPCS3, though. So, the only way to insert custom configs would be to resign them (with sign3), and re-encrypt the DAT to EDAT (with something like TrueAncestor EDAT Resigner).
Click to expand...
I have tried it and removed old signature on bottom and calculated new one with sign3, but the game does not load because of config error. this was with an official config
 
haxxxen said:
I have tried it and removed old signature on bottom and calculated new one with sign3, but the game does not load because of config error. this was with an official config
Click to expand...
Hm, could you post the config you are working with? If you are encrypt the DAT after resigning, then it should in theory work fine. Otherwise, issue is probably with config itself.
 
I get this error message when creating a pkg of the Demo 1 disc.
Pop-fe stops within seconds of creating the pkg and there is no pkg file created.
v0Mn9p4.png
 
mrjaredbeta said:
Additionally, all games that have to fall back on this method of obtaining title ID may also need Demo One's PPF to fix boot issue if it is a non-JP region title.
Click to expand...

Ok, but since this ppf just changes the magic string to match NTSC-J then applying the PPF will basically be a no-op if the title is already NTSC-J. In other words, I can just unconditionally apply this ppf for any/all games that lack a SYSTEM.CNF and where I need to discover the disc id a different way.
 
You must log in or register to reply here.

Similar threads

Back
Top