DroptheHammer

Attached... although it's the log I can get to remotely since I'm at work. There are mods installed in that log, but all savedgames mods. Also, my bug is the same for both a clean repair and a modded install. this log was from our mission night the other evening. I was able to fly the Mirage using the flashlight to highlight the cursor. dcs.log

I have the DCS Cursor black issue with MT and opened a separate thread for that....

I posted a separate thread on this as well, except mine is focused on VR. No matter if I use Yolomouse to replace the cursor or not.. it remains black in VR even after full repairs, full reinstall, clearing of graphics drivers and flushing of WMR VR applications. Only way I can spot it inside a dark cockpit is to enable the flashlight for the surrounding glow

so... ok I get it.. maybe the old super bright blue cursor was a major nightvision destroyer (especially in OLED VR headsets like my Bigscreen Beyond). But why black? especially at night? for everyone? Can we not just get a daytime and a nighttime cursor that are reasonably colored or let us choose the colors? This one is silly. Steps taken so far to resolve.... Repair, Slow option, clean all extra files. FXO and Metashaders directory delete Display Drivers removed and reinstalled via DDU to latest nvidia driver. WIndows mixed reality removed and reinstalled Still black cursor. I also tried to replace it with YOLOMOUSE which does work in 2D just fine to replace the yellow cross cursor... but it does NOT replace the cursor in VR. That cursor remains black even though the Yolomouse software has selected and implemented a replacement.

See above, can only spot with a flashlight at night

are most of you guys on windows 10 or 11?

While I dont run that switcher, I have the same functionality in OpenXR Explorer... One thing I discovered this morning was that with --force_OpenXR enabled... even if Varjo is selected, it gets wiped and the log entry like daddio007 appears. 2023-07-26 17:18:11.764 ERROR VISUALIZER (Main): OpenXR exception: runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:322 If I remove --force_openXR the game actually starts working again and varjo remains enabled. Wierdly though, I get a mask that doesnt match the aero at all. See attachments. This is the first time I've had current VB able to launch with post-41066.1 DCS. I dont believe the mystery is solved yet since up to this point, all advice was to leave --force_openXR enabled, and the mask isnt the right mask and the image is just weird in the headset. However, the log failure to find runtime does not appear. My belief still is that current DCS and current VB aren't identifying the headset properly (for some headsets)

I’ll give this a test tomorrow morning and see if I’ve also got the same solution.

"S:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR ^^ My Prompts

I think he means it only worked AFTER he rolled back to 41066.1.... Which isnt really a solution since we both want to be on the latest open beta. Today's patch. also ineffective to this... I went to it. was unable to launch.. back to 41066.1... game+headset works again... Something is still broken after patch.

Nope... still broken. I guess I'm going back to 41066.1 again @Jyge

Anyone try again this morning on the new patch? If not I’ll give it a go in a few hours.. for me on the prior patch didn’t matter if I had DFR enabled or not or toolkit enabled or not… my aero just doesn’t launch with DCS unless I roll back to 41066.1 then it works fine no matter what combination of DFR and OXRTK I’m using (within mbuccias support matrix)

I can confirm with @Jyge that I am also a recent delivery Aero user (received 24 hrs ago). I went through the same testing loop as him and ended up with the same resolution... DDU'd and went to latest nvidia drivers 536.67 - FAIL WMR Removal and Reverb G2 Drivers purge - FAIL double check --force_enable_VR --force_OpenXR was still enforced on MT (Yes I had this for my reverb G2 before, so it worked great) - varjo FAIL(still works on reverb G2...) full DCS SLOW repair remove all extra files - FAIL disable OXRTK - FAIL uninstall OXRTK - FAIL Varjo Foveated 2.0 - FAIL Mbuccia Quad Views Rendering - FAIL Attempt to use DCS Single Thread (this is where my story differes from @jyge) - FAIL Enable VR Headset Checkbox on - FAIL Disable VR Headset Checkbox - FAIL Re-Enable VR Headset Checkbox - FAIL Rollback to prior version of dcs 41066.1 - Success Varjo FOveated 2.0 with 41066.1 - Success QVFR with 41066.1 - Success Install and enable OXRTK - Success Toggle VR Headset Checkboxes - Successes, doesn't matter. Reinstall G2 for side by side testing - Success I don't know if it's some difference between firmware or headset construction more recently that recent owners aren't connecting and older users are... But either way. Something broke in the last update that is keeping us from using DCS.

My problem is I’m supposed to be testing and or returning this headset in a limited time window and DCS is the only app I’m really concerned with. I assume you’re flying ok in the older version so i suppose I’ll rollback to test…

I'm having the exact same issue as OP! Reading this thread was like mimicking all my frustrations of the past 4-6 hours trying to get this to work. I've done a DDU, latest nvidia drivers, full repair install slow (twice) and cut and pasted enough shortcut endings to go nuts. @jyge, did you just roll back and update again? are you on the latest OB now or is this a problem with the latest version of OB regardless?