Strong05

No good guide on VRAM requirements for VR, but most people are having good luck with 8GB cards with index/Rift S/Odyssey. I ran my Odyssey just fine with a 1070.

You can literally go into task manager and disable all but 2 cores and see no degradation in DCS FPS/performance. Kill it down to 1 core and the sound stops working properly. My understanding that the appearance of DCS using more then 2 cores is a windows thing, not a DCS change.

Currently you are correct that DCS is very clock sensitive. However what you are not considering is how many instructions per clock cycle (IPC) that a CPU can do. This is an important factor and why many times a CPU can complete a task much faster at the same clock speed as an older cpu. The new Ryzen cpu's complete more IPC's then the current Intel CPU's. What I'd like to see is if it's enough to overcome their clock deficit (compared to intel) with DCS.

I have a 6700k and also looked at upgrading to a 7600k. Not a whole lot of improvement here, maybe 10% so I passed and went for the 1080ti (from a 1070). I think it was the right move. You won't see CPU bottlenecks the way windows 10 distributes the load across cores. Look at your GPU utilization and if it drops to below ~80% then you know it's a CPU bottleneck. I've seen my GPU utilization drop to 50% (frames at 30fps) or less when looking at a crowded airfield, and as soon as I look at the sky the GPU utilization jumps up to 99% (frames jump up to 70 fps).

I have the Volairsim and would not recommend. Ergonomics are not good, and way to much flex where the wheel mounts without some serious modding.

Every headset will require some kind of software. The WMR headsets require the most right now to run DCS (however I wouldn't exclude them because of this). They all have pros and cons. You'll just have to pick what fits your use case the best.

Depends on your computer but I have a very similar setup to yours and have found that cockpit shadows have very little impact on fps, the same with flat terrain shadows. I've also found that depending on the mission, DCS can be either GPU or CPU bottle necked. Most MP servers are CPU bottle necked while simpler missions will be GPU bottle necked. The easiest way to tell is to watch your GPU utilization (if it's not >90% you are most likely CPU bottle necked). If you are CPU bottle necked GPU utilization (at least for me) dropped to about 50% or less, and the FPS tanked to 30 or less.

I may have stumbled upon a bug/fix. Got fed up with low fps and started rolling through all the settings one at a time in the instant action mission for the TF-51 (per Wags instructions). Nothing made much of a difference, maybe a frame or 2 with any one setting. Then I said what the heck let's try the VR pre-setting button. BAM! 75fps (45-48fps before). Proceeded to incrementally set all setting back up to what they were before and it settled in around 55-60fps. It does seem to bounce around a lot more but it is absolutely a 10fps gain or more from pushing the VR pre-set button then turning everything back up. options = { ["VR"] = { ["box_mouse_cursor"] = true, ["custom_IPD"] = "69", ["custom_IPD_enable"] = true, ["enable"] = true, ["hand_controllers"] = true, ["pixel_density"] = 1, ["prefer_built_in_audio"] = true, ["use_mouse"] = true, }, }, ["format"] = 1, ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 0, ["MSAA"] = 0, ["SSAA"] = 0, ["SSAO"] = 0, ["anisotropy"] = 3, ["aspect"] = 1.7777777777778, ["chimneySmokeDensity"] = 0, ["civTraffic"] = "", ["clouds"] = 1, ["clutterMaxDistance"] = 0, ["cockpitGI"] = 0, ["effects"] = 3, ["flatTerrainShadows"] = 1, ["forestDistanceFactor"] = 0.5, ["fullScreen"] = false, ["heatBlr"] = 0, ["height"] = 2160, ["lights"] = 2, ["messagesFontScale"] = 1, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 2, ["preloadRadius"] = 100800, ["rainDroplets"] = true, ["scaleGui"] = false, ["shadowTree"] = false, ["shadows"] = 4, ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["treesVisibility"] = 5000, ["useDeferredShading"] = 1, ["visibRange"] = "High", ["water"] = 2, ["width"] = 3840,

I have found the steam super sampling feature to be very easy to set and use. Vive and Index will also only have one layer of middleware. Only WMR headets are stuck with 2 sets of software (WMR and steam). That being said, it seems to work well enough.

DCS still requires the oculus software to be installed. Pretty sure DCS doesn't natively support any HMD, all of them require some type of middleware to work (steam, WMR, or oculus software).

Steam also forces updates. However, pending your steam setting for updates, it won't do it mid game. Not sure if there is a roll back capability.

I've got very similar hardware and get between 35-45 FPS on avg with the Odyssey. Haven't played with the vive in a while but I would expect even better fps. Very playable with what you have, I don't think people are getting a whole lot more fps with even the latest and greatest hardware.

80 fps? What are your graphics settings for the game? I have a very similar hardware setup (except CPU), just curious if the CPU is holding me back by 30 fps. Thanks, Sorta

Turn on labels. Until we get higher FPS (to get rid of the ghosting) that's about the only thing that can be done. VR zoom can also help a little but it's pretty limited. The labels LUA file can be edited to only show within a certain range and to only resolve IFF at a certain range as well I believe. So it can be made to work somewhat realistically.

I thought the only difference between the i8 and i9 was a soldered lid? If that's the case the only thing you picked up was additional cores and higher OC headway. DCS is still hugely clock dependent so OC the heck out of that thing. Are you talking 20% overall CPU usage or are you looking at each core?

You need to download the WMR software on steam for it work.

It definitely sounds like a radial and not a lawnmower. It could still use some tweaking, and as always the start up effects/sounds aren't nearly as good as another sim.

Had a similar problem with my VKB gunfighter and turned out to be a loose wire.

Openbeta update reports fixing a memory leak. Will be interesting to see if that has an impact on memory usage.

Apparently in some countries yes, it is a crime to use the swastika.

This may be obvious but, have you cleaned your GPU cooler? Most of the time it doesn't make much difference but might be worth a shot.

I've got a 1080ti with 11gb of VRAM and just upgraded to 32GB of RAM. Task Manager showed over 20-22GB of ram usage on MP servers. I'm not sure if it's actually using all of that or if it's just allocating it for future use. I can't say I noticed any quantifiable difference going from 16gb to 32gb either, but I also haven't had much time with it nor have I made any effort to really compare before and after performance.

Wonder if the Radial is heavier... that might help with boom and zoom tactics.

How well will it do against P-51, Spitfire, or the Thunderbolt?

There is definitely a difference when you move the IPD slider. Although it's not what you think, it just helps your pupils line up with the sweet spot better.