Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
I did some testing with a DualSense controller connected via Bluetooth (Windows 11). I have a 120 Hz G-Sync screen with v-sync enabled. All measurements were done with CapFrameX, using RTSS to show its overlay.
The fps I get with each controller are very stable, but the exact number depends on which controllers the game sees in which order.
[*}When I start with Xbox, switch to DualSense (by disabling HidHide), and go back to Xbox (by re-enabling HidHide), the frame rate stays at 23 fps.
GPU load scales precisely with FPS (RTX 4090):
CPU utilization however is a bit weird (Ryzen 9 5900X):
While GPU load behaves just as expected, the CPU utilization seems to be completely independent from the frame rate, so I did some more testing with Xbox controller:
This made me wonder whether the game behaves differently with v-sync disabled. And yes, it does, in very interesting ways:
All of those numbers are perfectly reproducible, no matter how often I restart the game.
Conclusio:
Edit:
Using a wired connection does fix the issue with the DualSense! However: Not when DS4Windows emulates a PS4 controller, in which case the game still drops down to 80 fps. Not an issue, but an interesting observation.
BOTTLENECK varies by the game.
If you want to know by how much your CPU is the bottleneck the best way is to:
a) set "Prefer Maximum Performance" in the NVidia CP (per-game or Global) to prevent frequency drops of the GPU
b) ensure no FPS cap (including VSYNC if that's capping things) in the game
c) observe the "GPU Usage" via an OSD tool (if it's 80% for example, then the per-core CPU processing power needs to be 1.25x faster. To oversimplify.)
When I did my research to buy the RTX4070 to pair with my R9-3900x I discovered that a lot of NEWER games started to be fairly CPU bottlenecked with an RTX4080 or above.
Baldur's Gate III needs a very top-end CPU at times to even hit 60FPS. My Ryzen 3000 probably drops to 40FPS at times.
There's a bit of a MYTH that you don't need much CPU power at 4K. The load shifts TOWARDS the GPU but the CPU load is still higher as the resolution increases, so given enough difference in CPU vs GPU the bottleneck can easily be on the CPU.
Many tasks related to ray-tracing, or keeping track of characters or whatever are still limited by some combo of per-core processing and number of cores.
TLDR: RTX4090 with an R7-3700x will have a lot of games bottlenecked by the CPU. Depending on the games played, however, it doesn't necessarily mean that upgrading the entire system makes sense either. There's always a bottleneck somewhere.
(TBC, you have to look at "GPU Usage" because CPU usage on its own tells you very little as you can have 30% CPU usage and still be having a CPU bottleneck as games can effectively use only so many of the CPU's cores. The GPU can be sort of thought as a single core where 100% is full usage and 50% (at max frequency) is using half the GPU's potential.)
xbox os is also windows based
I thought it was a gpu problem until I saw a mention of that bug somewhere. Since I own a PS4 controller I decided to test it, fixed everything!
EDIT: TEMPORARY FIX!! Lower Controller speaker volume to 0%
Buttery smooth 60 FPS with no screen tearing at 4k (FSR) Very high settings.
That bug needs fixing, I want those sweet adaptive triggers!
Also, Windows had major issues with XBox Controllers on and off for the last several years, including 2024 (2023 for sure). So if Microsoft can't keep the XBox controller functioning reliably on their own OS I can imagine Sony might have even more difficulty.