Buzzer1977

Probably a hardware issue and not VA or SRS. Most likely insufficient cooling or insufficient power supply or damaged hardware from insufficient cooling or insufficient power supply.

I added all combinations of SR/TR for the S-300 on the map. All with the same layout, and the same targets circling overhead. Only the SAMs with a clamshell SR haven't even been able to fire once.

S-300 clamshell search radar is broken. A S-300 site with a clamshell search radar won't fire. See attached track, mission file, debrief and dcs.log. S-300-clamshell-bug.log S-300-clamshell-bug.miz S-300-clamshell-bug.trk dcs.log

There are 3 S-300 search radars: Big bird, clam shell, tin shield. None is mobile, all 3 are trailers without a tracktor.

A trailer without a tractor won't move in DCS and is not mobile. All other units required for a S-300 site have at least one mobile version in game. LID-A tracking radar -> just a trailer, therefore not mobile LID-B tracking radar -> mobile

I created a little test mission for all kind of SAMs. Seems like some SAMs have very hard times to shoot down anything. See track and mission. And btw. there's no mobile S-300 search radar. Making the SA-10 search radar compatible would be a nice solution until a real mobile S-300 search radar is available. SAM-performance.miz SAM-performance.trk

The S-300 (SA-10) units lack a mobile search radar, so a S-300 site isn't mobile. All other necessary units are movable, like the LID-B tracking radar. Would be nice to have a mobile search radar to reinforce SAMs in game.

Have tried for several days now to replicate it in single player, but it hasn't happen yet.

How to replicate the Bug

I was able to recreate the issue in the ME that triggered all of this. As you can see, the menu on the right has changed back to "Route" while the main screen is stuck in "Ammo". And as before reloading the mission from File->open results in the same stuck load screen. New dcs.log also added. I'm gonna investigate further how to reproduce it more exactly. dcs.log

I was just building a small plain mission to demonstrate another bug (the low performance with moving ground units), when ME decided not to switch back from "Ammo" to "Route" on a ground unit. I was able to save the mission file, but while reloading it DCS just hung in the loading screen for ever. Mission file and dcs log are added. Moving Units Performance.miz dcs.log

It seems like moving ground units are a performance killer. As soon as i add a few convoys to capture other airfields, performance drops extremely low.

A S-3B tanker got stuck in CAT 1 for ever while placing the launch bar Track file is pretty large because it happened in multiplayer. S-3B tanker stuck on CAT.trk

I've got a F-15E with multiple guided weapons (2*JSOW, 3*GBU-54B, 2*GBU-31(V)3/B, 1*GBU-24) After launching the JSOW via CC i can't switch to the other weapon stations which are still in 'INIT' state. Waiting until TIMPCT doesn't help either, i still can't pick a station in 'INIT'. Is this a bug or works as designed? How can i launch JSOWs with CC and while they're on their way do stuff with the other GBUs ? Track, mission and debrief are added. *SOLVED* Select another PROG with different STA in ARMA Trainig-F-15E-TGT.miz F-15stuckAfter-CC-JSOW.log F-15stuckAfter-CC-JSOW.trk

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.