正在加载视频...

视频加载失败

Replaying Pokémon Omega Ruby on my AYN Thor at 4X resolution scaling with HD textures, the black outlines disabled, at 60 FPS, and it's given me a brand new appreciation for how gorgeous the game is 🤯

10,885 次观看 • 8 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Wuthering Waves PS5 Performance Test • Test Setup PS5 Slim (brand new, clean, no dust) Room temperature: 22°C with AC • Map Issue Yes, it's real. The new map is locked to around 2 FPS when opened from the menu, making it extremely laggy. • Stuttering Problems The game has severe stuttering. In some areas, it even freezes for 4–5 seconds, making the experience frustrating. • My Observation From my testing, the game appears to be running at a very high internal resolution on PS5 instead of relying on aggressive upscaling. For example, DLSS Quality at 1440p renders the game internally at approximately 1707×960 before upscaling it to 2560×1440. On PS5, however, it looks like the game is rendering at or near 2560×1440 internally and then upscaling to 4K. If that's true, it's an extremely demanding target for a base PS5. • Is This Fixable? Yes. If the game is indeed using such a high internal resolution, lowering it and using better reconstruction or dynamic resolution scaling could significantly improve performance. Running at such a high internal resolution on a base PS5 doesn't make much sense, and the game has suffered from performance issues for nearly 12 months. • Final Thoughts Kuro Games needs to address this. At this point, we can't keep blaming players, their hardware, or the engine. If the high internal resolution is the cause, it should be adjusted. If it isn't, then something else in the game's optimization is seriously wrong. #WutheringWaves #Gacha

Kaito

49,355 次观看 • 1 个月前

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 次观看 • 6 个月前