Major Corvus

I was having this same problem (crashing on game launch) after returning from a two week trip away from my PC. During my time away my PC needed to make various updates such as Windows, Nvidia GPU, DCS (obviously), Vario base and HMD firmwear. DCS crashed on launch everytime after these updates, and after following the suggestions in this thread still I couldn't get it to stat, that was until I reread the instructions on mbucchia's Github for the very excellent foveated enhancement. The long and short of it is that even though I don't run the OpenXR toolkit comapanion app in DCS, I started the app and checked the 'disable the OpenXR toolkit' box and closed the app. The next time I started DCS in MT and VR, it started perfectly and looks better than ever (Thanks mbuccia)

Yes it's the same for me too as I only fly in VR. At the moment it looks quite blurry with lots of shimmer using my regular DCS settings. It's a good looking map at altitude though, so fingers crossed for further optimisations

Same issue just for info. Chilling for the fix

I wouldn't mind the delays so much, if there wasn't so many YouTube teasers from Razbam and selected YouTubers. They really are starting to get squarely on my nerves now, and Razbam need to poop or get off the pot

Solved. There was a coincidental update to the Varjo Base software that appears to have over written Mbucchia's OpenXR wrapper as found on a previous Aero OpenXR thread. I have reinstalled the wrapper and made new shortcuts and now both ST and MT are working

As per the title. When using my Varjo Aero and trying to start the sim Via a shortcut from the bin-mt floder with the added --force_OpenXR in the target, the sim seems to try and start as usual with the version loading screen and the log in bars displaying briefly. However, following this DCS apears to be running on the task bar but there is nothing displayed on either my desktop monitor, or in the HMD. moving the cursor across my desktop has it disapearing and reapearing as if the mirror is displaying as normal, however there is no display. The only way I can shut down DCS in these conditions is via the Task manager. Unfortunately, this exact behaviour is now replicated when I try to launch using the normal ST DCS.exe. If I try to launch using the ST DCS.exe from the folder without the --force_OpenXR modifier , I get the usual quad screen display that you get if you don't use the correct modified shortcut, and when I try using the DCS.exe from the bin-mt folder, I get the same issue as if I was trying to launch it using the moddified --force_OpenXR shortcut. I can get the DCS single thread version to start in steam VR, if I use the ST shortcut with the --force_steam_VR modifier. However If I try the same but using the bin-mt shortcut, DCS starts to load but becomes unresponsive and freezes at 16-19%. DCS wil start in both ST and MT in 2D mode, but as it stands at the time of this post, DCS is completely unplayable in MT and is very compromised in Steam VR in ST. System: i9 10900, RTX 4090 and 64gb ram I hope this can be rectified soon

I'd just be happy with giving the canopy glass a clean

Joking aside, this is actually a big problem in VR. The state of the canopy glass on the F-5 really makes dogfighting and general target spotting even harder than it already is.

Will this fix the terribly dirty canopy glass?

I actually meant in such missions you'd start in a running hot started aircraft, but I understand that you're restricted by the host sim. Thanks and keep up the good work

Firstly, I'm a fan of Reflected's work and I appreciate the amount of effort and passion he puts in to these campaigns. I'm only on mission 3 of this campaign, so that's two flyable one's and the mission one intro, but already I'm getting anoyed at the fact that on such time sensitive missions, I'm having to cold start the Anton and taxi for take off straight away. In mission two (defending the sub Calais harbour), the briefing, start up and taxi for take off all has to occur in four minutes to comply with the wheels up time. Additionally, the rest of the flight Taxi to a runway intersection intead of the end, which means that I was unable to use the full runway length for take off whilst weighted down with an external fuel tank. So on the first two times I attempte to take off and make the timetable, I had to use full power with cold oil which resulted in a damaged engine that failed enroute to the objective. Eventually I was able to tease the plane up at reduced power, almost clipping the perimeter fence and stalling, and was able to warm the engine up whilst flying at a low power setting orbitting the airfield, and the rest of the mission was great with the usual high standard of voice acting and mission design. Mission three is an emergency scramble situation, and again I started in a cold and dark Anton. I quit out as I was still annoyed from mission two. I'm no expert on the subject, but I'm pretty sure the ground crew would have started the plane as the pilot ran from the officer's mess or where ever he was when the bell rang, and DCS being as realistic as it can be, the Anton takes something like ten minutes to warm up fully, and the oil temp hardly moves for the first five minutes, and even before you can start the engine there's about a minutes worth of breaker pushing and fly wheel energising. Are there more missions where the timetable is as tight as this on this campaign? I love cold starting a plane in VR, as it really adds to the immersion and builds a sense of involvement, but I find cold starts in these situations to be annoying, and something of a deal breaker.

Varjo Base update today (3.7.2.13), and the Varjo is back to full funtionality and the best it's ever been on the RTX 4090. Buttery smooth on the High preset and completely stutter free. DCS has never looked better

Yeah I'm getting this one too. I'm glad to see that it's not just my rig

I have just encountered the exact same issue as this. Almost exact flight parameters and the exact same lights on the failure warning panel, with the same fuel issue. I was able to land before fuel starvation, but without lights or primary instruments. No track file.

Yes, this one worked for me too