FoxTwo

Are you using an autoexec.cfg file? Does it have options.graphics.stereo_mode_use_shared_parser = true in it?

They don't need a hole all the way through, they have a threaded hole on the opposite side so you can screw them together. 450-500g should be enough with a little bit of friction on the dry clutch.

Not everyone uses the virpil desk mounts.

I'd be more excited about the CM3 if they hadn't abandoned the CM2s mount. Would have been a day one purchase, now it's a wait for someone to come up with a top mount adapter for 40 series t slot.

I get the ask but wave height is entirely determined by wind, so if there's a "sea" preset then surface wind conditions would go along with it. Conversely, you can set wind speed/direction at the surface to change water conditions.

You going to have ED add the ipad and emulate the ios software they're using to control them too? Cause they're not exactly integrated into the Mig-29s avionics.

Just a head's up, this guy is selling a bracket for a counterweight (not included) on etsy. https://www.etsy.com/LaserWing/listing/1271733962/counterweight-bracket-for-virpil

If you drop the numbers into the detent calculator you can get a curve for any module and for any throttle hardware. In my case my detent kicks in at 28. The Mirage F1 hits max MIL power at 43 and goes into AB at 42, so my curve looks like this:

This is an early 1970s HUD you're lucky it is as readable as it is. To be honest it's probably very accurate and technological limitations (the resolution of your VR headset) are the problem, not the module. I wouldn't expect it to change. You should have tried reading the F-14's analog gauges with a samsung odyssey+ when it came out.

https://mbucchia.github.io/OpenXR-Toolkit/upscaling.html I have no explanation for a reduction in framerate other than 20% (80) is less than 25% (150).

Nope, just change the file name of the config files to the new device udid. You can use something like bulk rename utility to just find the old ID and replace it with the new one.

https://forum.dcs.world/topic/282694-bug-runway-and-terrain-lighting-anomolies-with-pimax-8kx-in-large-fov/ Oh hey my bug report is about to have an anniversary. I'll have to put something on my calendar.

I took the liberty of running them through audacity with a filter eq and compressor. It's not perfect but it's less jarring I think. Up to you to use them. comm FX.zip

Some of Flip's radio chatter from mission 2 doesn't have the radio compression effect applied to it. Raven 405 005 taxi 7s Raven 405 005A short 5s Raven 405 006 tower 6s etc. I didn't go through all off the files but it was noticeable during the mission.

I just completed the mission last night, with the right radio on channel 1 and GRCV enabled I was able to listen to guard without issues. Had to switch radio 1 to G to transmit though as expected.

The wiggle issues can be solved with the TM stick if you 3d print a spacer. You can save yourself $600. Not saying the RS stick is bad but it's probably not worth it if you have a TM already. https://www.thingiverse.com/thing:4575333

This is an old. Old. OLD. Request. And probably at least half dependent on vulkan. So don't expect much if any traction until they change the entire rendering engine.

I don't even bother editing the lua anymore, I just use quaggles input command injector and munkwolf's community keybinds, which so far seem to have all the inputs required to map pretty much anything in any module. But if you don't want to bother, you can just use the relevant part of the keybinds from munkwolf: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/FA-18C/Input/FA-18C/joystick/default.lua {cockpit_device_id = devices.HMD_INTERFACE, pressed = hmd_commands.BrtKnob_ITER, value_pressed = -0.5, name = _('HMD OFF/BRT Knob - CCW/Decrease (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.HMD_INTERFACE, pressed = hmd_commands.BrtKnob_ITER, value_pressed = 0.5, name = _('HMD OFF/BRT Knob - CW/Increase (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.HMD_INTERFACE, pressed = hmd_commands.BrtKnob_ITER, value_pressed = -2, name = _('HMD OFF/BRT Knob - CCW/Decrease (Fast)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.HMD_INTERFACE, pressed = hmd_commands.BrtKnob_ITER, value_pressed = 2, name = _('HMD OFF/BRT Knob - CW/Increase (Fast)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.HMD_INTERFACE, down = hmd_commands.BrtKnob_AXIS, up = hmd_commands.BrtKnob_AXIS, value_down = -1, value_up = 1, name = _('HMD OFF/BRT Knob - 0% else 100% (2-way Switch)'), category = {_('Special For Joystick'), _('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.HMD_INTERFACE, down = hmd_commands.BrtKnob_AXIS, up = hmd_commands.BrtKnob_AXIS, value_down = 1, value_up = -1, name = _('HMD OFF/BRT Knob - 100% else 0% (2-way Switch)'), category = {_('Special For Joystick'), _('Instrument Panel'), _('Custom')}},

Look into this https://github.com/Quaggles/dcs-input-command-injector and this https://github.com/Munkwolf/dcs-community-keybinds

I used Cable Matter's USB-C to displayport adapter with my 2080ti and Reverb G2 without issues. I've also plugged it into my Surface Pro 8 and it worked OK (albeit with poor performance due to the integrated graphics). Just to be sure, you are plugging it into usb-c port closest to the FRONT of your laptop correct? It seems that one is marked as DP.

Did you restart steam VR when you changed it? Running in "Normal" fixed it for me, but the aspect ratio doesn't change unless steamvr is stopped and restarted.

The aircraft remains functional, but pilot death results in what seems to be a normal flight where you cannot interact with the cockpit. There is no black screen and you are not kicked out of the aircraft. It's very confusing. This is inconsistent with pilot death behavior in every other module.

You don't need to run the software to use winwing hardware. It also doesn't seem to phone home apart from checking for updates. It doesn't really seem like winwing is a PLA front.

I've made that mistake as well, it's in the actual text briefing section.