Buzzer1977

After some time the F-15E is stuck in A/A mode. Can't switch back to NAV or A/G and the left MFD is stuck with the A/A radar and can't open the menu. Can't attach a track file, because they're way too large as it usually happens in longer missions.

How is your Quest 3 connected ? MetaLink or Steam Link ? Wi-Fi or LinkCable ?

In the example mission a F-14B (cat 3) and a S-3B (cat 4) will always collide on deck of the Forrestal. This results in a damaged F-14B jumping between the deck and the inside of the ship and it's wingman "gliding" over deck with only a few kts faster then the carrier. F-14jumpingDeck.log F-14jumpingDeck.trk Houthi-Hamas-Hezbollah.miz

Has been requested several times since the module released ...

The landing gear collapses after repair. Zipped track file added. Might be related to: P47RepairBug.zip

The blue RAF livery is missing textures for the external tanks and pylons. Did a file check to be sure it's not a installation issue. Track, log and example mission added. BlueMosquittoLiveryBug.trk dcs.log Normandie-MkI.miz

For those who prefer original training documentation: P-47D original manual 1940s USAF training film "How to fly the P-47 - Pilot familiarization"

@RealDCSpilot Is it so hard to understand that there already is OpenXR support in DCS? And that OpenXR needs a OpenXR runtime? And that nobody cares how the OpenXR runtime is called. Can be WMR, Pimax.dll, what ever ..... People just want to use their VR headset. They don't care if you like how the driver is called, or who made it, as long as it works, which WMR (yet) does.

I'm pretty sure it's the other way around and you're mixing up things. OpenXR a API that relies on a OpenXR runtime, and in the case of WMR devices the OpenXR runtime is WMR.

Which is wrong. They literally said it in their release note: It is deprecated as of now and will be removed in a future release, which is Q4 2024 for Pro and Home and Q4 2025 for Enterprise.

"no one" is everybody with a WMR VR headset.

What does this mean to DCS VR users with WMR / SteamVR headsets? https://learn.microsoft.com/en-us/windows/whats-new/deprecated-features?ranMID=24542&ranEAID=kXQk6*ivFEQ&ranSiteID=kXQk6.ivFEQ-LL9a9nOYiiInA01N0LKr8A&epi=kXQk6.ivFEQ-LL9a9nOYiiInA01N0LKr8A&irgwc=1&OCID=AIDcmm549zy227_aff_7593_1243925&tduid=(ir__d926c190x0kfd2l22dux2jo1yu2x92ueqc3kmw6200)(7593)(1243925)(kXQk6.ivFEQ-LL9a9nOYiiInA01N0LKr8A)()&irclickid=_d926c190x0kfd2l22dux2jo1yu2x92ueqc3kmw6200

Each time this bug is added, it's one more. If it's ten times in the bug list, the it's now eleven times in the bug list. It's one buggier.

@IronMikeAny news on this? I only see the "coming soon" on the F-4 in Steam. I already preordered directly via heatblur for my sons non-steam rig. He's gonna tease me all day long if he get's his hands on the F-4 first, because his 'ole dad still waits for the F-4 on steam.

It was added too the bug list quote often. But why is it not priority high anymore like back in July? https://forum.dcs.world/topic/329827-all-nevatim-spawns-start-in-air/?do=findComment&comment=5253156

Two other common things that cause similar issues: 1.) Reduce the framerate in Windows Mixed Reality settings from 90Hz to 60Hz. If your system can't feed the G2 reliable with the high 90Hz framerates in all conditions, the G2 goes black. https://forum.dcs.world/topic/328615-reverb-g2-goes-blank-when-dcsmt-is-under-load/#comment-5243131 2.) If this doesn't help, try a new G2 cable. The 6m long G2 cable maxes out all signal specs, so a sharp bend in the cable or a bad contact in some positions might cause a black out too.

There's a bug fix firmware for the G2 with the audio issue. "Resolves a potential issue where displays may flicker or go black when playing certain titles at high volume levels." https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-reverb-g2-virtual-reality-headset/33835976/swItemId/ob-271221-1

Iraq operated the F1 since 1977 and during the Iraq-Iran war, but the F1 is not available with the historic unit filter enabled in the 80s.

It would be nice to have some documentation like a spreadsheet about which units can use which frequency spectrum with which modulation. Especially now that VoiceChat is a thing mission planing will be more interesting in regards of using the right frequencies.

Jep. @Lange_666 It only happens in single threaded. In VR i'm using MT, in non VR i usually don't care because i mostly use it for mission editing and testing mission scripting, but it seems i'm in ST when not using VR. @Flappie Can you also verify that it happen in single threaded?

When repair/verify has passed i'll give it a try to verify. I don't have the issue when playing in VR ...

Not that i would know and not with a vanilla virgin DCS folder ... Currently running repair verify to be sure.

Did it again with a vanilla and virgin DCS folder, but the issue remains. Added DxDiag ... DxDiag.txt

Sample mission, track file, options.lua and dcs.log. Good to see that the KC-130 and IL-78m aren't affected, only the C-130 / IL-76md cargo versions. It also only happens in 2D, and not in VR. dcs.log options.lua WireFrameBug.miz WireFrameBug.trk