michap7

Hi! Suddenly, one day after the installation, I get "No data found" when tying to choose month and week manually... Anyone else?

Ok, thank you, I´ll give it a try - but I think I was within the limits and reducing power unfortunately did not stop the sound....

Ah, ok. No, it seems to be the same sound as the altitude alert but constantly repeating....

I am still constantly getting repeating beep sounds on climb out, no mater if I use VS or IAA or even when handflying the departure... I do not understand how to solve this or what I´m doing wrong.... 😕

It´s more a continously repeating beeping sound, not the altitude alert. It starts around 1000 feet and never stops... And on the CAWS I see the green "AP TRIM" light, but this should be normal...

I like it a lot, but when airborne I am constantly getting repeating beep sounds, possibly due to AP TRIM but do not understand how to solve this....

Exactly the same for me...

That´s what helped in my case, thanks!

Interesting: Just had a 5.87 kB (yes, kilobyte!) update installed via the sim (old-fashioned DVD-Version) itself... Nothing via the store...

Fortunately I could finally solve my CTD problem. Disabling the explorer integration of Capture One AND renaming the above mentioned file led to no more MSFS CTDs on my system (until now). So let´s hope...

😁

Meanwhile Zendesk officially aknowledged a problem with Capture One and wrote: "Hi Micha, First, remove Capture One from your system because we know that this software can prevent Microsoft Flight Simulator from running properly. Then, please install the Xbox App."

From: https://forums.flightsimulator.com/t/ctd-caused-by-capture-one-20-codec/452538/30 Go to your Capture One installation folder Rename the file “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll” to “Capture One 20\WIC\WIC64\P1.WIC.NativeComWrapper.dll.off” i additionally disabled the Windows explorer integration in Capture ONE

In Windows, I think they belong to the shell intergration of Capture one. For what reason MSFS loads them Idon´t know... Yesterday I disabled the explorer shell integration of Capture one and did some short flights in areas usually prone to CTDs without any problems. Now I have to do some real world work and have to try more flights later.

In my case it could be Capture One which is interfering with MSFS. But unfortunately I reinstalled some software (including Capture One) before reinstalling MSFS. I will have to further check it later...