05-19-2020, 12:14 PM -
Hello, I'm a new member, great to be here and all that bumff.
Right, straight to business... I got bored being in lockdown so I went through every option in RPCS3 and the custom config to find out how to run InFamous a bit better and squeeze out every last drop of FPS and so here is my report.
Title specifics: BCES00609
System: Ryzen 1700X - Radeon RX 5700 XT - 16GB of mammaries.
RPCS3 version: 0.0.10-10406-3d320aea Alpha
RPCS3 global settings: Default settings except for the following..
Anti-Aliasing = Disabled (I kept getting an RPCS3 warning about my card not liking MSAA so I disabled it globally)
Max LLVM Compile Threads = 14 (I have 16 in total and like to keep 2 for background tasks)
BCES00609 custom settings:
SPU Decoder = LLVM (default anyway)
Enable SPU loop detection = unchecked (slight fps increase but big stability increase/less stuttering)
Preferred SPU Threads = 6 or lower (I found that PPU and RSX need almost as many threads as SPU, for my Ryzen the ideal number was 6 threads for SPU and 10 to be shared between PPU and RSX)
Renderer = Vulkan (default anyway)
Strict Rendering Mode = checked (this cleaned up the graphical issues such as the broken glass on the ground which looked like purple wire-frame blocks without this setting)
Disable On-Disk Shader Cache = checked (this made the biggest difference, an extra 7fps in every scene!)
Alterations to config_BCES00609.yml:
'Disable FIFO Reordering: true' (this got me an extra 1 or 2 fps overall)
Results:
Solid 30fps during Sony and Sucker Punch cinematics (to be expected)
21fps during the "Press Start" screen at beginning of intro sequence.
45fps at moment of nuclear flash after pressing Start.
Between 18 and 27fps during the hectic "people fleeing" scene (this is where audio begins to stutter)
37fps during the aerial shot of the blast.
Since I must have restarted the game 60 or 70 times during these tests I didn't bother to go any further than the above scenes or it would have taken me all day to get through all of the options in the config file. I also just assumed that any difference I saw during the intro sequence would likely be replicated in the game anyway.
Two final notes:
1.) I tried ASMJIT as SPU decoder but the ingame difference was negligible while the difference during the two intro cinematics (Sony and Sucker Punch) was huge, they both dropped from a solid 30fps to around 6fps, so ASMJIT clearly isn't beneficial for my setup.
2.) Disabling Thread Scheduler while enabling Lower SPU Priority seemed to give an fps boost when I first did these together but the boost wasn't permanent and disappeared the next time I loaded the game, then after some playing around with other settings I tried these two again and got the same boost, so I don't know if it is maybe related to something that was cached or not but these two options have promise, they just aren't consistent. Sometimes the game runs faster, sometimes it does not.
I might follow this up with further experimentation in other titles unless I die from the virus.
krashd aka Rob
Right, straight to business... I got bored being in lockdown so I went through every option in RPCS3 and the custom config to find out how to run InFamous a bit better and squeeze out every last drop of FPS and so here is my report.
Title specifics: BCES00609
System: Ryzen 1700X - Radeon RX 5700 XT - 16GB of mammaries.
RPCS3 version: 0.0.10-10406-3d320aea Alpha
RPCS3 global settings: Default settings except for the following..
Anti-Aliasing = Disabled (I kept getting an RPCS3 warning about my card not liking MSAA so I disabled it globally)
Max LLVM Compile Threads = 14 (I have 16 in total and like to keep 2 for background tasks)
BCES00609 custom settings:
SPU Decoder = LLVM (default anyway)
Enable SPU loop detection = unchecked (slight fps increase but big stability increase/less stuttering)
Preferred SPU Threads = 6 or lower (I found that PPU and RSX need almost as many threads as SPU, for my Ryzen the ideal number was 6 threads for SPU and 10 to be shared between PPU and RSX)
Renderer = Vulkan (default anyway)
Strict Rendering Mode = checked (this cleaned up the graphical issues such as the broken glass on the ground which looked like purple wire-frame blocks without this setting)
Disable On-Disk Shader Cache = checked (this made the biggest difference, an extra 7fps in every scene!)
Alterations to config_BCES00609.yml:
'Disable FIFO Reordering: true' (this got me an extra 1 or 2 fps overall)
Results:
Solid 30fps during Sony and Sucker Punch cinematics (to be expected)
21fps during the "Press Start" screen at beginning of intro sequence.
45fps at moment of nuclear flash after pressing Start.
Between 18 and 27fps during the hectic "people fleeing" scene (this is where audio begins to stutter)
37fps during the aerial shot of the blast.
Since I must have restarted the game 60 or 70 times during these tests I didn't bother to go any further than the above scenes or it would have taken me all day to get through all of the options in the config file. I also just assumed that any difference I saw during the intro sequence would likely be replicated in the game anyway.
Two final notes:
1.) I tried ASMJIT as SPU decoder but the ingame difference was negligible while the difference during the two intro cinematics (Sony and Sucker Punch) was huge, they both dropped from a solid 30fps to around 6fps, so ASMJIT clearly isn't beneficial for my setup.
2.) Disabling Thread Scheduler while enabling Lower SPU Priority seemed to give an fps boost when I first did these together but the boost wasn't permanent and disappeared the next time I loaded the game, then after some playing around with other settings I tried these two again and got the same boost, so I don't know if it is maybe related to something that was cached or not but these two options have promise, they just aren't consistent. Sometimes the game runs faster, sometimes it does not.
I might follow this up with further experimentation in other titles unless I die from the virus.
krashd aka Rob