hhhttt

It’s very easy to enable label by modify the zip file of each mission. just open miz file as zip file, open the text file in it, find label config, change it. Save and update the zip file

Based on my testing, in cpu limited mission, 7950x3d on 3d vcache core 20% faster than on non x3d core (aka 7950x) it just harder to trigger cpu limited situation now due to multi threading in VR my cpu time reduce from 8ms to 6ms (Apache Mariana ) but that is not needed because gpu frametime is 10ms in my setting. But thinking in the next 5 years. Planes would became more complex but you can always drop graphic setting but you can’t make cpu faster

Share some of my finding with DCS MT, 7950x3d,4090 I raise the max frame limit to 300 fps, select 1080p resolution (to remove gpu bottle neck), 2d, mostly high setting, 2xMSAA Measure F-16 Ramp start, Caucasus Using process lasso, force DCS MT on either cache or high freq cores. 1. cache cores, average fps 266 2. high freq cores, average fps 220 So x3d cache does help maybe 20% when CPU bound. Secondly, core parking does work with DCS MT If I disable process lasso, most of the process are in cache cores, however, DCS seems to span too many thread, and some of them are wake up parked high freq cores, and was put there. However, average fps are still around 266, 1% low are also similar. at 126 fps, it is possible that those thread that on high freq cores are not in heavy communication with main thread, so moving them in to high freq core won't incur cross ccd penalty that much. Conclusion: 1. Not worth to use process lasso or tinker around, since majority of the usage are still on cache cores, just play the game normally. 2. x3d cache does help when GPU is not bottle neck.

May be DCS is hard coded with 8 core in mind because in MT FAQ it keep refering P core and E core. As we know 13900k have 8 P core, but 7900x3d only have 6 core on vcacheccd. If DCS is coded incorrectly to always use up to 8 core, rather than aware of 7900x3d's 6+6 situation, it may mess things up the speed as cross ccd is somewhat slow.

MT FAQ are talk about E core and P cores, maybe DCS MT is spreading so many thread that is force non 3D core to start? Have anyone test with disable frequency core? The 60fps may be a speed limit when threads from 2 ccd are talking with each other. In a way, you can think x3d expand cache from 32MB to 96MB, so it would improve a game if its core caluclation/simulation model can not fit in 32mb cache. MSFS definitely see gain there. Maybe with MT they optmized/removed some calculation that it spread out more, so it can fit regular 32mb cache, so x3d improvement is gone now if you are using simple plane. I wonder if F15E or Apache or F14 can gain better from x3d.

save the follows as .ps file and run it to batch rename config files. Replace the uuid of course cd "D:\MyDocs\SavedGame\DCS\Config\Input" gci -recurse -path. -File "*{2E011970-248F-11ec-800C-444553540000}.diff.lua" |foreach { copy $_.fullname "$($_.Directory)\*{BA3F7B20-3524-11ec-8003-444553540000}.diff.lua" ; }

If you remove it from forced_option, your own setting will take effect

You can just open the mission file in winrar DCS World\Mods\campaigns\FA-18C Raven One Dominant Fury\RODF M01.miz And open a file called "mission" At end of the file, you'll see text like ["forcedOptions"] = { ["labels"] = 4, }, -- end of ["forcedOptions"] ["start_time"] = 32400, } -- end of mission Just remove the ["labels"]=4 line, close the file. Winrar will ask if you need update the file, click yes. You have to do this for every missions though.