You don't need to press the test button, no. Follow the checklist, make sure the four gyro button are on. Then you have the radio master switch, AP master, and EFIS master switch. For takeoff, in low winds you can set the rudder between center and TO notch. In winds greater than 7-8 knots, put the rudder to TO line. You don't need to set aileron trim. If everything is setup correctly, the plane will maintain a heading with minimal pull to the left. Adjust the rudder trim to account for any pull to the left. The slower you are, the more rudder trim you will need, and as you build speed you will need to center the rudder. Watch the ball right below the attitude indicator/EFIS, and keep it centered. If the plane is trimmed, the plane will only pull a very little, and that can be countered with aileron if needed. I never use aileron trim however. With AP on, the plane will hold a heading or NAV/GPS route just fine, even if the ball isn't centered. You're just introducing more drag by not centering it. The only thing I can think of is that perhaps you have some assistance setting on that are interfering with the plane. Yes, the plane does pull more than others I've used, but it is a normal amount of pull and certainly not uncontrollable or inappropriate. Make sure these are on and the trim is set to TO, or close to it (it's centered here). The elevator trim works best at the bottom of the green for takeoff: [image: b0207051-1f05-4ddf-818d-4d294474effd.jpg]

Great news, many thanks for the update.

It supposed to save all the switches and buttons between sessions but sometimes it can mess up the plane. When this happens the only solution is to start with default C&D panel state. Here is another example https://community.justflight.com/topic/7205/my-yd-light-is-on

Lots of users complaining about parking brake issues in MS 2024 with different planes. Turns out that SU3 in many cases has caused additional controller bindings to be added, so look out for those.

Okay I use SI instead of the ingame ATC, so no problem. Good to know, didn’t saw that option in the EFB

@Delta558 No worries, have fun! I investigated it a bit further in the meantime. The trim tab seems to have a lot more impact on the overall lift coefficient than the elevator itself - which is odd to me. I tried to map my joystick to the trim axis and the trim to the elevator axis and that actually gave me realistic control over it in slow flight (looks very funny to steer that thing but only the trim tab moves). Can you try landing that thing without trimming it, because that seems to be the core of my problem - i.e. without trim, no slow flight possible because elevator alone cannot create enough lift with that low power setting.

Thank you very much to all.

@SebAvi Indeed, this is why I have not adopted all the pilot/copilot model visibility features that I had in MSFS 2020, or passenger model features that are available in MSFS 2024. We have no independent control over the visibility, dynamic position, rotation, or scale of the new characters, which leave them horribly jammed into the cockpit, or even through the cockpit, as you have probably seen in other aircraft. Unfortunately, there is also no way to use the MSFS 2020 character system without being in compatibility mode for MSFS 2020 aircraft, which restricts us from using all he modern features of a MSFS 2024 aircraft. This has been the reality of developing for MSFS 2024 in so many aspects.

A lot of aircraft are simply not working in SU4 beta at the moment - I've seen development work and testing explicitly having to stay on SU3.

Is there the potential to give the users the ability to customise avionics outside of the simulator by choosing just one for that aircraft, just like the possibility to create a turbocharged, non-tip tanks entry by copying a folder and modifying a textual parameter?

For my part, I felt that the wind had an excessive effect on the aircraft even though it was below 5 knots. However, my approach speed was slightly insufficient, which may have amplified that impression.

Fingers crossed we hear something. I'm surprised on the lack of reaction.

Hey again! I've evolved. Went to SPAD, and following @MikeyFlyz variables, got it working. If I figure out the ALT in ALT HOLD bit I'll let you know. This is quickly becoming my most studied aircraft. Thanks @Black-Square for sitting with all those YTers to show off the intricacies.

No luck, unfortunately, but the help is appreciated. Hopefully Asobo will see the light, soon. Thanks!

I manged to get it working somehow reliably two times. I disabled my VPN as I've read in another forum that State Saving is actually saved onto Microsoft's servers (truly horrible choice), so I figured NordVPN might be a problem. The same post also told about the importance of choosing the same livery, as SS is tied to that also. This is not on the manual. I noticed that sometimes the livery is pre-selected, some other times it reverts back to the default one. In the first case, I've found it's good to actually select another livery, then select the previous one manually, and some of the variables are recalled: engine health, active failures, fuel on board, windowed open, cabin thermometer. The rest is always reset (including the radios).

Thank you! I think I must have been over complicating things and using increase/decrease as the operation, and trying every which way...

I stick to medium, personally. "Realistic" is absolutely insane and exaggerates way too much, especially on approaches with light or calm winds. Medium is still a bit heavy but it's more manageable without wrestling with the yoke and pedals. I would speculate that "realistic" works better with heavies but I don't fly many airliners in sim. I've noticed less an effect with the greater inertia in similar conditions, so I picked the middle ground, if even medium feels a bit too strong.

I think it must be the navdata for that particular airport. Possibly the third party addon messing with it. When I tried a different airport (KSRQ) it worked just fine. The SID from KATL also worked just fine in both flight plans.

@Black-Square said in 1997 realism option – disable VLF/Omega: When they were updated with GPS, most of the screens relating to OMEGA were just removed, as were references to the system, such as on the "Update VLF from FMS" I think that would be the way to go if you were to do a “modern” variant without Omega. But there is a lot of code (I’ve looked) in the CDU and MFD JavaScripts that would need to either be modified for a tablet enable or removed (and tested). If that’s outside @Black-Square’s scope of work, perhaps an enterprising modder will take it on.