@Mark said in Elevator trim not working: I have just tested this and I am seeing the tail plan position indicator move between +5 and -3 by triggering the elevator trim assignments This is the expected behaviour. Regardless of flight model. The manual still states +3 and -5 degrees tail plane trim. The tail plane indicator should move even when trimmed on the ground because its offset is changed, no aerodynamic trimming with tabs. Me (today) and @jaspar11 (2 years ago) are getting only -0.5 degrees and 0.5 degrees movement on the indicator. That is half a mark. Barely visible even at full trim. How to check that trim is neutral befor take off, as the manual requires? We can't

Ah ok, so that's how it ended up in the manual. Thanks Mark.

@GeographicalInvert Thank you for the kind offer. Could I ask you to open a ticket with Just Flight Support via the following link and send any reference material you have to our support team? https://www.justflight.com/support That will be the best way for us to receive any reference material, and it'll then make its way back to the relevant development team. Mark - Just Flight

The direction of the rain on the cockpit windows is linked to airspeed. If you're sitting at a gate with a fairly strong headwind, it is possible that the airspeed may exceed the threshold for raindrops to change direction. Mark - Just Flight

Yes, depending on the MSFS Traffic settings, MSFS could be generating online/offline traffic in addition to the traffic generated by the FS Traffic module. To ensure that FS Traffic is the only source of traffic generation in the simulator, we would recommend double-checking that the MSFS Traffic settings match those in the Quick Start Guide on pages 8 and 9 of the FS Traffic manual: https://downloads.justflight.com/products/JFF003616/FSTraffic_MSFS_manual.pdf Mark - Just Flight

The locked cockpit seats are intentional logic in the MSFS 2024 versions of the F28 to work around a simulator limitation. See point 5 in the following FAQ: https://support.justflight.com/en/support/solutions/articles/17000145497-f28-professional-msfs-2024-known-limitations Thanks for the feedback regarding noise reduction/headphone option. Although nothing is planned at the moment, we have added that to our internal feature request tracker for consideration in a future update. Mark - Just Flight

Perfect, that worked a treat. Thank you!! My Stream Deck+ now accurately shows the ARM state.

I think is something with the Sim itself, This happens also with the PA-28 and the SWS pc-12. Im moving the Heading Bug and suddenly right before arriving to the hdg i want it jumps straight like 40 more degrees. so I have slowly go back.. Same thing happens with the CRS Bug.

@Black-Square Ok, great. Is it too late to be considered for some maintenance?

@gustavpicora Have you tried toggling the "Tablet VR Static Position" setting on the options page? That's roughly where I put it in that mode, and I try to cover as little of the instrument panel as possible.

I mean the boot animation in FS2020.

Oh the map light, perfect, thanks!

It's a shame I love this plane and mostly fly with radio navigation but the behavior when catching/flying on radials is really bad, it's oscillating and overshooting a lot even in easy situations.

I see. I'm actually among those (highly!) grateful for your implementation of the door behavior. The forced entry/exit is certainly not desired, to say the least.

@Black-Square after first frustration, the software engineer in me kicked in and i made it work. I was able configure every possible/available switch/button on my alpha/bravo. I will check the anunciador lights later, but i dont think is necessary. I will also check the virtual axis of the beta range for the tbm-850 and bonanza. Im not sure is even possible for the bravo quadrant since is my understanding the bravo physically bellow the idle detent has no actual axis input. I wonder why there is such range under the idle detent then. Whats the purpouse.

If by "bug" you mean a typo in the checklist, then yes. It's fixed now.

Such a simple fix, yet it required a find-and-replace across 12 files. All done