Can confirm, SU4 beta fixes dynamic registration, SU4 beta also fixes this issue with the starship.

Thanks for your reply Mark, I look forward to it!

We're not aware of any missing sounds in FS Traffic, however, the simulator can begin to automatically cull AI aircraft sounds as a performance-saving measure in performance-heavy scenarios. Just so we can be sure that this is the case, could I kindly ask you to raise a support ticket via the following link: https://www.justflight.com/support In the ticket, if you could provide details on the aircraft you observed having no sounds (if there was a particular model), and the airport you were at (and if you were using a third-party version of that airport). Our support team will then be able to attempt to replicate that and take any necessary steps from there. Mark - Just Flight

If they're sitting slightly above idle, that suggests it may be related to the throttle axis sensitivity curves, or it may be related to which control assignment is being used to control the throttles (see a similar thread here: https://community.justflight.com/topic/9025/rj-and-thrustmaster-airbus-throttle?_=1762424953968) I'd recommend having a quick read through that other thread just to see if changing any control assignments fixes this. If you do continue to experience this issue, could I kindly ask you to raise a ticket with Just Flight Support via the following link, and our support team will be best placed to offer any assistance with recommended controller sensitivities/settings: https://www.justflight.com/support Mark - Just Flight

@Black-Square the manual says: NEW Three aircraft in one: Normally Aspirated A36, Turbonormalized B36TC & Turboprop Conversion A36TP. and 5 more mentions of the A36TC model I can't tell by size or appearance. P.S. I apologize for being annoying🫣

Openable windows are quite a trivial thing to add, particularly after a product has been released. Not only do they require significant modelling/texture changes, and a small amount of code to go along with it, but they also require a rework of the sound set to ensure the sounds are all mixed correctly with windows open and closed. In the case of the F28, the project's original scope was set long before openable windows became more common in MSFS, so the feature was never planned. As with a lot of things, it all comes down to the allocation of resources for us. We looked at adding opening windows in the F28 v2 update, but we couldn't justify taking four developers off other projects to add them. Never say never, of course, and we do have this logged on our internal feature request tracker, but there are no plans to add them in the near future. Mark - Just Flight

I am in calm weather, and after landing, the chocks remain set, but external power cannot be attached. via the EFB it indeed disengages after a short moment. While in 2024, I also tried to attach it via the walkaround mode, but while it was possible prior to departure, after arrival it refuses to connect.

Ok, clear. Thank you very much

The nature of the propeller problem was essentially what I expected to find. I believe I have fixed it with the addition of only one line of code. Thanks for pointing it out!

Fixed for the next update.

@Black-Square no problem and thanks for the reply

Heureka (I have found it) Below works, it’s been tested twice in FS2020 Found a way which works, you can keep the over stressing settings on HARD, as I’ve always had. spawn to runway take your little Bonanza back to the parking turn everything OFF start as you would cold & dark, in this case slightly warm & dark takeoff works fine, without crashing ! So the question is (for the Developers to work out) what’s the difference between spawning to the runway…and starting cold & dark ? I’ll leave it here, I can live with extra extra step, no problem. Cheers, Ronnie

Finally, the issue was caused because I tried SU4. I was really not expecting that. Now back to su3. Thanks!

I see that there were mentions of tip-tank transfer in the checklists within the manuals (but not with the in-game checklists). I have removed those now, thank you. The aircraft modeling in the Baron Professional are equipped with integral fuel tanks, which freely flow together, and do not require any pumps to transfer fuel. The same goes for the Turbine Bonanza, which is actually created from a B36TC, which comes from the factory with the Baron's wings and increased fuel capacity. Hope that answers your question!

Ok, the last 5 times I tried it, it wouldn't work. This time I started flight sim to get you that screen shot and it fired right up... I dunno...

Hot-swappable tip-tank and winglet variations, and the ability to remove the radar display unit with the wing radar pod will be added in v1.1, for which you should only have to wait a couple days. Enjoy!

I am well aware of these two failure deficiencies, as they are two of the only areas where I have no taken complete control over the systems to achieve my desired level of accuracy. The former, I have not thought of a good way to do this without overriding the native autopilot, which becomes a near impossibility when dealing with so many different 3rd party developers for GPS units, who also override the native autopilot for their own purposes. The latter is only slightly difficult, because MSFS does not provide a persistent indicated airspeed value (one not affected by the simulator's own sense of icing and blockages, which cause it to go to zero...), and I would worry about trusting my own derived value (that I currently use for sounds) for something as critical as airspeed. I have wanted to tackle the entire genre of pitot/static failures for a while, but the math is fairly difficult to get them real world accurate with all lapse rate and temperature effects (high to low, look out below), and I know that is the first thing people would want to try if I make that kind of realism claim. In short on both issues: It's never as easy as it seems, and sometimes it's an order of magnitude harder than you might even imagine.

@Guenseli I don't have a streamdeck but I see you have the target cabin temp on one of the buttons.. what variable provides that? Edit: Found it: L:var_cabinTemperatureSetPoint

@AlphaEcho I suspect the events I use, are the same events that are listed as Range Zoom IN and Range Zoom OUT in your menu. I do all control binding in external software, so don't know exactly how the input events are shown in the GUI inside MSFS '24. Anyways, we're very off-topic here. I can check later, and post in the MSFS forum with my results!