@Jiblet Thanks for all that you are doing as well on this... much appreciated. I didn't hear from my contact at VF, so very happy that you did, but a little disappointing their reply was "umm-humm we'll see" not very encouraging. Because I am not fully getting it thru my head all the way, what would need to happen if we take the other route, and not use VFHub? I have always been confused why MSFS and our throttles have to have some axis reversed and others we don't, especially when looking at the windows calibration from control panel... since all 6 axis simply give a value of 0 to 4096. Is M$ the one to blame for things also being screwy there? I think I now understand though why sometimes axis work full range and other times they don't based on you point about values. Perhaps it's time to admit the purchase mistake, Ebay them off to someone else to have fun with and look for something new.

I retested and it works definitely. The key is to setup "Control AP Pitch with Hardware Events" in the tablet. I seems to me that this setting does not stay ON in the next flight.

@JakeBunny This is exactly what I tried to explain that you might be experiencing above. The issue is that the water rudders may appear to be up, and the handling in the cockpit is in the correct position, but the invisible water rudders in the physics simulation are still down. I'm still not sure what steering tiller input you're using (perhaps I'm just unfamiliar with this hardware input), but it's likely that it's turning the invisible water rudders. Here is how I worded it in the changelog, just for different phrasing: The water rudder may have invisibly failed to extend or retract in MSFS 2024 due to an undocumented change. Previously, users may have experienced a perceived lack of water rudder authority, or perceived abundance of aerodynamic rudder authority, depending on how the aircraft was loaded. If you wanted to test this to confirm my suspicion, you could copy these two lines of code, replacing the corresponding "point.15", and "point.19" entries in the amphibian's flight_model.cfg: point.15 = 5, -33.20, -5.33, -4.00, 2500, 0, 0.75, 40, 0.30, 2.5, 0.85, 0.01, 0.01, 8, 200, 200, 1 point.19 = 5, -33.20, 5.33, -4.00, 2500, 0, 0.75, 40, 0.30, 2.5, 0.85, 0.01, 0.01, 8, 200, 200, 1

Good catch. Fixed for the next update.

What is considered "short final" to you? Can you record a video showing the issue so it can be reproduced?

@Black-Square If I ever make a ton of money I'll buy my way into Asobo and start flipping over tables until it's fixed (amongst other more critical issues). For now we just have to be happy with what we have which begrudgingly is better than we've ever had before. It's almost more frustrating being so close to perfect and seeing no movement on issues that seem to pale in complexity when compared to everything else the sim can do.

@Black-Square Not sure if you can do anything about this, but this was Matts reply to another user regarding the same issue 2 years ago... I will probably mention in the A2A forums as well pending your response (if you have time to reply that is...). I don't really see how the AUX page not functioning can be an aircraft issue. [image: 03abf688-2816-47e1-a286-6a270847e0db.png]

I am version 581.8 with no issues and am not in any rush to update due to only having a terrible experiences... Next GPU will definitely be red for the foreseeable future.

another +1 for very good to know

@BeginnerPilotDK You can definitely upload images in forum. This is a known bug with aircraft that support visible pax unfortunately.

When my cabin gets all stinky because all the jet a fumes I'm blaming yall On a real note yea that would be a good idea

https://community.justflight.com/topic/10288/fuel-flow-guage

The Amphibian version uses a longer path than the Passenger version. Deleting folders shouldn’t do anything to the registry, so I’m not sure what happened there. We would not recommend manually deleting anything though - use the uninstall option in Installed Apps to remove any files or folders. Like you say, deleting the Custom File natal option should allow you to get around the long path issue.

I have a similar issue and raised a support ticket. For me it only affects the amphibious version. The passenger version installed perfectly fine. I suspect the installer is having trouble finding files that are not included with the amhipious version. Even having long paths enables in Windows doesn'y prevent this error.

@batkizoltan Just to let you know... Even without the patch I can confirm the following: I made several flights with her flying from Wichita in Kansas, USA to Friedrichshafen in Germany. Due to the range restrictions of the airplane I took the "northern route" crossing Canada and flying over Greenland to Iceland and UK (several hops / flights). I was able to tackle severe storms with very low temperatures (sometimes manually because the AP, realistically, couldn't manage any more) and I also think I had several times icing effects. However, I was always able to manage without crash... and I didn't care that much about the weather in advance ;-). The only issue I had was the cabin temperature (but this is another thread and fix is coming up). Here's what I did (please be aware I am no real pilot): 1.) Avoid moist air, namely clouds... Icing equipment shouldn't be an excuse to take needles risks. Of course many times I was not able to outclimb the clouds, etc. Then you have to rely on your Anti-ICE defenses. 2.) Use the Bypass handle if any Clouds or FOD 3.) Bleed Air always on while in climb and cruise (not for Take off and Landing !) ... and in order not to crash ... 4.) If I had any icing on the cockpit window I took the windshield and prop heat to on. But if there was any weather change (or I was coming out of the clouds)... I turned them off again... In doing so I "ensured" that I can see the icing conditions if they happen on my cockpit window and wings and reapply the procedure.