@M1ke360 I can atest the beta itself was more stable in many areas prior to Public, for me at least. I'm not shocked anymore at when things break after Microsoft hits the big red "GO" button.

@Rhinozherous said in Possible GTN650 integration?: Soooo, is a GTN650 integration still a thing? Unfortunately, no, at least not by me.

Sunset flight Dubai to Abu Dhabi [image: 53bcfad6-48ec-4586-9309-13eb6c88e5db.jpg] [image: c8c79fff-7e0b-4444-aac4-17e59e3010a7.jpg] [image: ac843f41-1021-4025-8073-2d810f6941a9.jpg] [image: bbef4dae-1ec1-4ae0-abfd-670771c94481.jpg] [image: c3826248-b0c6-49cd-b406-840775d3f382.jpg] [image: 0ad25897-2077-41c0-9eb6-77766a3c3171.jpg] [image: f91ee82d-5930-4c12-892b-1c8bae67b523.jpg] [image: e9a4836d-a051-41b5-8f4b-7c58c1611ace.jpg] [image: 727acdc8-9023-450a-948e-783a5eeed3e1.jpg] [image: c592d63a-bfba-418a-acef-08b0bb541976.jpg]

Thank you for your swift reaction. I have found the problem… it was the Airbus quadrant that caused the problem. When I set the start switches to off, the problems were gone. No lights in the annunciation panel. Still strange is the red master warning light. I really have no clue what is going on . Will look further in to it (unless you have a hint?)

I had something like this happen to me the first time as well. It was extactly on the IAF of the approach (LJLJ ILS30 via DOL) while on AP. When entering the STAR into the FMC, I already entered DOL before selecting the approach, so could it be that the waypoint was in the FMC twice (manually + as approach transition) and it confused the AP?

To confirm, yes it works very well.

@Martyn to be fair, the changelog lists "Added new, modern EFB tablet model" as version-independent, and the 146 got EFB updates in 2020 as well, so if similar communication went out to stores, I can see how that would cause confusion. I was looking for the 2020 update after getting the first-party communication.

Unfortunately we've had to react very quickly to issues that were introduced by MSFS 2024 SU4, updating our entire fleet of aircraft a couple of times in a short period, for both Marketplace and non-Marketplace, PC and Xbox. That's all happened at the same time as a lot of the team signing off for Christmas, so we might be a bit slower than usual at updating changelogs and posting here.

Does the image show up if you overwrite one of the existing ones, e.g. Paper_chart_1.png, without making any other changes to the ini file?

@KAPA-Flyer September is when xbox gets the 737-700 Id still be waiting for the crj by then too

@PilotTumper As far as I’m aware, we can’t disable dynamic registrations on Starship (on Xbox at least).

I have the same behaviour. MSFS 2024 with BeyondATC

Just updated to a version 1.5. Uninstalled previous one, restarted the PC. Runs just fine. Hmm you may have some other stuff conflicting...? Not sure.

Any news for the marketplace? The Dukes, Starship…. Would be nice for Christmas…. One can dream…

Chill, bro There is a general bug in MSFS: Button trim speed depends on FPS for all planes. Measure trim time (0-100% on the HUD), then enable frame limiter and measure again! It's different, reverse proportiknal with fps. This is true FOR ALL Planes! This is dumb, it should depend on the time duration the button was pressed, independent of FPS! So maybe the only way for the JustFlight guys to make a usable trim button was to make the trim very sensitive, so it can be trimmed in a reasonable time. As a side effect the tailplane position indicator cannot be used to check trim state, we need to enable "hud in cocplkpit" and then you can checkthe 0% trim before takeoff. And God forbid, use an axis contrlol for pitch trim like the saitel trim.whreel. move 1 percent (few mm) and it's at full trim. Move 10% plane stalls/spins/disintegrates!

@Voice-of-Reason @Chotter hello! Any updates on manual or plane itself please? Thanks

I have SBP and SZP and they work fine in 2024 via backward compatibility, save for LoD issues on certain assets within SZP.