MakAttack

I would agree that for most games the 7800x3d is ideal. I went with the 7950x3d because I typically run extra processes that I feel don't require the vcache performance gains so I wanted to see if I could task those to the frequency ccd. I'm not sure it really buys me much, other than more cores with cache available to the main game process. Since I enjoy VR, with DCS, I will often run VAICOM pro with voice attack. For FalconBMS, I use foxvox for audio recognition. I also have tacview for both dcs and falconbms, but I think DCS runs it as a module within the main process, but I'm not 100% sure. It just seems to me that running these extra processes in ccd1 while the game runs in ccd0 makes sense. I also see OBS in ccd1 when I am using that tool. For MSFS, I'm often running vr, voiceattack (for copilot like commands), beyondatc (with traffic injection) and find that those run well in ccd1.

I thought I would post on this thread, as I found myself buying parts for a new VR sim gaming computer, and took advantage of a sales tax free holiday coupled with a new MicroCenter credit card to get the most discounts I could on a 7950X3D based system using the MC bundle available at the time. This is the build: https://pcpartpicker.com/user/mak8tack/builds/#view=yCTJ7P where I pulled the 4090 from my previous system based on a i9/12900K CPU. I'm happy with it, but found the DCS multithreaded performance to be interesting. Using the latest Win11 23H2 (with the AMD branch prediction patches) coupled with the latest chipset drivers, XBox Gamebar, and UEFI BIOS, I find that with the multithreaded DCS app, it will default to using both CCDs (extra vcache CCD0 and higher frequency CCD1). If I were to use Win11 Task Manager to setup "Process Affinity" to keep DCS on cores 0-15, by disabling 16-31, I don't perceive much of a difference with the DCS built-in FPS counter. This is in VR (Windows Mixed Reality with a HP Reverb G2) Here are some screenshots I made with a OBS recording of DCS, AMD Ryzen Master (to easily show which cores are utilized) with no special CPU affinity config, and affinity preferring CCD0. In the screenshot with the CCD1 cores with the lower level of activity, I think that might have been OBS. Anyway, feel-wise, they both felt similar in performance in VR. Numbers-wise, they both hovered between 45-51 FPS on the DCS frame counter. I will note that with other similar sims I have tried: MSFS, and FalconBMS they tend to run in CCD0 based on the XBox Gamebar identifying them as games. DCS is also recognized by XBGB as a game, but I have to use the Task Manager process affinity config to make it run in CCD0. nullnull

I'm seeing this in VR, which is particularly noticeable especially when changing head positions while looking around. Seems worse looking out the side vs forward facing.