Knights Contract [BLUS30582]

RPCS3 v0.034-17098-2262ac16 Alpha

In-Game at least- with default settings, more playtesting needed to confirm full playability but seems to run perfectly so far with default settings.
Has an entry for another region in Playable state, so it likely is, but will keep testing.

*******************************

Upscaling introduces stuttering in cutscenes, but I was able to fix it running at 300% / 4K using these settings:

Note- Recording with RPCS3 brings back the stutter. However, using a 3rd party capture tool- ApowerREC -there was still stutter but very minimal and playable.
Also, it oddly performed better with the RPCS3 Performance Overlay on. But if not recording, there should be no issues.


Advanced>GPU

-Handle RSX memory tiling
-Disable Vertex Cache
-Prefer Exclusive Fullscreen
-VBlank NTSC Fixup (Left at 60Hz Default Value)

Advanced>Core

-Accurate RSX reservation access
-Accurate SPU DMA

GPU>Renderer

-Anisotropic Filtering x16
-AA Auto
-ZCULL Precise
-Shader Quality Ultra

GPU>Resolution

-Default Res 720p
-Res Scale 300% 3840x2160

GPU>Additional

-VSync
-Multithreaded RSX
-Asynchronus Texture Streaming

CPU>SPU

-Mega SPU Block Size

*******************************

Images of settings with Main Window in full view for clarity & transparency.

CPU

   

GPU

   

Audio

   

   

I/O

   

System

   

Network

   

Advanced

   

   

Emulator

   

   

*******************************

I checked with the rules below and do not see any settings I listed that would violate them.
Note- I did not see a Debug tab, I saw there is Console Debug Mode but didn't use that setting in the end because it had no effect on the cutscene stuttering.

"Using any of the following settings is not allowed for compatibility reports:
- CPU: SPU Block Size: Giga
- CPU: SPU XFloat Accuracy: Relaxed
- GPU: Shader Mode: Shader Interpreter only
- Advanced: Debug Console Mode: ON
- Advanced: Disable On-Disk Shader Cache: ON
- Advanced: VBlank Rate: Non 60Hz value
- Advanced: Clocks Scale: Non 100% value
- Any setting in the Debug tab"


*******************************

Log File, split into two logs due to size constraints.


  RPCS3 Log Part1.7z (Size: 8.33 MB / Downloads: 0)


  RPCS3 Log Part2.7z (Size: 7.64 MB / Downloads: 0)

*******************************

Link to Gameplay Video

https://youtu.be/n3S40dEx5OI

*******************************

Final caveat is that I am running on Alder Lake as you may have noticed,
it doesn't always play nice with everything but it did play with default settings with no problems.
So, mileage with these settings may vary on other CPU architectures and require tweaking.
Though for me, adding or removing any more settings than I listed brings back cutscene stuttering.
I would try the settings for yourself and tweak if not running smoothly.

So I was able to play through the whole game with upscaling using the aforementioned settings.

The cutscenes would still stutter sometimes, but usually play no problem.

I would still call it Playable, however there was a boss fight with broken graphics at Episode 16: Cutting Ties.
There is one side of the battle area that it displayed normally, so I got through it with restrained movement.
There were not broken graphics in any other fights or any aspects of the game.

So, while the cutscenes can still stutter- it's not so bad you can't follow them and they usually correct themselves and stop stuttering as they play out- not game breaking and can recommend for 99% of the game.
However that 1% I would consider game-breaking, even if I managed to find a janky way it would still work, most people probably would not. Have to recommend playing this fight at default settings, I tested the fight in default settings and it plays without any graphical issues.

Gameplay capture displaying the fight playing with graphical issues in 4K, then playing perfectly with Default settings:
https://youtu.be/cBWKyZmi_YY

Being that the game needs only to be fully playable at default settings, I can now verify it is indeed in a fully Playable state by RPCS3 standards. 🙂

Edit: Post-Completion log files now attached below.


  (11-13-24) RPCS3 Log Part 1.7z (Size: 4.96 MB / Downloads: 0)


  (11-13-24) RPCS3 Log Part 2.7z (Size: 4.84 MB / Downloads: 0)