@Black-Square, no, I have a Bravo but all buttons are unmapped because all buttons and switches are managed by Stream Deck. I've double checked it anyway.

Interesting the patch notes say it required the F28 to work; I don't have it and it worked for me.

Hmmm, just had the same "bump & fly 50m forward" after completing GSX pushback. The brakes are OK though

It is expected behaviour that the F28 should be susceptible to floating when entering the ground effect. The F28 has a low wing, much lower than most conventional aircraft due to the lack of engines, and it also has a very thick wing that is designed to generate lots of lift at low altitudes. Combine both of those factors with an approach speed which is similar to more conventional airliners, and it's likely that the aircraft will be rather susceptible to ground effect. If an approach is carried out following standard procedures, it is standard to extend the speedbrake as the aircraft crosses the runway threshold (there is a callout for this in the F28 Professional). When the speedbrake is deployed, the extra drag will slow the aircraft down to the VREF speed, thus reducing any tendency to float. Upon touchdown, the liftdumpers will automatically deploy (if armed), which are used to spoil any remaining lift that is being generated by the wings. The act of extending the speedbrake during the final approach is something unique to some of the aircraft we develop (F28/146/RJ), and does differ from the more conventional aircraft, but once you start doing it a few times, it starts becoming second nature. There are few settings in the simulator that we may recommend changing that could improve your experience with both points you raise: We recommend using linear sensitivity curves for all of our aircraft. This is what the flight models in our aircraft were developed around, and provides consistent control throughout the control range. The sensitivity curve can be adjusted in MSFS 2024 Settings > Control > then click on the cog icon next to your joystick/yoke/controller > Hardware Settings. We recommend using the "Low" turbulence setting. Based on various feedback we receive from real-world pilots on our testing teams, the "Medium" and "Realistic" turbulence settings tend to produce overly aggressive wind effects in the simulator. Therefore, reducing this setting to "Low" will provide a more realistic experience, and may reduce any wind effects/ground effect caused when low to the terrain. The turbulence setting can be found at MSFS 2024 Settings > Assistances > Turbulence. Hope that helps. Mark - Just Flight

I would really appreciate this too. It is such a huge step up in immersion, no more fiddling with the mouse and loosing sight on your instruments or the exterior. Thanks in advance, Hans.

Thanks for reporting this. This is a known issue, and we do have a fix already implemented for our other airliners that will make its way into the RJ in the next update. Mark - Just Flight

@CoolGunS said in Personalizing Starship: Lol this was funny, your transponder codes suggest you are expecting radio failures, terrorists and major emergencies. Nope, no terrorism, that's code 7500. Since afaik there are no permanently assigned transponder codes besides the two "squawk VFRs" and the three 7xxx codes, it seems logical to store those in the presets. I left out 7500 since in a GA turboprop, I figure the risk of a comm failure or emergency is greater than an act of terrorism, and having the two VFR codes is just convenient. What would you store there?

You can find almost all of the hardware inputs in the "Hardware Inputs & Outputs" section of the manual. For the autopilot, you will find the standard native bindings under the "Instrument Events" heading: K:AP_PANEL_HEADING_HOLD K:AP_NAV1_HOLD K:AP_APR_HOLD K:AP_BC_HOLD K:AP_ALT_HOLD

There's very little custom or unusual that I'm doing with the parking brake, so it really should behave like any other aircraft in the simulator. I assume you've tried this with other planes? Despite you already searching for control bindings, my best guess is still that you might have the brake axis bound to hardware, because a toe brake signal from hardware will override the parking brake in MSFS.

Hey thanks for the response I’m sorry I didn’t mean the animated character laps but I meant seat belts for the back seat

That's it. Thank you so much!

I'll try some of the others. I'm using the pms50 gtn750

Ok thanks i'll Look

Update 2: all is well, no issues. It could well have been user error, since the "Master Radio" switches have to be on for 60 seconds.

Indeed! The TDS developer was actually nice enough to add that at my request! Perhaps others requested it too, but it still made me feel special while we were discussing how it would be implemented Yes, I will add this to the TBM for the next update after SU4.

@jmarkows Oh. Very much sorry! I just copied without seeing what i got ! That was the PL REV! I sincerely hope i did not mess things up for anyone.. [image: 62c96042-c204-43fe-9d71-6c82006a6d27.png]

said in ND Data and Alt hold small bugs: @awde Looks like the standard reply should have been sent out which is basically "we will log these issues and pass them to the dev team". This was done but someone probably forgot to reply. Apologies for that. Meanwhile, the dev team is aware and will be looking at what's possible to resolve in a future update(s). Thanks for passing it on.

@Outermarker and @hangar_101 Thanks chaps for your wisdom regarding the Asobo tablet - I wasn't aware it could was integrated as a 3D device. Having it and the Black Square tablet combined in the cockpit is sounding like a great idea