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?

Prior to this patch, enabling HAGS in windows and running VR in DCS had around a 5-10% FPS hit as well as a lot of stutters and jitters. AFTER the patch... No matter if I use ST or MT... HAGS ON or OFF makes zero positive OR negative differences. So now you can leave it on for your other games like MSFS2020 DLSS3 or Cyberpunk 2077. DCS was the last game for me that caused me to keep HAGS off and now I can safely say that's no longer the case. Proof attached! System in signature. I also was on Discord, Teams, OBS was streaming, my full office suite was up.. tons of files open etc. For reference, the below is ultra settings 250% render resolution HP Reverb G2. F-14 Persian Gulf carrier quals and F-16 Syria Free Flight. used to be that F14 PG CQ was my CPU Bottleneck test (around 48 pre patch, 65 post patch and 90 post patch MT) and F-16 Syria FF was my GPU Test (Around 72 pre patch, 78 post patch, 90 locked post patch MT). Also running latest 531.29 driver.

I’ve run it through my test suite of around 15 different reproducible scenarios, some cpu and some GPU bound. Some multiplayer and others also on a 4090 with 13900k at 6.2ghz. native for native in all cases 100% oxr res with oxr toolkit disabled vs steamVR at 100% global and 100% app. i tried reprojection on and off and compared all 4 setups. I did not see your claim of increased fps in steamVR come to reality in any scenario in a measurable way @more than 0.5ms cpu or GPU in a consistent way. HOWEVER this is still an amazing piece of work for steamVR. Prior to this release there was a clear winner In OXR and now in terms of performance and clarity at default settings it basically makes no difference which compositor is being used. fantastic work to the steamVR team and windows mixed reality for streamVR team. where you do notice a difference is in the reprojection…. The steamVR one handles some limited scenarios much better than OXR for reasons I’m not able to determine. The Apache rotor blades shapes and movement matches the shadow in steamVR but is just a broad sweeping “wiz” in OXR with reprojection on. So if you like reprojection or are an Apache pilot… steam is prob the way to go. Personally I prefer reprojection off and then ifs a dead heat performance / clarity wise. What will keep me with OXR right now are a few key things. #1. Ease of launch and close without steam needing to be in the middle. #2 the “Input smoothing” feature of OXR makes my streams buttery smooth with no VR “helmet shake” for my viewers. #3. Color, contrast, hue and other controls in OXR Toolkit without the lag of reshade in steamVR and finally #4.built in scaler, fov, fixed focrared rendering and other controls end up giving OXR the performance and clarity edge again if you really want to tune things a lot. In my case this is done steady and I’m locked 90fps at 250% render res. with better color and no shakiness. for a new/casual user…. Just stick with steamVR. It is super efficient and smooth now and frankly once I turn off the FPS counter I just can’t tell the difference anymore on equal settings. great job devs.

I attempted to correlate this with PTT presses but in a crewed aircraft with NOBODY pushing PTT at all... we still had the radios jumping 0.005 at random. I dont believe that is tied to PTT at all.

Fast INS is really a scramble setting mostly for air defense work. Where being off a few hundred feet isnt a big deal.

Hello all, I've got some missions that I want to practice in various conditions but I'd prefer not to keep opening, changing and saving every time I get a new version. I'd like to script the following but I'm not sure where the various variables lie within the .miz. Each mission would be split into the following. Daytime - mostly clear Afternoon - Heavy IMC / Rain Night - Clear with moonlight Night - IMC conditions For example I have a training range file that I use. Rather than replicating each of these I'd love to automatically split that file (as I upgrade it from time to time) into the 4 with the time/weather presets. Regards, DTH

https://www.twitch.tv/videos/1638295465?t=01h23m04s You can see my squadron dealing with this for around 90 minutes on our weekly mission twitch VOD linked above. You'll notice at random both of my radios (in my crewed F-14B) continue to mhz hop and the tanker doesn't respond to us. However, our wingmen flying with jester, as well as the F-18's were able to hear the tanker, AWACS and ATC calls etc.

Which segment is only the haze reduction? it's the primary reason I mod shaders anyway and maybe I just need to do that part on my own.

Not sure about y'all, but I really prefer flying without the radar shroud. However, on some maps/missions etc with airstart... I cant remove the shroud in flight. Can we change this? I'm sure realism wise i dont have anywhere to "put" this thing inside the cockpit but... not sure realism over fun is worth it on something like this. It's not the same thing as changing from JHMCS or NVG mid flight (not possible ,and gives a false gameplay advantage). This is purely cosmetic.

So the radar bug on the screen, currently has hard keybinds of left,right,up and down as well as the TDC Depress. Given that it's a control stick. When can we get a proper X/Y axis for the TDC to make selection smooth with standard throttles or a second joystick (to mimic IRL)? Thanks in advance! This thing is my favorite plane to fly since the F-14 released. Analog 4 lyfe.

Thanks, this reply is excellent! I’ll give this a go over the summer and see if we can migrate to this. Appreciate your hard work on this and your detailed reply.