(1.7.7.0) C172 classic variants with Avidyne IFD550/540

Sim Update 5 Beta | MSFS 2024 Aircraft & Systems
,
1

I have the premium deluxe edition but I can’t find this

Cessna 172 Skyhawk

  • Added C172 classic variants equipped with an Avidyne IFD550/540 rather than the GNS530/430.
Classic Cessna 172 Not Appearing in Menu
Avidyne-gauges in C172 are still missing
2

Me neither

3

I think there’s another thread reporting this bug. Not in this release so far it appears!
Regards

4

I reported it in the survey Sim Update 5 Beta (1.7.7.0) Forum Surveys - #3 by DementedCorn327 but I don’t think there was a dedicated report.

1 Like
5

Is it supposed to be a free aircraft to begin with?

6

@Hasheminia
The Cessna 172 Classic is part of the Deluxe, Premium Deluxe & Aviator editions. Only the G1000 variant is in the Standard edition

1 Like
7

I figured as such. Maybe OP does not have the proper edition.

1 Like
8

I have the aircraft having but when using it it still has the gns ones

1 Like
9

Yes - as reported here and in thw 1.7.7.0 survey, a number of people (including myself) are reporting no variant with the Avidyne IFD550/540 avionics. It would be interesting to hear from anyone who does have the Avidyne IFD550/540, with a screenshot of the configuration page showing the variant & one of the instruments in the cockpit.

6 Likes
10

Is it not tucked away as a livery of the standard version? (Not on beta, just seen a lot of aircraft hidden away like that)

11

@Uzura2203
Not that I’ve seen. I just have 1 “official” and 15 “Flightseeing” liveries for the basic aircraft.

1 Like
12

I get that the G1000-equipped aircraft can be considered an entirely different variant, due to the G1000 being an entirely integrated system.

But a strong suggestion: other, drop-in avionics shouldn’t be considered a separate variant, they should be selectable and hot-swappable in the EFB, similar to how many second and third-party aircraft are managed. Otherwise we’re going to deal with even more clutter in the menu.

5 Likes
13

Still don’t see it in the 1.7.9.0 update or whatever the new one is

2 Likes
14

Continuing the discussion from Sim Update 5 Beta (1.7.7.0) Release Notes - February 20, 2026:

Something new about the Avidyne IFD550/540? Can’t find it in SU5 Beta v1.7.10.0 from 26/03/10.

15

We strongly, strongly recommend against this practice to all developers who will listen. The HTML/JS and instrument system in the sim is very much not designed to be hot-swapped at runtime. We did a rudimentary hack on the GNS to attempt to support hot-swap (which works with varying degrees of success and non-success), but we will not be adding such hacks to any other instruments.

The IFD will not support hot-swap. The sim variant and attachment system in 2024 has been expanded so that developers and community modders don’t need to make separate liveries for each cockpit configuration any longer. So variants are the correct place for this configuration to take place, not the EFB.

2 Likes
16

That’s fair enough. When I have used it in the past, in the JF Arrows for example, it was just to switch to the TDS 750xi anyway. If it had spawned with it, I would not have needed to.

17

This is interesting as the aircraft I have which support it (A2A Comanche, Aerostar, Carenado C210, B55, Got Friends A-32, Wilga, and probably others) have never had issues with it - can I ask what’s at risk by implementing this?

Or am I misunderstanding the question/answer entirely?

1 Like
18

Avionics are massive state machines, but so is the sim. These states must be aligned and properly communicated at various known points. For example, when you load a flight from a specific state, like on the runway vs at a parking spot, there is a bunch of state in FLT files communicated and synchronized. That state may not apply or be nonsensical if the instrument is loaded later.

There are other internal parts of the Coherent engine itself that need synchronization as well, API sessions, etc, that require proper shutdown and init, but that can’t be completed if the instrument is just dropped.

Additionally, for complex integrations like are present between something like the G3X and an external navigator, those require synchronized init and specialized panel.xml and other wiring for each configuration. Changing out portions of the instruments breaks that contract.

For a simple GPS like the GNS folks mostly don’t notice if something doesn’t init exactly as it should. But we always tell developers to please use the variant system, as that is what it is designed for, and Coherent (and the many layers that communicate and operate via it) is very much not.

2 Likes
19

Good to know - I guess I have either limited to simpler systems, aren’t paying enough attention to notice the issues, have gotten very lucky over the last few years, or a mixture of all of those.

I really hope the next iteration of the sim improves upon the “variant” system/UI as what we’ve got is better than what we had, but still results in a lot of extra scrolling.

As an example, the DHC-2 Beaver currently presents the user with twelve variants to scroll through and choose as it has two (2) cabin configurations, two (2) undercarriage configurations, and three (3) avionics configurations. It would be significantly cleaner to have a UI where we pick the aircraft, then select which cabin/undercarriage/avionics options we want through dropdowns for each category.

1 Like
20

Is breaking the “contract” mostly an issue in career mode? I don’t see any of this behavior in free flight with the avionics I use.

If this is the case, I cede the point, however, the selection UI needs a full makeover because at its base, that’s the reason I suggested it in the first place. Loading the aircraft physics in the menu, the messy selection process, etc, makes one pine for a simpler, more streamlined process.