NBee

I have found the solution to the problem: I use Varjo-Foveated-0.2.0.msi with my Varjo headset. If I uninstall Varjo-Foveated-0.2.0.msi then DCS_mt can start in 2D when VR is enabled in options under VR settings without headset connected.

HI @Hornblower793 First, thank you for your time and effort in reading through my log. But unfortunately, neither of the two proposals has solved the problem. I have run DCS_updater_repair (cehck all files (slow)) and subsequently renamed DCS_Openbeta to .old started DCS_mt (2D) without problem. Then I set VR as selected under VR options and restart DCS_mt without headset connected and DCS crashes.

For info: I can see that DCS generates 2 crash logs every time I start DCS_MT without VR connected. I have attached both. First file is dcs.log-20240414-130739 and then DCS generates dcs.log-20240414-130817 after about 10-30 sec. dcs.log-20240414-130817.zip dcs.log dcs.log-20240414-130739.zip

I normally use a VR headset (Varjo Aero) when playing DCS, which means that VR is enabled in options under VR settings. I experience that if I want to start DCS without the VR headset connected, it crashes if I use \bin-mt\DCS.exe. But if I use \bin\DCS.exe, I can start DCS in 2D without any problems. This also means that when I update DCS via DCS_updater without the VR headset connected, the game crashes when DCS_update automatically starts DCS mt after the update, which is a bit annoying. Is this normal?

Tanks @BIGNEWY Just for info I tried same mission with A10CII + AV8 + Mirage 2000 and was not able to reproduce. But F-5E => same problem no DME on TCN after low-level flight: see attached log and track file. So perhaps it’s not just a F-18C issue? 5.log 5.trk

It seems as the TACAN in the F18C does not automatic pick up the DME (Distance) signal after low-level flight. Starting at 15000’ setting TACAN to Cn 13X, picking up the TACAN signal + DME. Then decent to low-level behind mountains, stay low until TCN signal diapers. Start climb until TCN signal is picked up by the receiver => DME not updating distance to TCN Turning TCN in aircraft OFF then ON brings DME back. 13.trk dcs_13.log CVN73_TX1.miz

Just tested the same mission and I can confirm that the issue has been fixed in last OB patch. And @Flappie Remember to thank the hard-working developers and the team behind DCS for their effort.

Thanks for the quick respons.

Anyone else having this problem in VR? I’m experience “whiteouts” meaning I sometime experience a fast flash of white light that blanks the screen out for a millisecond, just like a fast flash, this happens with different intervals during missions, especially at dusk and nighttime. VR Varjo Aero, Latest DCS patch, Win 11, GPU 4090 AMD Ryzen 7 5800X3D.

Awaiting delivery.

As I wrote earlier, this problem was the result of turbo mode in an old version of OpenXR Toolkit ver. 1.2.3. But I also had the problem afterwards as a result of a headset that was defective, The headset freezes for 1-2 seconds, then it wakes up again for about 10 seconds, after which it freezes again for 1 second, after which it works without problems. I had the headset replaced under warranty via Hp. which solved the problem temporarily but unfortunately the "new" headset has developed a "black screen" problem and won't boot so I don't think this problem is DCS related but a result of of, two a row faulty, headsets from HP. So I have decided to replace my headset with a Varjo Aero instead.

@Flappie Just an update I have not experienced any crashes for a long time, only problem I’m having is temporary blackouts lasting 2-3 sec in the headset (HP reverb v2) when playing. But I don’t know if this is related to DCS, Nvidia driver, my Graphics card, or my headset. I’m using: DCS MT beta latest version + OpenXRToolkit + Tacview. Edition Windows 11 Pro Version 22H2 Installed on ‎21-‎09-‎2022 OS build 22621.1778 Experience Windows Feature Experience Pack 1000.22642.1000.0 Processor AMD Ryzen 7 5800X3D 8-Core Processor 3.60 GHz Installed RAM 32,0 GB Graphic card: RTX 4090 Gaming OC 24G Nvidia Driver version: 532.03 (without Experience) System type 64-bit operating system, x64-based processor

And here is one more crash in MT VR mode dcs.log-20230402-121626.zip

Just want to show the difference between Multi-threading On vs off in terms of FPS and CPU Load System win 11 AMD ryzen 75800x3D Nvidia 4090 Same track replay with and without MT · Blue track is FPS with MT · Yellow track is CPU Frame time with MT on · Orange is FPS without MT · Gray is CPU Frame time with MT OFF Conclusion: In my system MT dos not help in getting higher FPS since I am GPU bound most of the time. But if you look at the CPU frame time you can se a clear difference, the frame time is significant lower with MT on. So, systems with CPU limitations will benefit from MT. One thing I have noticed with MT on is that the graphical quality seems to suffer, and introduce shimmering

You might be right in your assumption I’m not a specialist. But I’m thinking like this: I want to save power (My PSU is only rate to 750W) and at the time get a stable clock speed that gives me a minimum FPS count > 45 with a low FPS fluctuation. So, my approach is the following: Power limit Is the max power the graphic card is allowed to use. And within this limit the card will try to reach max clock speed, and when it then hits the power limit it will throttle down meaning that there is a risk of getting unstable/fluctuating clock speeds as a result. So, if you at the same tells the card to never to exceed 2700MHz above 950mV then you “hardcode” the highest possible stable clock sped available within your set power limit and thereby in “theory” this should minimize the fluctuation of FPS. I have attached the track file that I used Mirage2000 vs SU 33 over Syria. 2 mirage vs su33.trk

I have not experienced that there is a difference in the graphic quality of DCS when I test. However, it is absolutely certain that DCS crashes if I experiment with adjusting the Memory clock in MSI afterburner.

In DCS the GPU speed is relatively stable around 2715 MHz in the OC Bios.

Just want to share my experience with power limiting and undervolting my Geforce 4090RTX in DCS 2.8.2.35759 Open Beta Settings in: OpenXR Tools for WMR is custom render scale ON and 100% MR Disabled OpenXR ToolKit: Turbomode ON The data below is recorded with OpenXR ToolKit by replaying the same track file in VR (HP reverbG2) Ignore the first 8-10 sec of the graph since this is a recording of starting the track file and activating with OpenXR ToolKit.

First I located the problem for the blackout/crash. It seems like DCS don’t like Turbo mode on in OpenXR Toolkit ver. 1.2.3 when its on DCS locks after some time in VR. Launch method: I use DCS native support for OpenXR no Steam or OpenComposite app installed.

I have problems with DCS generate black screen in VR headset and freezes game in WMR. Using HP G2, Windows Mixed Reality + OpenXR + OpenXR Toolkit and DCS native settings "F:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR System spec: Lates DCS-beta, Win 11, AMD Ryzen 7 5800X3D, Nvidia RTX4090, 32 Gb RAM See attached 3 x log files. Crasch 1 dcs.log Crasch 2 dcs.log Crasch 3 dcs.log

DCS_updater_repair solved the problem.

Hi mbucchia Thanks for the explanation. I have done the restore, all is up and running.

DCS Crash in VR and OpenXR toolkit When setting HAM: Fixed foveated rendering to PRESET Cull outer mask yes and HAM Then crash = black screen in headset See attached logs.

When I replay track files on my monitor that have been created flying in VR (HP Reverb 2 and OpenXR) the replay is Zoomed way in se pic below. Is this normal behavior? Or are there some settings in DCS that need to be checked/un checked in order to replay on a 1440P monitor without the Zoom efekt?

Hi Flappie Sorry for the late reply. But my job has negatively interfered with my free time. I have now tested and I cannot reproduce the issue. Thank you. Don't forget to praise the developers for their efforts.