Fizzle

On mission 5 after both salutes I’m stuck with directors crossing their flashlights over their heads and the ”taxi prohibited” message. I tried waiting several minutes. Ignoring them and heading to cats 1 or 2, the crew ignores me and won’t launch. Anybody else seeing this or am I doing something wrong?

If you have moved your Saved Files from the default path, note that HaptiConnect won't find your Scripts directory correctly. It will write an export.lua and some other scripts to the default location, so you can go grab them there, copy them to the correct location, add the line to your actual export.lua, and get it working that way. This is HaptiConnect 2.3.1, the latest as of today.

This weekend I also found that an unarmored SA-10 TEL took 2x282s to kill but a single 151 HE would do the job. Happy to provide a track if it would help, but it's trivially reproducible.

From the most recent changelog, DCS 2.9.3.51704: Something is amiss, here. 282s used to be a completely reliable way to kill lightly armored vehicles like BRDMs, BMPs, Shilkas, etc. with a single rocket. Since the patch, it virtually always takes two. Are others seeing this?

Seems unlikely this was intentional: Texaco in Mission 9a is flying at 190 knots. I sort of assumed I could refuel if I wanted to, then end the mission and move on to part 2, but having the tanker so slow made this impossible.

Curious why you removed this. It was handy whenever ED shipped an update, to ensure the backup data was good when you re-installed mods post-update.

Yep even a small wing rock will fix it, so you can do it pretty last-second before releasing if you have to.

I’m using OpenXR and still the older varjo-foveated DFR. No OpenXR toolkit.

A few days later I have had a single instance where DCS didn't start in VR with this set. So it's not a complete fix, but it's definitely a big improvement. Used to get VR starts about 20% of the time, now it's more like 90%.

I'm ashamed it took this long to find this, but checking the "Enable Virtual Reality Headset" option in the VR settings fixed this for me. I've been using the --force_enable_VR switch so long I forgot that setting even existed. With this setting ticked, the startup argument is irrelevant and DCS is starting in VR every time. It looks as if the last patch introduced a race condition that affects reading launch arguments but not config settings. To avoid having to launch DCS twice now when I want it in 2D (the first time to change the setting), you can modify the ["enable"] = true value, the last line below, in [Saved Games]\Config\options.lua. It has the same effect as changing the setting in-game. options = { ["VR"] = { ["bloom"] = false, ["box_mouse_cursor"] = true, ["custom_IPD"] = "62.4", ["custom_IPD_enable"] = false, ["enable"] = true, Hope this helps somebody else.

Are you overclocking? Monitoring temperature? AVX instructions can really increase temps and you could be seeing thermal throttling by the CPU.

Almost certainly a DCS bug. Don't waste your time re-installing the whole OS!

Not sure another anecdote is helpful in any way at this point, but I find this to be a massive improvement with a Varjo Aero at max ppd.

I figured this out from info here, here, and here. Modify your existing (or create a new) steam desktop shortcut and change the URL to steam://launch/223750/option1

Ah! Got it now. Thanks @LazyBoot and @A10Yoda.