PS4 [Research] PS2 Game Status on (PS4's - PS2 EMU)

Code:
apiRequest(0.1)

--Fix graphic issues with SPS, SCES-53851 only

eeInsnReplace(0x2E2B44, 0x4BC949FF, 0x48449000)
eeInsnReplace(0x2E2B4C, 0x48449000, 0x4BC949FF)

Use this as lua file.
 
Interestingly enough, the Snowblind engine games actually *run* pretty much perfectly in Jakv2 emulator, but there's some serious background graphics crap going on, real distortion, flickering, horrible glitches. The psdevwiki for PS3 net_emu lists a bunch of fixes. Can any of these be converted over to PS4's ps2emu?

http://www.psdevwiki.com/ps3/PS2_Emulation#Unofficial

0x3D => 0x431B (17179)
0x4A => (sets something 0x15100)


All Snowblind engine titles have the same glitch and the same fix. I tried the "usual" (heh) clutmerge commands, no go,.


How change resolution to native?

Change "uprender=2x2" to "uprender=none"
 
Last edited:
Interestingly enough, the Snowblind engine games actually *run* pretty much perfectly in Jakv2 emulator, but there's some serious background graphics crap going on, real distortion, flickering, horrible glitches. The psdevwiki for PS3 net_emu lists a bunch of fixes. Can any of these be converted over to PS4's ps2emu?

http://www.psdevwiki.com/ps3/PS2_Emulation#Unofficial

0x3D => 0x431B (17179)
0x4A => (sets something 0x15100)

All Snowblind engine titles have the same glitch and the same fix. I tried the "usual" (heh) clutmerge commands, no go,.

Sorry to nag, but do you know anything about this @kozarovv , chief?
 
Outstanding, thank you for your insight :) Honestly... the indepth nature of the emulator and commands is way over my head, so I'm really grateful you know your way around it :D

~edit~

--vif-thread-chunk-size=86272

Freezes the emulator at pic1, I guess 86272 is too high a size? 86 works, doesn't freeze, but doesn't fix the flickering/corrupted textures either. I've tried a combination so far;

--vif-thread-chunk-size=86
--vif-thread-chunk-size=86
--vu1-mpg-cycles=100
--vif-thread-chunk-size=86
--vu1-mpg-cycles=1000
--vu1-mpg-cycles=100
--vu1-mpg-cycles=1000

No go, doesn't even seem to be a difference in corruption/flickering. I'm going to try different sizes of chunks and cycles, is there a rule to the applicable sizes? 86272 and 86 seem very specific.
 
Last edited:
Btw, not sure if you was aware of this @sabin1981 but the unnofficial config used in PS3 for the PS2 games made with snowblind engine... later was replaced by official configs
Short story... in PS3 there are several PS2 emulator types, and some of them has the configs "embedded" inside the emulator.self itself (pun intended), but we was not able to see or extract that official configs. So initially it was made an unnofficial config that was fixing the problems partially

But later zar made a tool to extract the official configs from the official emulators, and surprise !... there was configs from the snowblind engines (and was different than the unnofficial config we was using)
So lets say... the unnofficial configs for snowblind engine was "superceeded" by the official configs that fixes the problems completly (and are made by sony, so we can be confident that are relliable)

You can see he ouput of the tool able to extract configs in this links:
https://github.com/Zarh/Get_CONFIG/blob/master/soft/log.txt (config info extracted from ps2_softemu.self)
https://github.com/Zarh/Get_CONFIG/blob/master/log.txt (config info extracted from ps2_gxemu.self)
 
Aw hell... official Sony fixes, and perfectly working ones too *moan* God I'd love to get those for PS4 PS2emu! Thanks for the info, bud :D It's such a shame that the PS4's PS2emu seems to be so much less capable, both in terms of compatibility and performance, than the one included in the PS3. Hell, even PCSX2 really struggles with Snowblind games and only in the last two years have they finally been fixed --- but you still need a *monster* of a PC to run them at full speed. I'm rocking a 4.3Ghz i7-3770k and a 2Ghz GTX1070, and even THIS system struggles with Snowblind games in heavy scenes. Crazy stuff.

I wish I knew enough about emulation, or had reversing knowledge, to port those fixes to PS4.. but that's beyond me :( Shame too, as it looks like they also fix MK Shaolin Monks :o
 
Chronologically, in PS3 the ps2 emulators followed this order:
ps2emu.self ---> ps2_gxemu.self ---> ps2softemu.self

The first one was for the first PS3 models that has inside the EE and GS from PS2... so is a PS2 at 95% and the emulator only does some "management"... or is working as a proxy

The second one was for PS3 models with EE, but without GS... so this one does a lot more emulation functions, and is the first version that acepts config commands

The third is the first version that mades the emulation 100% by software (for PS3 models without EE/GS)
But the core code of all them was taken from previous versions... and at this point the performance was a disaster

So they rewrote the emulator and made the ps2_netemu.self (as a replacement of ps2_softemu.self), that also does all the emulation 100% by software, but it has a big difference in how the processor threads are managed
The performance is much better, and it inherited los of stuff from previous versions (included the configs)
But some of the configs from previous versions are not 100% compatibles with this new version of the emu

For PS4 i bet they "recycled" the code from PS3... and in the same way the ps2_netemu.self for PS3 was like a rewriting of the code to adapt it better to the PS3 processor arquitecture... the one from PS4 is another rewrite to adapt it to the PS4 processor arquitecture (+ some extras like the LUA support and probably lot others)

So most of that official game config info extracted from PS3 emulators could work on PS4, with a few exceptions but this exception are not a whole config, but specific commands
Lets say a config uses command 16, 17, 18... maybe 18 is not compatible with PS4 but 16 and 17 could be
And maybe the emu inPS4 does the 18 by itself (without need for the config to tell it)

The ones that are surelly compatible with PS4 is when there is some data "patched" at a specific offset of the game (of the ISO, ELF, or the RAM). That offsets and the patched data should be exactly the same

In PS3 we have a lot of unknown commands though... we are lucky we got that official configs extracted to study them... but still is in progress :D
 
Issues:-

Fate/Stay Night [Realta Nua] = (
Playable) Graphical glitches on image transition and movement.

Example of the glitch in spoiler below
Fate_Stay%20Night%20Realta%20Nua_20180826155615_zpslhtmrs4w.jpg
 

Similar threads

Back
Top