IniSteve

logged. thanks!

Hi Bill. Are you using a controller or joystick that might inadvertently be commanding the grear up?

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. We've explained this a few times. With this product, we aren't able to code two separate control configs so LOCK mode has to take priority. (this means legacy will at times have reversed inputs) Should advancements in the sdk allow us to easily convert the xml, we'll look at mirroring the functionality but it's not possible at this time.

Thanks for the feedback. I will pass it onto the animation team and see if it's possible to implement.

As you suspect, that feature in GSX isn't fully compatible just yet. An update showing seated passengers is coming soon according to the GSX changelog.

Michael, the relevance is I am showing the user who is having the issue results from the simulator without any factors that may be inducing lag. I'm not sure why you feel need to make assumptions on my intention or jump to the conclusion that we feel there isn't an issue.

Here is raw video from the sim with input windows shown For 1:1 comparison - No FG, No vsync, sustained fps of >40. Joystick is a TM warthog with zero input curves and no null zone. As you can see there is no discernable input lag. FlightSimulator2024_l8obGlMqfG.mp4

One of your bindings is interacting with the rudders. Confirm it is centered.

Noted and logged.

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 model has changed, therefore, these liveries will need to be fixed by the respective creator. Please reach out to them directly.

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

Hi Tommy, This behaviour is correct to the real aircraft. Please reference the following graphic from the FCOM to better understand the limitations of this system. You can enter 12' and 59" to approximate the local time in Auckland. For values larger than that just inverse from zulu time.

Hi, as Erti mentioned, failure randomization is coming in a follow on update

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!

Hi TFG, Rather than turn to robots who aren't on our team, I invite you to check out the many streamers and youtube creators all over the internet who have showcased it's capability over the last 12+ hours. Hopefully they shed enough light.

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.