Dunska

Thanks! @deadlyfishes The download link for this v2.4.9f Mariana Island TTI in User Files actually downloads the South Atlantic TTI zip file.

Really enjoying these missions with a friend. Thanks so much for all the work!

We can only dream of this.... and keep nagging

Like you, I installed, selected DX11 and OpenXR for DCS MT. I then had to launch DCS in 2D mode to be able to use the ReShade menu for configuration. Once configured, I could then launch in VR and had ReShade working (just could not use the ReShade menu in VR). I could use a hotkey to enable/disable ReShade to see the difference in VR. For reference I am using a Pico 4 via Virtual Desktop using VDXR.

@bandit648 just updated the view distance file from Mustang's mod for 2.9.3: You can modify the graphics.lua to set the view distance you like for each setting.

This appears to still be a thing. Anyone been able to stop it creating the Scripts folder on C drive?

I have a centre-mounted F-16EX stick with an extension. I also have the grip slightly turned to the left so it fits nicely in my right hand, as in an F-15E / F-18C, etc. The issue I have is that the centre position of the stick sits slightly to the left on the roll axis as that side is heavier. I have the medium springs with soft centre cams, but it still calibrates and sits slightly left of centre in the roll axis. Is there any adjustment in the base to help centre the stick? I've tried calibrating and not moving it to the full stops on the left side, which sometimes works, but gives less motion on the left roll axis. Maybe I need to add some counterweight to the right side of the stick to compensate and balance it out. Anyone else had this issue or any ideas on how to solve it?

You could try Taz1004's Optimized Textures (which include lots of core textures and a number of cockpit textures such as the AH-64D and A-10C II). For the F-14 I use F-14 VR Ultimate Xperience (F14VUX). F-14 VR Ultimate Xperience (F14VUX) (digitalcombatsimulator.com)

I did this by accident after a zoom climb and negative G's flamed out the engines. I just put throttles to cut-off, hit the JFS (no change of bottle) and then finger lift to start the right engine and throttle to idle once RPM was 24%. I was able to throttle the right engine up while then starting the left engine the same way. Luckily I was at 35k feet, so plenty of time to do this. Got the engines going again and landed. Was quite fun and unexpected as I was not aware the F-15E engines flamed out like an F-14A

Thanks @swartbyron. I gave this a try in VR with ReShade 6.0 (now supports OpenXR - yay!). Looks great, but I did lose about 5-8 FPS in initial testing. More testing required.

ReShade 6.0 works for me in VR. Pico 4 using Virtual Desktop with VDXR. I installed ReShade 6.0, pointed it at the DCS.exe in \bin-mt and told it that DCS uses OpenXR. I could then launch DCS in 2D mode and configure the ReShade settings in the in-game dialog - ReShade was working in 2D as well. I then launched DCS in VR and ReShade was running. The ReShade dialogs and hotkeys don't work in VR (unless you are running SteamVR Desktop I think), but the shaders certainly do. It did cost some performance though... about 5 to 8 FPS (on RTX 4090). I used swartbyron's settings from this post and also added the VRToolkit shaders when installing ReShade. I did remove ColorMatrix though as it was a bit too bland for me. Need to play around with it some more, but the BloomingHDR shader is quite nice. Just need to get the performance hit down a bit.

Here's a complimentary mod from Taz1004 that can also help with perceived haze/visibility. I leave the shadows on, but set the opacity to 0.2 (line 101).

Working fine for me in 2.9 in MP.

Yes, I only get the log message when using the setting in autoexec.cfg. If I remove that setting, but still have hotplug disabled in the GUI, I don't get the dcs.log message.

It seems to only show in the DCS.log if it is disabled in autoexec.cfg (no_device_hotplug = true). If it is only disabled in the GUI, it does not show in the DCS.log. Not sure if there is a difference in how each method disabled hotplug though, so I do both

Works fine for me with v22 on current MT OB 2.9.1.48335. Win11 23H2 / 4090

Nice to have the GUI, but would be better if it was more granular. Many VR users needs 36 or 72 FPS limits which were fine in the autoexec.cfg. The GUI only works in 5 FPS increments though. You can modify it in the options.lua, but as soon as you open the Options GUI it will jump to the nearest 5 FPS slider setting.

It's actually overwritten in NVCP by Virtual Desktop for me in VR, so I like to do it in-game. Virtual Desktop does limit to 72 or 90 FPS, but it does sometimes overshoot to 73/74 or 91/92 so that's why I do it in-game as well, as it seems to work better to remove any overshoots and keep things smooth locked at 72 FPS. Just a shame the autoexec.cfg setting does not work anymore. I can set it in options.lua, but that gets overwritten whenever I open the settings within DCS. Not a huge deal, just a nice to have, as the slider is now there, but is not quite granular enough for 36/72 FPS settings.

I like the Max FPS option in the GUI now in 2.9.1, however it does not allow setting 72 FPS for VR usage (only allows settings in 5 FPS increments). I used to do this in autoexec.cfg, but that is now not taking effect. I can set 72 FPS in the options.lua, but as soon as I open the options GUI in game it drops it to 70. I would be great if the Max FPS slider would allow changing in 1 FPS increments.

I like the Max FPS option in the GUI now, however it does not allow setting 72 FPS for VR usage. I used to do this in autoexec.cfg, but that is now not taking effect. I can set 72 FPS in the options.lua, but as soon as I open the options GUI in game it drops it to 70. I would be great if the Max FPS slider would allow changing in 1 FPS increments.

Thanks for the info. I tried this and now have an upgrade available for the Joystick Base 2-2... but it wants me to unplug the F-16 grip before updating. What a pain - means I have to disassemble the joystick grip from the base to unplug that finicky cable. Oh well, it worked and is still working after reassembly Thanks again for the heads up.

The new 2.9 patch rotor wash on grass, trees and dust is awesome! One issue I have noticed is that the cockpit windows/glass of other AH-64D's around me shows through the dust and is not obscured by it. This is the same with MT or ST, VR or 2D. Screenshot is from the start of the Sinai AH-64D Free Flight instant action mission (OB 2.9.0.47168).

I had this. It was outside of the screen area in VR. I just modified the "POS" value of the "[Window][###FPS]" section in "C:\Users\<username>\Saved Games\DCS.openbeta\Config\imgui.ini" to be 60,60 and I could see it again and drag it around. e.g.: [Window][Debug##Default] Pos=60,60 Size=400,400 Collapsed=0 [Window][###FPS] Pos=60,60 Size=224,277 Collapsed=0 [Window][Stats] Pos=386,257 Size=1355,253 Collapsed=0

Yeah, that's a thing. I just press a HOTAS button mapped to "reset view" to set things back to normal.

Make sure your "Current OpenXR Runtime" in Steam VR is set to "SteamVR". My workflow with Pico 4 is to start Virtual Desktop Streamer, start other required programs (like Sim AppPro and SimShaker). I then put on the Pico 4 and run Virtual Desktop to connect and view the desktop. Then I run VoiceAttack (so it picks up the Pico 4 microphone). Lastly, I run the bin-mt DCS.exe from a shortcut with no other arguments/options. I also have the "User VR Headset" option in DCS enabled. Not sure what you do with mt.lua - haven't had to do any of that and I don't have an mt.lua in Saved Games / Config. Might be worth saving your control settings and doing a full slow repair (with clear extra files) and also remove saved games DCS folder, then add your controller configs back in. Another tip with VD and Pico 4 is to set the SteamVR resolution to 100% in SteamVR and only modify it via VD streamer (e.g. Ultra or Godlike). I'm also using the 1.x current version of SteamVR, not the 2.x beta. null