Headwarp

No flickering for me. I was just flying in another sim a bit ago @60hz and 60fps and it's amazing how much easier it is to identify the aircraft I'm looking at vs my experience with reprojection. Admittedly, before disabling reprojection, dropping to even 55 fps would kick on 30fps reprojection and that was no fun.. but once I disabled it.. dropping to 50-55fps is no big deal. YMMV i guess but getting a consistent 60fps and no reprojection artifacts feels is pretty awesome to me. Then again, I'm able to get away with msaa 2x due to the lower resolution with my headset. When I bump SS% up to beyond reverb resolution I doubt I could still maintain at or around 60fps with msaa on. Have you updated to the win10 2004 build? Earlier posts in this thread point out it's supposed to have made some differences with the 60hz setting in WMR. At any rate.. I'm ecstatic to be flying in VR without reprojection.

Frankly, I'm with the idea of some control assignments for 20-30 degrees or so. If I had to back up a vehicle looking over my shoulder with blinders on like I'm wearing a VR headset I'd never be able to do it. Yet.. without restrictions on my vision, I can see behind me looking over my shoulder just fine. Eyeballs pivot, ya know? It's why something like TrackIR works.. you can move your eyeballs right or left to keep looking at your screen as you turn your head.

just now getting around to testing out DCS with WMR set to 60hz in my odyssey. disabled motion reprojection...and wow how nice is it not to have all the artifiacts caused by motion reprojection? lol. Undecided on whether I prefer the occasional hiccup with msaa 2x and 160% SS, or the shimmering with 200% SS and no msaa, with less dips to 50fps.. but, afaic 60hz VR is the way to go until hardware or a graphics API change gets us towards 90FPS in VR.

You have one of the highest resolution headsets on the market.. vive pro, index, oculus, and pretty much every other WMR headset out there would have to increase either PD or supersampling to even get close to rendering the amount of pixels per eye you are. Adjusting either PD or SS = adjusting the rendering resolution, and given headsets come at different resolutions the effect it has on your system is a YMMV kind of scenario. To the OP - With liquid cooling (A decent AIO unit will do) you can probably get that 8600k to 4.7-4.8Ghz without much of a struggle.. but read a good guide on how to do so with your motherboard, especially when it comes to vcore. You don't want to overdo the voltage. But imo, OC that CPU, get a beefier gpu, get another 16GB of the same speed/brand/model of ram.. you'll probably find settings that allow you to maintain a consistent 45 fps in VR.. also probably worth setting PD to 1.0 and bumping the supersampling in SteamVR instead. That 8600K should last you at least another few years if you can get a stable OC out of it. If you're computer illiterate and scared of attempting to OC, 9th and 10th gen intel cpu's boost to around 4.7-5.1 GHZ, but imo you want a beefier GPU for VR, and most folks I know flying DCS have stepped up to 32GB of ram. Just fyi, @ 5ghz and 150-160% SS with my Odyssey, which has a slightly higher resolution than your headset, I can find myself cpu limited with my 2080Ti. Bumping the resolution to a point where I'm gpu limited will find me below the 45fps minumum at times. My previous GPU was a 980Ti, which was on par with a 1070, and it simply wasn't enough for VR in DCS without some serious sacrifices to image quality.. but me personally I can't live without 2x msaa in this game, and I also like being able to read my guages, which with my headset requires some supersampling. If you're going to build a new rig for dcs.. go big imo. But if you can wrap your head around overclocking, a new gpu and more ram might be all you need.

Around 10 minutes 40 seconds in this video, it's the last thing Wags covers in the demo/tutorial. Worth a watch

Well that's going to be freaking sick. @ Cato, have you set it up for a program in the stats page? Wags was showing off the ability to see friendly d-link targets in his HMCS video.

Can the HMCS track enemy air targets via datalink?

@$10 a day one buy was a given. $19.99 at the end of the month isn't unreasonable either imo.. site must be bogged down lol.. taking forever to process my payment.

ERMERGERD *waves ten dorrah birl*

I get you, just thought it might be worth checking out. ;) The nVidia default fan curves favor lower decibel operation as opposed to performance.

I would suggest reading up on overclocking on forums dedicated to the practice rather than the DCS forums. Seems there is much you're lacking about how turbo boost functions and the dos and don'ts of adjusting vcore voltage. 8700K is stock 3.7Ghz, it boosts to 4.3Ghz when multiple cores are in use, and boosts 1 or 2 cores to 4.7Ghz when applications aren't using more than that out of the box. That being said, even single threaded apps like DCS can cause it to boost to 4.3Ghz instead of opting for the 1 or 2 cores at 4.7Ghz. 8700K's are pretty much guaranteed to find a stable OC up to 4.9ghz on all cores with 1.3vcore or less. But toying with voltage takes some knowledge, you never want to go too high, and you really want to find a comfy spot around 85C max via hours of stress testing under full load, which also should let oyu know if you're system is stable. Like..no hangs, and no crashes during stress testing. 90C isn't going to kill your cpu, neither will 95C, but it's high enough that I'd want to back off the voltage and/or cpu frequency. You want to make sure you have sufficient cooling, I have a dual fan radiator AIO liquid cooling unit that keeps my cpu cool enough to feel comfortable. I'm @ 4.9Ghz currently at around 1.275vcore.. but YMMV, one person's settings and achievable clock speeds aren't going to work for everyone else. Pushing 5Ghz requires a hefty vcore bump on my machine and causes quite a bit of heat, so I backed it down to 4.9Ghz, which an 8700k SHOULD achieve comfortably. Others got a lot more lucky with the silicon lottery. You also want to disable the avx offset when overclocking to maintain your clock frequency. It's honestly pretty easy to OC the 8700k and find a stable 4.9Ghz.. but there are better places to research how to do so, and finding the lowest voltage to accomplish it is a task of reducing vcore in increments of .005 to .015. And it's best if your motherboard has a bios reset button in case you do something silly and need to reset to defaults to even get your board to post. I mean no offense to the DCS community but you're going to get a lot of varied responses, some from people who have a better understanding than others, and some who don't.

While I understand the sarcasm and appreciate that you seem to get it.. have you tried to set some custom fan curves for your GPU? :) IDK about Palit, but my 2080Ti tends to stay just around 61C @ 99% usage. Though the sound of it sometimes scares me and causes me to crank my neck checking 6 in WW2 birds as the fans spin up. There's been a time or two where a driver update has caused me to need to set up my fan curves again and the gpu getting above 80C had a pretty big effect on performance. Anyway, just some food for thought. My fan curves are way aggressive. I like to get the air flowing well before it's started getting towards that 60C temp range.

If you're making your decision based on this user's experience alone, reading about CPU and GPU bottlenecks, the differences in DX11 vs newer API's like Vulkan and DX12, and the effect resolution has on each of these is probably much more valuable than a new piece of hardware can be and will help you make such decisions in the future. Here's an example of how such information can help. If you're hitting 99% on a single CPU core while flying in DCS, which is currently a DX11 title, then you are cpu limited and a faster GPU won't help, where a CPU able to achieve faster clock speeds will. It takes a higher resolution to become GPU limited so you can tell what your GPU is actually capable of. (you have to look at each individual core.. using a quad core for example, one core maxed out is only 25% total cpu usage) If instead you are consistantly using 99% gpu, and none of your cpu cores are anywhere near being maxed out, a faster gpu will likely increase performance. It's going to be a different story when ED is on par with the Vulkan API.. but currently, treat DCSW as a program that relies on single threaded performance up to the highest obtainable cpu clock speeds until you reach a certain resolution. Trying to judge what experience you'll get from someone using a completely different display and resolution, as well as being frame limited by VR specific features intended to reduce the risk of motion sickness isn't going to offer you much to go on. Understanding how hardware bottlenecks work, however, might keep someone from spending money on something that won't offer much of an improvement to their current setup.

In many Dx11 titles, less than 4k resolution was still showing a cpu bottleneck @5ghz with a 1080Ti (per other peoples benchmarks, I went from a 980Ti to a 2080Ti, and had similar results with the 2080Ti). @3440x1440 i could see a single core of my 8700k hitting 99% while still getting 98-99% gpu utilization.. pretty much riding right on the edge of a cpu bottleneck in DCSW. With my Odyssey and 160% SS, I often get the light blue indicator showing motion reprojection being engaged due to cpu limitations, yet at the same time show the dark blue indicator indicating gpu limitations with my 2080Ti (WMR specific feature). Same riding right on the edges of bottlenecks, but lower FPS overall in VR as one would expect. If I bump up to say 200% SS, which is like 2024x2520 per eye with my odyssey, I get just the dark blue indicator showing being gpu limited (what we strive for) but, ioften I'll see the red indicator meaning that the system can't even maintain 45fps. So, without going to a higher resolution, or getting a good deal above 5ghz on a single core of your cpu, a gpu with more power than a 1080Ti, or even 2080Ti isn't going to show an improvement. This is a big reason we're looking forward to Vulkan. I wouldn't recommend holding your breath waiting for vulkan.. a complete graphics API rewrite, especially one that changes the single threaded nature of DCS on DX11 to a multi-threaded process is a hell of a task. In the meantime, for dx11 and lower titles, especially sims, increased resolution is about the only way to measure performance between nvidia gpus from pascal to now.. other than increasing cpu clock frequencies, which 10th gen k series I7 come stock with a 5.1Ghz Turbo boost.. intel's kind of up against a wall pressing the limits of their current architecture. Currently I run at 1808x2252 per eye and still hit cpu limitations with my 2080Ti @4.9Ghz, and I wasn't seeing a real difference at 5Ghz. Thing being though, my bet is the 30 series will have an easier time at maintaining the minimum 45fps for reprojection at higher resolutions. For index users, at higher resolutions you might be able to maintain that 60fps minimum for 120hz refresh rates. But testing with reprojection on isn't going to net results that tell you much of anything. Bump your SS% up to Reverb G2 resolution or more.. and do all testing with reprojection off imo. Otherwise upgrading to a 3080 from a 1080Ti isn't really going to be beneficial with current hardware and DCS on DX11. In the end, your still basically looking for the highest resolution you can get while maintaining the minimum framerate that still allows reprojection to function.. or sacrificing graphics quality while attempting to hit 90fps. The results don't really surprise me considering the nature of the testing, and the nature of DX11 which doesn't allow multi-threaded processing anywhere near the capability of Vulkan or DX12. I will note that I prefer to run with msaa 2x in DCS, as I just can't stand the shimmers without it.

You should disable motion reprojection to see what framerates you're actually capable of getting or you're just going to see 45fps anytime you dip below 80-90 fps. With reprojection, gpu usage will also be lower than without as the gpu is being frame limited. I would do that both at the resolution you currently play at, as well as increasing the resolution to a point where you are mostly gpu limited just to get a general idea of what the gpu is capable of. Also worth running DDU if you haven't, as well as making sure power settings are set correctly in NV Control panel.. as well as boosting the fans via afterburner or something since Nivida cards run better with lower temps. It might be worth seeing what happens if you disable the meltdown/spectre patches as well, as they've reduced the performance of at least 8th gen and older intel CPUs. if you're up for the risk. At some point, newer cpus will have to break 5.5ghz.. lol.. isn't hardware fun? There's simply more to benchmarking than just throwing a new piece of kit into a system and running software. I mean, it might still end up a disappointment but tests without covering the bases don't really offer much to go on.

the DDCS server is the only server where I've personally flown the Ka-50 or the huey much at all. Mostly the Huey for slinging crates and deploying units. Though I did once get to fly out with several Ka-50's for some ground attack. Most of the MP action is about the fixed wings tho.

I'd say merge any separate threads that point to the same issue, and while that's a lot of work, once it's been done checking the forms once a day or every other day should be more manageable. The vocal portion of the playerbase is always going to manage creating a mess.. and like a home.. it's less work to clean a little every day than to clean after months of not touching anything.

YMMV but I don't like curves on my collective/throttle axes. Might be because the TMWH throttle has a longer throw than most setups I've used but I also just find more consistency in managing the collective with a linear axis as opposed to a different feel depending on whether my throttle was centered or towards the extremities. Came to the same conclusion with fixed wings, especially when attempting close formation or AAR. Just feels like I know more what to expect out of a given range of motion. Where when not using FFB, curves on a stick and rudder pedals are generally helpful. Others may feel differently, but if you can manage a light touch.. worth checking into imo. like I said ymmv.. nothing wrong with preferring curves if you prefer them.

While I don't recommend the SA342 Gazelle module until Polychop demonstrates what they can do with the Kiowa, and afterwards fix the little Gaz.. here's a video of me demonstrating some ground control in the Gazelle, strafing, circling, and coming to a soft controlled landing. My friend said he was struggling with controlling the bird.. so I made this video to demonstrate how little I'm actually moving the cyclic.. pay attention to the control surface indicator in the bottom left corner. Pardon my Aussie buddy dropping the F-bomb, as apparently I was on discord when I made this. YMMV in other DCS helicopters.. but.. less is more when it comes to hovering and ground control. Flying the Gaz I literally just lightly tap the stick with a finger in a lot of cases, albeit frequently.

Yeah low speed controlled taxiing. Hovering and taxiing require exerting a combination of Rudder, cyclic, and collective. It's a bit of a balancing act so to speak. Controlling a chopper between 0-15 knots close to the ground is a developed and necessary skill. Ground control is an essential part of the piloting experience. No instructor IRL would let you take a helo up solo without first showing confidence in this ability. Trim for hover (slightly aft and left cyclic, apply a bit of left rudder) Having rudder pedals helps a lot in this regard too.. even if it's just to extend the left leg a hair. I have loved my MFG Crosswinds since day one, and to this day I appreciate the smoothness of the cam design compared to plastic pedals I've used. If you're attempting this with the twist function of your stick.. do make sure you add plenty of curve.. even then it will likely feel a bit awkward. It really teaches you just how little you actually have to move the controls to achieve a shift in direction. Doing so with a light spring like say on my Logitech Extreme 3d pro is probably a lot easier than with my TM Warthog...msffb2 allows for a lighter touch than both, and when you engage the trim button, there's no centering force what so ever until you disengage the button.. really allowing for fine control. Without FFB however, you're able to add curves or reduce y saturation on the cyclic axes so it won't be quite as touchy.. I don't recommend curves on the collective personally as I prefer the 1:1 ratio for every part of my throttle's range. Helps me to know what to expect when I move my throttle at any position. And most adjustments are very slight. In other words, just got to give the cyclic a little tappy tap. Minimal adjustments.

There's also a search function in the control configuration menus.

I mean.. my main guesses would be you only have one engine started.. or the speedbrake is open, or you don't have the option checked in the "Special" menu in the options menu that disables the need to enable the finger lifts to enable afterburners. Or perhaps you've adjusted the y saturation on your throttle axes? But yeah maybe you should create a trackfile or a youtube video showing us the instrument panels or exterior views. Perhaps enable the control surface indicator as well.

Very slight adjustments to the "collective", keeping in mind that your x56 throttle has a fraction of the range of an actual collective due to the length of the collective. And with the huey, adjusting the collective also changes the orientation of the helicopter, unlike say the Ka-50 which has a lot of auto pilot function. Every aspect of the collective/cyclic requires being able to make tiny tiny adjustments, moving one generally requires movement from the other.. and in many cases it takes just the slightest nudge. Learning ground control (taxiing around the runway) can go a long way imo.

Ok I think I want one of those Koolertron keypads to turn into a hybrid F-16 and F-18 UFC panel. I have a Logitech G-13 I keep next to my throttle that I have the top right most key programmed to "G" for the gear lever. In the Ka-50 I also have the Targeting mode panel as g18, g19, g21, and g22 and the thumbstick for cycling the cannon modes (fixed/moving etc) and one of the buttons next to the thumbstick as the targeting mode reset. I know we aren't talking the Ka-50 here, but the g-13 offers quite a bit of functionality and you can make a profile for any aircraft you fly in DCS, and is easy to feel for button locations. Unforunately, Logitech discontinued the thing quite some time ago and i don't know what I'd do really in terms of a replacement, as you can only find them used and priced rather high. Razer has a couple of options but I despise the synapse software. I've considered buying the AULA Excaliber for the invetible day my G13 poops the bed. Anyway, food for thought for more options you might be able to navigate without looking at it.

This can be helped by learning to hover. Honestly what helped me the most to develop a light touch was learning to taxi the Huey around a runway.. but I was also aided by my MSFFB2 in that regard.. as the day I got it transitioning to a hover got so much easier.