MSFS 2024 I have similar problems -> the tablet are not saved after a flight. Engine Conditions is always 0% and Pax & Baggagee + Fuel are same amount as I start a new flight. I need repair engine every time before I can start the engine. There was everything ok as I use simupdate 3 but during beta 4 the problems started. Yestarday I made a test flight after official SU 4 was done. Engine was broken and I repaired it. Then I left from airport and found that tail of the aircraft was very low position, trim done nothing and speed was about 100 althoug I set V/S a few hunred feet/min. I reached my target 10 000 feet very slowly but after that all works as they usually do - no problems. Any idea? Thank You Rolf

Could be a largest project like a king air family. C90 or F90 , B200 and B350. Big bundle. ^^

Unfortunately SU4 has introduced some issues for aircraft that use WASM gauges, including ours. At the moment the only reliable solution appears to be to click START FLIGHT, then BACK once the loading screen has appeared, and then START FLIGHT again.

Unfortunately SU4 has introduced some issues for aircraft that use WASM gauges, including ours. At the moment the only reliable solution appears to be to click START FLIGHT, then BACK once the loading screen has appeared, and then START FLIGHT again.

Unfortunately SU4 has introduced some issues for aircraft that use WASM gauges, including ours. At the moment the only reliable solution appears to be to click START FLIGHT, then BACK once the loading screen has appeared, and then START FLIGHT again.

Turbulence is a very tricky thing with flight sims. I don't entirely doubt that "realistic" might produce realistic accelerations, but somehow aircraft control and visual concentration seem easier in the real world in moderate turbulence than in flight sim. Thanks for the kind words. I'm glad to hear that you're enjoying them

I've already fixed this for the next update. Thanks for letting me know, though!

You mentioned the animation - and that's why I mentioned the above. No, mine goes right into feather on the ground. I made a video for you: https://horizon.meta.com/shares/NGFE6yzx9bG4e91Ak8Coi2uXWZn8IJ

I found L:var_CorrectedAlternatorAmps_L and _R, using SPAD.neXt. I did take time to review the documentation, did not see these but then after reviewing your note above I thought to bring them up in SPAD. I now have an operational Air Mgr instrument displaying ALT LOAD and BUS VOLTS. It checks other variables to confirm that the Battery Master and the corresponding Alternators are online. Thanks

[image: 66335820-25ca-427d-922a-8d200d1eec34.png] I did also see TRU1 taking the brunt of the starting power compared to TRU2, I'm not sure if they should have approximately the same load or not.

In what circumstances exactly?

Espero que tenha mais sorte em encontrar uma resposta na secção do PA-28 deste fórum. Só queria garantir que a sua mensagem não se perdesse por aqui. [Google Translate]

That is a purposeful choice that myself and some other developers have taken. The way the MSFS rendering engine works, objects spinning at high speed will develop a fuzzy and jittering halo around them. To me, this is infinitely more distracting to a real world pilot than the static spinner with a blurred material. I appreciate the feedback, and if the majority of the community says they prefer the way it is in the default aircraft, then I will reconsider my opinion, as I always want as many of my users to be happy as possible.

I've seen a couple reports of this in MSFS 2024 with several different aircraft. To the best we've been able to determine, there is some residual payload that it left in the payload interface between sessions. I completely believe this, because MSFS 2024 retains many variables and states from previous sessions, which make debugging and switching aircraft on the fly very difficult for us developers. Try applying a new payload from the EFB payload interface and see if that helps. Otherwise, hopefully someone else who has seen this before and fixed it might chime in.

Ok sorry, the tailplane trim and indicator are working. But EXTREMELY slow! I have 'Trim Sensitivity' set to maximum in the tablet. I had to hold the trim button for 4 MINUTES to trim from full nose down to full nose up! Instead of 4 seconds, as stated in the manual. The trim range is wrong (backwards): Manual says +3/-5 degrees. I got 5 degrees nose up and 3 degrees nose down. Either the manual or the plane is wrong. A positive elevator trim means nose up.

okay good to know.

Well yes, the option is disabled otherwise. Originally it was removed entirely, but after some people were able to force it to work pre-SU4, Nick put the option in for those who wanted to tinker with it. At some point I would imagine that will be patched out and it will be enabled permanently.