Secondator

Could you try to enable the experimental updates through the configurator and updating to the latest experimental. Let me know if that works. If not, could you try as a last resort reinstalling the smaller busses again.

Hi I tried this on both A320 and A330 on both P3Dv4.5 and P3Dv5 but I am not able to recreate this issue. Only thing that comes to mind is that there is something that is conflicting with your controls and somehow setting the flaps back to 1+F for some reason. Other than that I simply have no idea what could be causing this issue for you.

Is there any common denominator on those flights where it happened? Did it happen on the same route? Around the same place? Same arrival? Or was it just completely random on different flights with different routes?

Hi Dreamflight767, Currently this is not planned but your feedback has been noted and we'll try to have a look into it at some point in the future if we can find time to make this happen.

Please try to post only one issue per topic. That way it's easier for us to manage different reports. As for the first issue. Can you confirm that you are well below the glide slope when the localizer is captured?

What fps are you getting in sim? Does it ever drop below 18? What if you try to run the sim in minimum settings, does it still happen?

To me this looks a lot like you don't have Prepar3D v5 installed or the simulator intsallation location cannot be found by the installer. The installer looks for the P3D root path through registry so the issue would be there.

Hello XCSWxcsw, First of all it looks like not all your screenshots have loaded correctly. At least I can see just one screenshot that loaded up while 4 others are just corrupted "unknown.png". Could you try to upload them again maybe? Secondly, this issue is something that we know exists but we are not able to reproduce this issue or simply have no idea where to look to fix this right now. Are you able to recreate this issue on this flight consistently? What route did you fly? What CI did you use? How long into the flight this issue happened (any location like x nm from waypoint y)? Did you make any changes in the FMGS when this happened (change in cruise FL or CI for example)? If you are able to recreate it, could you try to send us the log files (Preferably zip the whole Data folder inside the Aerosoft A330 folder and post it here) or try to catch the moment it happens on video. This would be really helpful since we are currently completely relying on customer information with this issue to get better understanding what could be causing this. The testing team is totally unable to recreate it consistently, so we have no idea what is causing this or where to even look from.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Just checked on the latest internal test build. This issue has been fixed and the fix will be shipped on the next update.

A_pilot is absolutely correct. It's not always a quick process when there are multiple moving parts within a single issue like it seems in this case. We are working hard with TFDi trying to locate this issue and get it fixed as soon as possible.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Could you try to download the Microsoft Visual C++ 2019 x86 from this. The version that you have is a bit older than mine and since the crashing module is in SYSTEM32 folder it could well be linked. Please let me know if this doesn't work. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

I tried to recreate this issue by departing out from runway 22R from JFK and starting managed climb to FL370 with CI30. At FL280 I changed the CI to 130 while still in IAS area and the aircraft flew the speed conversion as well perfectly. No problems at all. So this issue remains still as a mystery for us all. I know there could be still some speed related issues but they are all extremely hard to pinpoint. Let's keep an eye on this one and if you or someone here can recreate this, please try to post as much information (what route, any actions you took before this happened, log files, videos) as possible.

It would be great if you could specify the exact aircraft type and also the engine variant. Or does it happen with all the smaller Airbus aircraft? The aircraft should be smooth to operate and I haven't noticed this issue before. Is it on all phases of flight (departure, cruise, approach) and all configurations or just some? Could you take and post a video when this issue is happening. That could maybe give us a better idea what is happening.