tribbin

Yeah seems probable. I'll leave this here for if anybody else encounters it.

I cannot find any (recent) report of this. The trackfile I have is huge. If this is a new bug, I will see if I can reproduce it.

Will do. (But track files during an ECW session tend to be huge when I encounter this and previous big track files have been denied here.)

Thank you. FYI We all have great internet connections and the pilot (British), left-gunner (German) and I (Dutch) connected to a close-by server (ECW) in Germany. For the electronic compass, it was the British guy as pilot and I was co-pilot. The electric compass-problem was consistent for any co-pilot. I'm pretty sure that if the MP testers use a busy server like ECW, they will have no trouble replicating these issues. (we have not tried our own dedicated server yet)

I fly the MiG-15 pretty much exclusively and have many hours in it. Sometimes I can only set the gyromagnetic compass once, after which I'm stuck with the (potentially) wrong heading the rest of the flight, for instance when I let go of the fast slave button too early. Any time this happened, I had already built up a large track file, so I never submitted any.

Today I flew the Huey as multicrew (on ECW, with VR) for the first time. Many problems. As the right gunner, when I pressed the trigger my left gunner would fire. After reseating the slot I could not fire at all. As the left gunner (with no right gunner) I had no such problems. After above-mentioned reseating as gunner, my eye-level would be unusually high. Rotor low-RPM alarm inconsistencies between players. Electronic compass for co-pilot not working, making it difficult to navigate. Still had a blast as a 2-person crew, taking down a Frogfoot and two Hinds.

For our MiG-15 pilots a sustained low-speed turning rate is our biggest advantage in fights. Since the last big update, the mechanics have changed and a prolonged sustained turn can lead to a sudden G-lock. Hoggit-people who don't read questions and don't think keep referring to the F-16 changelog information, which makes no sense for an aircraft without a G-suit. The description in the changelog somehow implies that the direction of your turns during g-warmup matters, which gives me the impression that it is some mythical combo you have to do to unlock G-resistance. What are the variables and 'formulas' for G-resistance, for aircraft with and without G-suit?

I can't imagine ever flying without VR. Are there people who have flown VR and stopped?

The problem is solved with today's patch, tank you very much!

Will test this tonight.

Last week, the delay was already announced by now. So that gives hope.

ED does not have the code of the F-15, according to CptSmiley (RAZBAM).

I've been running DCS on Linux (through Steam/Proton) without problems for a very long time, but bought a Windows license some months ago so I have VR support, which is something that ED can't really fix for Linux. https://www.protondb.com/app/223750

Oh boy. Anyway, pretty much anybody that tried this has been happily playing DCS ever since:

Two comments above your comment is the solution that has worked for many, including me on W11.

Reposting my solution that has worked for many people, because it has ended up many pages back due to discussions. Happy flying this Easter weekend!

Halfghanistan is fake news; you only get one-third:

You need to go to service manager and disable Oculus stuff.

Stop it in service manager, as it will otherwise restart.

I tried it too, but I get motion sick when screens don't move with my head movement and the epileptic flickering is torture.

Maybe ask Dookieshoes73 for his version of that folder:

I'm not familiar with what debug tool you are referring to. If you have an instruction on what I must do to help gather information, let me know.

Multiple people were successful with my instructions:

Re-installing now lets you end up with v63, since yesterday.

It seems it was presumed that people could just disable the updates as a workaround...