FoxTwo

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.

For SAR/ASW missions. A flyable SH-3 would be nice.

Euro. Which is around $2300 USD at the current exchange.

Well barrier to entry is $1200 for someone with an 8kx already. That's a lot more tolerable than $2300 for the varjo.

It's really ruining the effect in VR. Like they look amazing and then you look into the distance and suddenly the clouds are being rendered by an Atari 2600.

Uh huh. Even if it looks "somewhat" better than represented in the video it doesn't look $1700 better to me.

Based on that through the lens video there, I cannot imagine paying upwards of $2300 USD for a headset that seems visually similar to my Reverb G2. It really doesn't seem to bring anything new to the table for DCS.