PS2 Classics Emu Config File Help

[Subaru_Forester]

Hi all,

I'm new here so if I'm posting in the wrong place just let me know. I was trying to get my backup of .Hack//Infection working on my PS3, but can't figure out the config file needed to keep it from crashing early in the game. I read the resources, but can't wrap my head around it.

The config file for it, listed here:

https://www.psdevwiki.com/ps3/PS2_Emulation#Official

is just listed as ALL and I can't find that one in the included in the collection of config files that I got included when I installed the PS2ClassicsGUI. It's probably something really dumb I'm missing here, but I just need a little guidance.

Thanks everyone!!

 

[Coro]

what is your model number? cech-??

managunz is often recommened because it includes config files. webman mod has an addon pkg for it.

some configs are encrypted and some are not if i understand right.

 

[Subaru_Forester]

I've got a 4001-B. I've been making the pkgs on my laptop then importing them over for installation on my PS3.

 

[Coro]

I've got a 4001-B. I've been making the pkgs on my laptop then importing them over for installation on my PS3.

okay webman mod can use configs too but i think managunz does it automatically.

 

[Subaru_Forester]

okay webman mod can use configs too but i think managunz does it automatically.

Cool. I'll play around with that method tonight. I just couldn't find anything directly addressing what I was trying to do with PS2GUI

 

[sandungas]

Think in it this way, we can load PS2 games in 2 different formats
The "PS2 classics" uses the firmware official functions, not modifyed, the only thing we do to build them is decrypting/encrypting files, because we have the keyz
And when you load the PS2 game as a plain ISO we are using "cobra" to do the encryption/decryption magic and we are patching the emulator files

With the official "PS2 classics" format the ISO and the CONFIG are encrypted... and with cobra are not encrypted
The use of non-encrypted files is a custom feature

So... if you are in CFW is more convenient to load the PS2 games as a plain ISO and with a plain CONFIG because is more straightforward and we are removing "protection layers" that are pointless, but you can use both formats
In HAN/HEN is not posible to patch the emulator files, so the only way is by using the "PS2 classics" format, and for it to work everything needs to be encrypted

ManaGunz contains the complete collection of CONFIG files in non-ecrypted format, for the purpose of loading a plain ISO, but it doesnt have support for the "PS2 classics" format
That support of the "PS2 classics" format is really a trick, we install a single "PS2 placeholder" app, and when you want to load a different PS2 game the backup managers replaces the files inside that directory (so the PS3 thinks the contents of the "PS2 placeholder" directory are always the same game)

 

[Subaru_Forester]

Think in it this way, we can load PS2 games in 2 different formats
The "PS2 classics" uses the firmware official functions, not modifyed, the only thing we do to build them is decrypting/encrypting files, because we have the keyz
And when you load the PS2 game as a plain ISO we are using "cobra" to do the encryption/decryption magic and we are patching the emulator files

With the official "PS2 classics" format the ISO and the CONFIG are encrypted... and with cobra are not encrypted
The use of non-encrypted files is a custom feature

So... if you are in CFW is more convenient to load the PS2 games as a plain ISO and with a plain CONFIG because is more straightforward and we are removing "protection layers" that are pointless, but you can use both formats
In HAN/HEN is not posible to patch the emulator files, so the only way is by using the "PS2 classics" format, and for it to work everything needs to be encrypted

ManaGunz contains the complete collection of CONFIG files in non-ecrypted format, for the purpose of loading a plain ISO, but it doesnt have support for the "PS2 classics" format
That support of the "PS2 classics" format is really a trick, we install a single "PS2 placeholder" app, and when you want to load a different PS2 game the backup managers replaces the files inside that directory (so the PS3 thinks the contents of the "PS2 placeholder" directory are always the same game)

Alright, here's what I did. Since I have one of the later 4001 models (A shame, my PS3 I got on launch died on me a few years ago), I can't really run most of the easier methods (That I know of).

I basically have to use the PS2 Classics trick. I needed the config file for .Hack//Infection, but didn't know how to get it or how to use the data presented and make my own. So I used ManaGunz anyway and this happened to put the correct config file in my HDD PS2 ISO folder when I tried to run the .Hack//Infection ISO that I had. I took that config file and then used my original method of PS2GUI on my laptop to create the pkg for the PS2 Classics trick.

So far, it has worked. About 40 minutes into the game and I've gotten past all the previous hang ups/crashes I had before. There are some weird shadowy textures that appear in the cut scenes time to time, but other than that, it seems to be holding up pretty well.

 

[Coro]

@Subaru_Forester you can get unencypted config files here. if your ps2 game is available as a real ps2classic (if it is sold on psn) then the file you need if probably under net folder. other games may be under custom folder. some games do not have configs. some configs dont fix all problems. use ps2classics gui to add the config file when you make the package.

you may find some ps2 games run better turning off "smoothing" under game settings in the xmb (under the system update icon). you can also stretch the video under that menu.

 

[Subaru_Forester]

@Subaru_Forester you can get unencypted config files here. if your ps2 game is available as a real ps2classic (if it is sold on psn) then the file you need if probably under net folder. other games may be under custom folder. some games do not have configs. some configs dont fix all problems. use ps2classics gui to add the config file when you make the package.

you may find some ps2 games run better turning off "smoothing" under game settings in the xmb (under the system update icon). you can also stretch the video under that menu.

Thanks for that Coro! I've got all of them. In the compatibility chart I linked in my original post, it just shows .Hack//infection's CONFIG ID as ALL. I wasn't really sure what that meant. I read most of the available info and still couldn't decipher it. I think I fixed it though. It took some back and forth, but I used ManaGunz to pull the one it had and then copied it over for the pkging program I have on my laptop. Definitely wasn't the most technical approach, but so far it's worked haha

 

[Coro]

Thanks for that Coro! I've got all of them. In the compatibility chart I linked in my original post, it just shows .Hack//infection's CONFIG ID as ALL. I wasn't really sure what that meant. I read most of the available info and still couldn't decipher it. I think I fixed it though. It took some back and forth, but I used ManaGunz to pull the one it had and then copied it over for the pkging program I have on my laptop. Definitely wasn't the most technical approach, but so far it's worked haha

i meant to link this a second ago. it tells which games work and some problems they have so you dont waste time making pkg that dont work right. if it says ps2 classic in green then use the config under net folder. other are probably in custom folder.

https://www.psdevwiki.com/ps3/PS2_Classics_Emulator_Compatibility_List