IniSteve

Hi, this is due to an issue in how the sim interprets layers with VR. It's not a quick or simple method but the QF folks are looking at how to make it work while not sacrificing performance.

Nothing yet but should have more to share after FS Expo at the end of the month.

Possibly, but I'm going to work one problem at a time 🙂

Something appears to be corrupted in your plan/autosave. I was able to reproduce the issue when loading your save but when I replanned the routing fresh from C&D there was no turn to the right or stall condition induced. Of note was the 430' alt constraint did not auto sequence to the next WP so we'll look into why that happens on certain procedures.

Hi. This is known and logged. Thanks!

We're aware of the move but appreciate the heads up. Once the facility is fully completed, we'll see if it's something we can add in a future update.

There is a manual the aircraft folder located here - ....[YOUR COMMUNITY PATH]\kwikflight-aircraft-hunter\Resources\Documentation We also released a feature showcase the day prior to release -

Yes. Despite the guidnace from FSDT we have found that GSX is not always respecting the filter for 2020 vs 2024 in cfg files. Until it's fixed on their end, you'll need to switch profiles per sim if using the same airport. Nothing to fix on our end as explained above.

Hi. Are you using the correct winglet option for the aircraft?

Hi. I will move this to the proper thread. with respect to your issue, did you update the aircraft in the manager or install fresh?

HI. I need to confirm winwing has actually reached out to us but in the interim we'll take a look and see what we can uncover regarding compatibility.

Not needed, this is enough. We'll take a look and see what's uncovered. Thanks!

logged. thanks!

Hi. GUI issue logged. Time compression has been extensively tested in 2020 so something else may be causing your sim to reset the clock. Are you using any 3rd party ACARS or tracking apps in concert with the 350?

Hi. It seems the timing of inputs was changed inadvertently and should be resolved in today's update. Procedurally, take a beat (half second or so) between clicks to make sure the sim doesn't fail to register the 2nd one as a unique event.

Hi. We'll look into this and report back.

Route info please.

Hi. Thanks for your report and the feedback. We are investigating these issues. With respect to AP disconnect the resolution rn is to deliberately press the AP disconnect button twice. If you go too fast, it won't always register the second click (we believe something in the core logic has changed and are trying to determine what that is)

Not sure if there is an answer that pleases here but I can assure you there is no "scam." While we are obviously very busy, we will continue to investigate issues with FS2024 and our products. By and large the feedback has been positive with regards to performance but rather than deflect, let's figure out what your core issue is. Have you tried starting with a fresh community folder that contains no other addons apart from the A300?

Hi Mike, I'm sure you've seen a number of the issues resolved in the past few updates, but specifically wanted to follow up to confirm the emergency descent logic is resolved and working as intended. Thanks again for your reports.

Hi. This is resolved as of 1.0.5.

Hi. The sound you're hearing is that of the nosewheel strut fully extending as the aircraft lifts off the ground.

Hi. Under USER EXPERIENCE in the assistance options menu, turn off "aerodynamic visualization"

Hi. We'll look into this and see what our side pulls. Thanks!

The freezing on exit is something we're aware of and have communicated (quite exhaustively) over the past 24 hours since release. It relates to networking and will affect apps like FSUIPC/vpilot/Simbrief/etc. Essentially, anything that uses simconnect or the networking api. We are trying to find a workaround but in the mean time the only way to fully exit the sim is to kill the process via task manager. While this may not be the most elegant solution, we felt it was a better alternative to limiting the ability to use these applications with the A300.