Glowingheat

Not sure what changed, but I used to jettison the bomb racks once the bombs had been released, but they remain on the aircraft even though I hear the clunk as they should be falling away....? Is that a bug or by design?

Oh I see - that'll teach me! Is there a technical reason why this happens in the real aircraft?

Not tried it in other modules, but when air refuelling the A-10C, after the first contact and successfull connection, if I get disconnected I cannot then get contact again - I have to close and open the receptacle before trying again - its the only way to get connected after the first disconnected attempt. The boom does some weird juddering too - which I'm sure it never used to do as it hunts for the hole.

Is there a date on when the Viggen will be out of Early Access? It seems pretty complete from my limited understanding. I recall someone sharing a Viggen roadmap - where do I find this?

If it supported VR, I'd buy it, shame there are no plans.

Am I missing something with regards to the Autopilot lights? I can't unselect altitude hold anymore, the only way is to disconnect it is by pulling the stick beyond the altitude hold limit.

Disable Sliced Encoding in your Oculus Debug Tool.

Disable Sliced Encoding in your Oculus Debug Tool. Fixes it for me.

I tried ST and it's much more fluid on my system too - this never used to be the case, MT was much better when it was launched - but at some point since then, got worse. My system is an i9 10900k RTX 3080 and Meta Quest 2

Just to add this doesn't happen in the ST version, only the MT version.

Since the most recent patch hotfix, my Quest 2 screens go black after a few minutes of flying. Didn't happen before. Ran a repair yesterday after Malwarebytes quarantined the dcs-mt.exe ANyone else seen this? I know my headset is old, but as I say working fine two days ago.

Malwarebytes never used to quarantine the DCS.exe or DCS-MT.exe files until the most recent hot patch yesterday.

Interestingly, one last look, I noticed that its only the MT version that gets quarantined.

Just to add that this only appears to affect the MT DCS.EXE - the single thread DCS opens just fine. Would appreciate some advice. Aside from excluding the entire DCS folder from malwarebytes.

Finished the slow repair, but Malwarebytes still complaining about Ransomware with DCS.exe - so I'm calling it a night, good luck everyone I'll check back tomorrow and hopefully ED will put out a solution.

Thats all good advice. I don't do any of those things, so when I see a trusted app saying suspected Malware in another trusted genuine app you do stop and think. I completely understand having worked in IT since 1996 - it's not worth the hassle and disruption even with backups and what not.

Now I may be being over the top, but excluding an entire app from the AV checker is surely not a great idea? Plus so far, excluding DCS hasn't worked, some of us are running repairs as we speak in case a file is missing or corrupted.

My Malwarebytes says removal failed - it's just the ransomware part that bothers me, even if its a false positive, it fills me with utter dread!

Me too - doing the slow one.

Not sure why they released this patch so quickly before testing it thoroughly....

@BIGNEWY There's some more people with AV issues in general bugs and 'game crash' - my Malwarebytes reporting ransomware and quarantining DCS.exe! Please help!

Are you both using Malwarebytes?

Let me know because I'm a little nervous about allowing it since the damage ransomware can do would be devastating to me.

Are you using Malwarebytes? I am and I think it's quarantined DCS as ransomware LOL

Since the latest small patch released today, Malwarebytes is reporting: C:\users\mypc\desktop\dcs.exe - shortcut.ink Malware.Ransom.Agent.Generic HKLM\Software\Microsoft\windows nt\currentversion\image file execution options\DCS.exe Quarantined due to Ransomware characteristics Can anyone confirm how to bypass and indeed should I bypass this message.......?!