Cal.Iber

I'm holding out for the release of the modern combat grip so I can ditch the warthog. Here's to hoping it lasts another month or two ... I'm currently using the "pinkie lever" as weapons release. Autopilot sorta works if I mash it enough times. Related anecdote: When I initially added the pinkie lever as weapons release, I didn't clear weapons release in the keybindings and for a short time had two weapons release buttons. The buttons still occasionally function and often seemingly press themselves. After a couple missiles flew off the rails on their own, I got wise and went and cleared the weapons release button mapping.

I ran through several KA-50 Normandy Free-Flight missions starting with the VR Presets as baseline settings and a Pixel Density of 1.5. VR Preset: 45 FPS (Deferred Shading On, HDR off, Medium Shadows, Flat Canopy Shadows, etc.) Change: Anisotropic Filtering 16, Global Illumination On, Dirt+Smoke Effects: 45 FPS MSAA x4 and Pixel Density of 1.5: 28 FPS MSAA x4 and Pixel Density of 1.0: 45 FPS VR Preset + ASW Manually Disabled: 45 FPS I'm pretty sure the 45 FPS ceiling is due to ASW being enable. Even when I forced it off in the Oculus Debug Tool, it started off disabled (in the DCS menus) and then (magically) became enabled after loading the mission. The only time I struggled constantly for frames was when I was using MSAA and a pixel density > 1.0. On a side note, flame/smoke effects also caused temporary dips in FPS (~35 FPS) from crashing (haven't been in the KA-50 in a while) or the couple things I managed to blow up while running around Normandy like a mad-man. I know from some previous discussions you're making use of the Oculus Tray Tool. It might be worth disabling it temporarily, verifying that Anti-Aliasing is disabled and try again.

I played 3 missions (Nevada only) and crashed after exiting the first. The second and third were fine. My specs are pretty close to your sig. I'll fire up one of the Normandy test missions you mentioned and report back.

Very possible. The release notes mentioned that they updated the graphics presets, so the first thing I did was click the VR preset which sets deferred lighting on among other things. I didn't play with any other settings other than lowering gamma to 1.6 and setting VR pixel density to 1.5.

After updating to DCS 2.1.1 Update 2 and using the new VR presets and adjusting the Gamma slider to 1.6, I decided to take the A-10C for a spin in the weapons practice and CAS missions. Wow! What a difference! Prior to gamma the HUD was almost completely washed out. Its much more readable now except against the bright sky (which may be realistic) and the gauges seem easier to read at a glance. The biggest difference that hit me was in targeting. Part of it was simply being able to see the MFDs clearly, but subjectively both Mavericks and the Litening pod seem nicer/easier to pick out target contrast. I think this change will really breathe some new life into VR pilots. Three :thumbup: up!

Its more like the buttons themselves have broken / physically degenerated in some way. Whereas there used to be a solid detent / tactile response for clicking the buttons, now there is only a mushy depressed response with almost no spring action. Control manager reports the buttons as being pressed almost constantly. Unfortunately this appears to be a common quality problem with the TM Warthog for these particular buttons. There are numerous other threads of people reporting that TM support required them to send videos showing the buttons lighting constantly and eventually needing to RMA the device to have it fixed (which I don't think is an option available to me anymore due to age) and/or purchasing replacement buttons. Unfortunately due to the PCB layout, apparently replacing the buttons isn't trivial. When it was one or two butons on the throttle I was looking into desoldering / replacing those buttons. After the weapon release on the stick died, I started looking to VKB / Virpil's (hopefully near-future) offerings to replace it.

I got my Warthog just over two years ago and although the gimbal has been _OK_, more than half of the (push) buttons are gone. I've lost weapon release on the stick, and autopilot and l/g warning on the throttle.

Usually a good place to start is by sitting in a neutral (face forward) way and hitting "5" on the NumPad. That should recenter the headset and often helps if you're too high/low/forward/etc. After that, play with the seat settings and other controls as mentioned.

I have both although full disclosure, I've never tried the Vive in DCS. The Rift is a lot more comfortable to wear for extended periods of time and for a seated experience is quite pleasant to use. The progressive nature of the lenses is a bit annoying, and you have to experiment with the strap adjustment to get it centered over your eyes or things will be (more) blurry. Outside of sitting experiences though, the Vive has much more lasting appeal (and far better room-scale support / tracking). The first-gen strap is not very good and doesn't support the weight of the headset very well. I often find it feeling very front-heavy and pressing down on my nose. They started selling a "Deluxe Audio Strap" that comes with built-in headphones ala the Oculus which is supposed to support the weight distribution on your head far better, although Amazon has been out-of-stock since release. Unfortunately this also adds to the cost. For room-scale VR games the Vive has several advantages: Tracking is very high quality and having wireless sensors makes room-scale placement a lot easier without having to resort to several USB3 extensions. TL;DR - If flight sims are primarily your thing, I'd go with Oculus. If you're intrigued by room-scale VR then the Vive deserves some serious consideration.

First thing to check is to make sure that Pixel Density is set to 1.0 in DCS, otherwise (my understanding is) that DCS will override the settings in OTT. The Oculus Debug Tool (C:\Program Files\Oculus\Support\oculus-diagnostics) can give you info about Pixel Density, ASW, etc. I tried using the OTT and eventually gave up on it as I wasn't seeing any real benefit inside DCS for it. I might try it again depending on how things change in the next patch.

Thanks :thumbup: I guess I meant to say that getting new products manufactured always ends up taking longer than anyone expects/hopes.

Good luck Zeus! Definitely excited for the Harrier and greatly appreciate the development progress and updates!

I can't claim to be an expert, but after backing several Kickstarter projects manufactured in China (one in 2013 that is just now getting to shipping) I'm not all that surprised. Looking forward to the T-50.