PS4 [Release[ PS2-FPKG 0.6 by Jabu - New tool to convert PS2 games for PS4

Status
Not open for further replies.

kozarovv

Developer
New Thread (v0.7 was a complete rewrite of the app):
https://www.psx-place.com/threads/r...of-my-ps2-to-ps4-converter.41916/#post-374371


PS2-FPKG v0.6 by Jabu
This app convert PS2 ISO/BIN games to fPKG which can be installed directly on PS4.​


unknown.png


How to use:
  1. Run ps2-fpkg.exe
  2. Select the ISO of the PS2 game in "Disc1"
  3. Click "Create fPKG" and choose a storage location
  4. Install created fPKG on PS4 and play
Note: For CD games (.bin) click YES when asked about adding LIMG sector.


Optionally you can:
  • change the game icon (Icon),
  • change background graphic when starting the game (Bg),
  • create a multi-disc game (up to 5 iso)
  • add your own config txt,
  • add your own config lua,
  • select the emulator to be used by the game (by default there are 2 known to be most compatible, you can throw more here)
  • import custom 8MB memory card (.ps2, .vm2, .bin [OPL VMC])
  • Customize PS Vita remote play key bindings
  • Customize the lightbar colors
  • Use FastForward (works best on loading screens)

Program automatically adds configs (config-emu-ps4.txt), ps3 (gameid_lopnor.cfgbin), lua (gameid_config.lua) if they exist in application database.
Yes, this application comes with unique ready to go PS2 game configs that will be added automatically!


Known bugs:
  • Few games not follow SYSTEM.CNF standard layout, for this games app will fail to find ID (partially fixed, only CD games affected now)
  • If program has any problems with creating fPKG, you can try to run it as an administrator, it should help.
  • App will fail to create pkg if path to save pkg is root of drive, like C:\ E:\. Fix it by creating pkg to for example E:\pkg
  • Memory cards greater than 8MB not work. This is emulator limitation, not app itself.
  • crc.exe may be detected by some lame anti-viruses as malware, THIS IS A FALSE POSITIVE!
  • Widescreen Patches won't work with CD(in .bin format) games

How to enable Widescreen Patches:
Check the "Widescreen Patches" checkbox in the "Graphics Settings" tab.
It's not enabled by default because it needs some more testing. This setting will be saved.
If the app finds a widescreen patch for your game, it will be automatically used.

How to add more emulators:
Put the folder with emulator files into the "emus" folder, restart ps2-fpkg,
new emulators should show up on the list, that's all.


A short demonstration of the program operation can be seen here:

Fast Forward demo:

CHANGELOG:

v0.6

  • Command line window is now hidden, animated "Creating PKG" text on the status bar is now shown instead
  • The main window won't freeze anymore while creating a PKG (pkg creation process was moved to different thread)
  • PKG creation errors will now show up in a window
  • Added settings for uprender, upscale, and display mode in the new "Graphics Settings" tab"
  • Added a FastForward option, this allows you to set a custom combo to remove the framelimiter, and for example speed up loading screens or FMVs, or even gameplay sometimes.
  • FastForward option is available in 2 modes. Hold the combo to fastforward or press a combo to toggle it on/off.
  • Added a option to change the DS4 Lightbar color for normal gameplay and for fast forward mode.
  • Added game elf CRC reading to allow imported widescreen patches to be found by the app(via crc.exe)
  • Added auto widescreen patches (3700 patches fetched from pcsx2 repository)
  • "Try to fix graphics" is now enabled by default
  • Some GUI changes
  • More broken english

v0.5

  • Added OPL's Virtual Memory Card (.bin) support
  • You can now select a Keymap layout for Vita Remoteplay
  • fixed some code, again

v0.4

  • custom Memory Card support! You can now import your .vm2/.ps2 memory card's from a ps3 or pcsx2, it should work in all games.
  • gui now use tabs
  • jpg/bmp support added for custom icon/bg
  • removed "try to improve compatibility"
  • added "Try to improve Speed" should fix games like GOW 1 and 2, may break some others(this may not work on some emulators)
  • added "Try to fix Graphics" fixes AirBlade, Frogger: Ancient Shadow, God Hand, SpongeBob SquarePants: Battle for Bikini Bottom, and maybe others.
  • fixed some code

v0.3

  • added compression support
  • added PS2 CD .bin support(app wil auto-add LIMG sector)
  • fixed DVD game ID searching code, it's fast now
  • limited "Try to improve compatibility" option to JAK v2 emu, Rogue emu not support that option
v0.2
  • initial release


Files used:


Used programs:


Credits:
Thanks Kozarovv for help, and suggestions. @Zar for his ps3 configs database. Veritas83 (@VTSTech ) for PS2 GAMEID TITLE database.

Download: http://www.mediafire.com/file/n83i3qbk9oyzgjg/PS2-FPKG+v0.6.7z/file
 
Last edited by a moderator:
There's an error with the PS2-FPKG.exe file during extracting in both 7zip and Winrar
 
Last edited:
Is it possible to add FPKG compression option in a future release?
Yes that should be possible.
Very good tool, which can create PS2 PKG more conveniently and quickly:D
Yep, and allow to auto add configs from PS3. So few games should work better, for example MX vs. ATV Unleashed, Spyro, Tourist Trophy licences should work now, many minor accuracy issues that aren't noticeable at first play.
There's an error with the PS2-FPKG.exe file during extracting in both 7zip and Winrar
Weird, maybe download failed in the middle?
-----------------------------
This app was in development for some time, even yesterday some minor bugs were squashed before release. I think is good time for release it to public, to get rid of eventual bugs before new exploit will be released, and PS2toPS4 scene will back to live for good. :)
Also please report if any game work worse with "Try to improve compatibility" option. This shouldn't happen, but is something that need some testing on more examples.
 
Am I doing something wrong? Am I missing something? I can't seem to get it to work.
dark.png

dark2.png

The moment after I click OK, pkg.exe immediately closes and does nothing. I've tried with at least 4 games. Tried with games that have LUA/PS3 configs too, got the same result.
 
Am I doing something wrong? Am I missing something? I can't seem to get it to work.
dark.png

dark2.png

The moment after I click OK, pkg.exe immediately closes and does nothing. I've tried with at least 4 games. Tried with games that have LUA/PS3 configs too, got the same result.
If such an error occurs, after clicking Create fPKG, you can directly click the X button in the upper right corner of the small window, and it will create it. This is the only method I have found now.
 
Am I doing something wrong? Am I missing something? I can't seem to get it to work.
dark.png

dark2.png

The moment after I click OK, pkg.exe immediately closes and does nothing. I've tried with at least 4 games. Tried with games that have LUA/PS3 configs too, got the same result.
Weird, did you tried to run as admin?
  • If program has any problems with creating fPKG, you can try to run it as an administrator, it should help.
Edit: Also this app is not compatible with Windows XP (and never gonna be), so if you are using it, that can be issue.
If such an error occurs, after clicking Create fPKG, you can directly click the X button in the upper right corner of the small window, and it will create it. This is the only method I have found now.
You mean that click X to close that window, instead of clicking OK fix it?
 
You mean that click X to close that window, instead of clicking OK fix it?[/QUOTE]

No, sometimes clicking X to close the window will create it automatically
 
Am I doing something wrong? Am I missing something? I can't seem to get it to work.
dark.png

dark2.png

The moment after I click OK, pkg.exe immediately closes and does nothing. I've tried with at least 4 games. Tried with games that have LUA/PS3 configs too, got the same result.
Ok, i was able to reproduce that. Issue seems to exist only when path to save PKG is root of drive. Like C:\ or E:\ . Try create fpkg to some folder, like for example E:\pkgs
Maybe you @nifengyuexia will be able to confirm?
 
Ok, i was able to reproduce that. Issue seems to exist only when path to save PKG is root of drive. Like C:\ or E:\ . Try create fpkg to some folder, like for example E:\pkgs
Maybe you @nifengyuexia will be able to confirm?
No, this only happens when applying a configured game. But there is no big impact. In short, it is a very good program, I hope it continues to be updated.
 
No, this only happens when applying a configured game. But there is no big impact. In short, it is a very good program, I hope it continues to be updated.
Ok, thanks for the report. We will try to track down that issue with developer. So this happen for you when adding custom config, right? Did you noticed that lua, or txt make difference?
Also some new exciting features are coming. One is compression, that was requested by @Vegeta . About another one i can't tell yet, but is something that any other application can't do, and is really simplifying some process. :D
 
Ok, thanks for the report. We will try to track down that issue with developer. So this happen for you when adding custom config, right? Did you noticed that lua, or txt make difference?
Also some new exciting features are coming. One is compression, that was requested by @Vegeta . About another one i can't tell yet, but is something that any other application can't do, and is really simplifying some process. :D
The program will automatically match the known configuration before it happens, like games without configuration will not have this problem. LUA and TXT are useful, and in the default TXT configuration, the default configuration of PCSX2 is added. Although some games have a PS3 configuration, they do not work, such as: The Dark Curse of Castlevania. Some configurations I posted on the forum, I hope to be adopted, please believe me, this is the result of a lot of tests I have done:D
 
The program will automatically match the known configuration before it happens, like games without configuration will not have this problem. LUA and TXT are useful, and in the default TXT configuration, the default configuration of PCSX2 is added. Although some games have a PS3 configuration, they do not work, such as: The Dark Curse of Castlevania. Some configurations I posted on the forum, I hope to be adopted, please believe me, this is the result of a lot of tests I have done:D
Ok, i messed with it little bit, and I was able to reproduce your issue when i used path to app like (please ignore what it means, i copied it from google)
Code:
D:\_Pobrane\PS2-FPKG_v0.2Pe̍h台灣語言

When i added Pe̍h台灣語言 to my app path, it wasn't able to create pkg. Can you test that path to your app have some special characters like that?
 
Although some games have a PS3 configuration, they do not work, such as: The Dark Curse of Castlevania.
Ah yes, that is known to work like that. But game boot like before right? I reversed emulator, and noticed that when unsupported ps3 config is used, emu just ignore it. So we decided with developer to add all known PS3 configs, as in worst case it will just do nothing (like for castlevania).

and in the default TXT configuration, the default configuration of PCSX2 is added.
This is what option "Try to improve compatibility" do ;) You can always turn it off when some game have issue with it. :)

Some configurations I posted on the forum, I hope to be adopted, please believe me, this is the result of a lot of tests I have done:D

Yes, I plan to collect all known configs from forum, also I'm gonna port MANY configs from pcsx2 gameindex.dbf. But this need to wait for 0.4 release. :)
 
Ok, i messed with it little bit, and I was able to reproduce your issue when i used path to app like (please ignore what it means, i copied it from google)
Code:
D:\_Pobrane\PS2-FPKG_v0.2Pe̍h台灣語言

When i added Pe̍h台灣語言 to my app path, it wasn't able to create pkg. Can you test that path to your app have some special characters like that?
I just tested it again, different drives, different paths, different names, no problem, it looks like it is random, which is a bit of a headache:(
 
I just tested it again, different drives, different paths, different names, no problem, it looks like it is random, which is a bit of a headache:(
Ok, big thanks for testing. For now it will stay like that, but developer will try to use different pkg.exe app, maybe that will resolve it.
 
Last edited:
Status
Not open for further replies.
Back
Top