PS4 [Research]PS2 emulator configuration on PS4

Can you explain, why this is set in your config? "Verbose" to me is something you enable, when you want to log or debug commands.
How is this different to --cdvd-sector-read-cycles ?
I think it was random value to test :D
Yeah, that should take 0 or non 0 as param. Also 0 will be better probably. Seems to be logging option only.
 
--fpu-accurate-range=0x162800,0x162900 Found it!

Proper fix for Need for Speed Carbon

cli
Code:
--host-audio-latency=2.77

--verbose-cdvd-reads=700

--gs-uprender=2x2
--gs-upscale=edgesmooth
--gs-optimize-30fps=1

--fpu-accurate-range=0x162800,0x162900

--ee-cycle-scalar=1.35

--vu1-mpg-cycles=1170

--vu0-opt-flags=1
--vu1-opt-flags=1
--cop2-opt-flags=1
--vu0-const-prop=0
--vu1-const-prop=0
--vu1-jr-cache-policy=newprog
--vu1-jalr-cache-policy=newprog
--vu0-jr-cache-policy=newprog
--vu0-jalr-cache-policy=newprog

2x2 for those that need it.

Got it working using Kinetica v2. JakX v2 and Jak2 v2 crash for me. Even with uprender/upscaler the game really looks pixelated. Tried fo force progressive/480p in cli and even tried to patch the elf directly in lua. Still the game looks like NFSC Minecraft Edition. NFSU, NFSU2 and even HP2 don't suffer from this. Can some of the "cycle" commands cause this to not tolerate uprendering?
 
Got it working using Kinetica v2. JakX v2 and Jak2 v2 crash for me. Even with uprender/upscaler the game really looks pixelated. Tried fo force progressive/480p in cli and even tried to patch the elf directly in lua. Still the game looks like NFSC Minecraft Edition. NFSU, NFSU2 and even HP2 don't suffer from this. Can some of the "cycle" commands cause this to not tolerate uprendering?
Can you post picture? Hard to judge without comparison :P
 
1.jpg
2.jpg
3.jpg
4.jpg


This even looks worse, when you play it. HP2 (last picture) looks okay.
 
That doesn't necessarily mean it won't upscale. More like some post processing get messed, or something. Algo for uprender is quite simple, but if that algo get wrong data, it will uprender wrong data.
Try --gs-kernel-cl-up="up2x2simple"
But it seems that game for some reason produce some bad overlay.
EDIT: Well, more i'm looking on that, more i think that is static blur effect that get messed up.
EDIT2: try also --gs-upscale=point
 
Last edited:
Emus tried

all the Jak type = crash at fpu clamp location
red faction 2 = crash at fpu clamp location


kinetica=works with no upscale
 
WIll try some other emus. Bully, Warriors, MSlug(A), KOF2000 seem to be some good candidates.

-- crashing
-- working, no upscale
 
Last edited:
Nothing too special. But here we go. My first attempts to optimize some games:

SLUS-20362_config.lua

(Need for Speed - Hot Pursuit II)
Code:
apiRequest(1.0)
local eeObj = getEEObject()
local emuObj = getEmuObject()

-- Proper 16:9 (Widescreen)
local widescreen = function()
eeObj.WriteMem32(0x00280734, 0x3c050000) -- Progressive/480p forced
eeObj.WriteMem32(0x0028073c, 0x3c060050)
eeObj.WriteMem32(0x00280744, 0x3c070001)
eeObj.WriteMem32(0x0010e994, 0x46011702) -- Widescreen
eeObj.WriteMem32(0x0032f6ec, 0x3f400000)
eeObj.WriteMem32(0x0032f850, 0x3f2aaaaa)
end
emuObj.AddVsyncHook(widescreen)

-- Fix shadow
emuObj.SetGsTitleFix( "forceSimpleFetch", "reserved", { texMode=1 } )

SLUS-20811_config.lua
(Need for Speed Underground)
Code:
apiRequest(1.0)
local eeObj = getEEObject()
local emuObj = getEmuObject()

-- Proper 16:9 (Widescreen) + FMV Fix
local widescreen = function()
eeObj.WriteMem32(0x00229da8, 0x3c01bf2a) -- FMV
eeObj.WriteMem32(0x00229dac, 0x44816800)
eeObj.WriteMem32(0x00229ddc, 0x46007307)
eeObj.WriteMem32(0x00229de0, 0x46006bc7)
eeObj.WriteMem32(0x003af854, 0x3c050000) -- Progressive/480p forced
eeObj.WriteMem32(0x003af85c, 0x3c060050)
eeObj.WriteMem32(0x003af864, 0x3c070001)
eeObj.WriteMem32(0x004ff434, 0x3f24a9cf) -- Widescreen
eeObj.WriteMem32(0x004ff628, 0x3f470000)
eeObj.WriteMem32(0x004ff630, 0x3f470000)
end
emuObj.AddVsyncHook(widescreen)

-- Fix shadow
emuObj.SetGsTitleFix( "forceSimpleFetch", "reserved", { texMode=1  } )

config-emu-ps4-txt
Code:
[...]
#Default clamping
--fpu-no-clamping=0
--fpu-clamp-results=1
--vu0-no-clamping=0
--vu0-clamp-results=1
--vu1-no-clamping=0
--vu1-clamp-results=1
--cop2-no-clamping=0
--cop2-clamp-results=1
#30fps games
--gs-optimize-30fps=1

NFSU has some slowdowns and audio glitches in the main menu, while accessing the memory card. In-game is okay. But this is also true for PCSX2 - at least on my Windows box.
HP2 seems to be okay. I tested the patches for the 60fps mode. I wouldn't recommend turning this on. I guess the PS4 hardware is just too weak for this.

Tested on PS4 Pro/Jakv2
Next I will try to get Burnout Dominator working. Or at least "bypassing" the freezing car selection screen. ;-)
what emu u use for these games?
 

Similar threads

Back
Top