Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

10,799 Aufrufe • vor 6 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

In my previous post about the #Nioh3 demo, I mentioned that when the game isn’t consistently holding 60 FPS or 120 FPS, several issues can show up. Here’s a clearer breakdown of what's going on. The main reason is that the game speed and physics are tied to the frame rate. When you enable the 120 FPS cap, the engine start overreacting and pushes CPU usage very high, even if the game is still running at around 60 FPS (as shown in the first example). In the second clip, you can see the uneven, jittery camera movement I mentioned before. Notice how much smoother 60 FPS and 120 FPS look compared to the unlocked side. Also, camera movement at 60 FPS is slightly faster than at 120 FPS. In the third clip, player movement is slower when the frame rate is unlocked. This doesn’t happen all the time, but it shows up often enough to be noticeable. Because of how the Katana Engine behaves, the game is clearly designed around 60 FPS. Running at 120 FPS is possible, but it’s only recommended if your system can maintain that target almost all the time, which isn’t easy to achieve. There’s also an alternative workaround where you select the 60 (locked) option and enable Frame Generation (DLSS or FSR 3), as shown in the last clip. The downside is that DLSS Frame Generation tends to show the same stuttery look as when the frame rate isn’t holding a fixed target, likely due to Reflex keeping the frame rate slightly below target. FSR Frame Generation, on the other hand, looks much smoother and works better here.

BenchmarKing

17,820 Aufrufe • vor 4 Monaten