Caravan Professional

If you're seeing the arrows, then you are using legacy mode, but there is no need to switch control methods. Some of my users prefer legacy mode, as it's a fast way to remove the blue control highlighting. I think about it like this: You push the trim wheels in the direction you want the aircraft to go. So, for the pitch trim, pushing the wheel forward/away from you pitches the nose down. Pushing the rudder trim wheel to the right yaws the nose to the right.

@Black-Square Woooow haha never looked up there. Also the transponder function is a really cool one I didnt know about Identifying icing conditions and setting up the TAS now possible, thank you

no ......... you are right, thanks

@Buzz That seems to have fixed the issue. Will keep testing. Thanks!

I wanted to update the post in case anyone else needs this: Decrease: (L:var_CabinTemperatureKnob, number) ++ 100 min (>L:var_CabinTemperatureKnob, number) Increase: (L:var_CabinTemperatureKnob, number) -- 50 max (>L:var_CabinTemperatureKnob, number)

@MiRexer A deadzone doesn't fit this case. It only happens when braking and not because of the rudder. Normal taxi is absolutely fine. And under braking braking axis are more than 0. But I'll try anyways

@HobAnagerik Oh, we've tried... Ours is the last request in February with no response. I'll see if we can elevate it again. Also, if you set the light softness to a very big number, you can create some really wild effects.

Forgive me if this seems too obvious, but have you checked the engine condition on the tablet interface?

Thank you everyone for viewing this post. Much appreciated! Here's a screenshot of a Default Caravan, just to show how the Dynamic Registration appears in a Multiplayer MSFS 2020 session. I can't fault Black Square at all apart from this detail, this is a superb model! Dave.[image: f12bdd89-660f-45a7-80ee-3946b2f2f7b0.png]

@Black-Square Sorry I missed your reply to this... while waiting for my new member "You're post needs to be checked by an admin" I didn't see you replied. Many thanks. Brett

@Jiblet These numbers are just like FSUIPC 16383 to -16383. Seems like I will have to pull it back out of the "Please go away and die cuz this should be included in the sim closet." Now... where did I leave my PhD on how to configure FSUIPC?

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

@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.

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

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.