AMD uses Xbox Game Bar and their latest chipset drivers to determine when to limit an application only to the high cache cores. Any application that Xbox game bar triggers for will likely induce the desired automatic behaviour. Try setting X4 to windowed fullscreen (recommended) and make sure your Windows 11 Xbox game bar is configured so that it detects games being run. Hopefully that should detect X4 running, or be able to be made to detect it, and that would trigger the desired core affinity behaviour.Dipluz wrote: ↑Thu, 5. Oct 23, 10:19Even with all my mods in late game with thousands of ships, I have literally 0 lag or stutter and that is also with my game running on Ultra graphics on 1440p@144hz.
I have read online its AMD that makes these CPU affinity drivers for each game.
Could Egosoft contact AMD to ask if they can add a default CPU affinity for X4? so that we do not have to do this task manually or figure out some way to add the CPU affinity through registry or a shortcut ourselves?
This issue is one of the reasons I would recommend gamers get the R7 7800X3D over the technically better R9 X3D chips. The 7800X3D just has 8 high cache cores so there is no reason to play around with core affinity and should be significantly cheaper. Of course there are still benefits to the R9 X3D variants for some non-gaming workloads that can benefit from the extra cores or higher frequency.
The core to core latency is unlikely the main issue. I think the issue is that the high cache cores run typical X4 workloads much, much, faster than the high clock low cache cores. The high clock low cache cores end up holding X4 back while it waits for them to finish executing tasks. On top of that the high clock low cache cores will generate significant heat and use significant power which could even reduce the performance of the high cache cores.Dipluz wrote: ↑Thu, 5. Oct 23, 10:19If you can't do this Id suggest making a pinned AMD Ryzen 9 7950x/7950X3D guide on the Egosoft forum and Steam discussions, as ive read the CPU latency between CCD0 and CCD1 is also high and can cause lag/stutter, since the latency between Core 0 and Core 34 is a whooping 88ns. Though what I have not tested yet, which I will do after work today is test and measure FPS on Core 0-15 and Core 16-31, and compare the results and user experience.