My observations (testing some but not all aircraft, so might not be universal)

In 2020 Sim, AAO mapped IE: events working for aircraft I have tested

In 2024 Sim, IE: working for native 2024 aircraft but not for legacy (2020) aircraft. Events are listed in AAO window but have no action when used

Is this something that Asobo is blocking?  Obviously events have changed in the new sim.  I see new file events.xml in native builds.

Just thought I would mention in case you saw any chance of improvement in next version...

Because I know a lot of users are trying to use their purchased 2020 aircraft in 2024.

And using IE: seems a quick way to build control map when working well.

Also I have not yet found a page explaining how Asobo compiler comes up with IE: event names.

12 minutes ago, JJBZ0053 said:

My observations (testing some but not all aircraft, so might not be universal)

In 2020 Sim, AAO mapped IE: events working for aircraft I have tested

In 2024 Sim, IE: working for native 2024 aircraft but not for legacy (2020) aircraft. Events are listed in AAO window but have no action when used

Is this something that Asobo is blocking?  Obviously events have changed in the new sim.  I see new file events.xml in native builds.

Just thought I would mention in case you saw any chance of improvement in next version...

Because I know a lot of users are trying to use their purchased 2020 aircraft in 2024.

And using IE: seems a quick way to build control map when working well.

Also I have not yet found a page explaining how Asobo compiler comes up with IE: event names.

Any concrete examples? I've only heard of this starting with the latest beta of MSFS 2024. Some IEs (but not all) stopped working for legacy aircraft. 
Also, be mindful that IEs require the correct value to function, the name by itself is not enough.

Example: IE:AS1000_PFD_1_COM_SWAP
This is no longer working in legacy G1000 aircraft since the latest FS24 beta. One has to work around it using BVars
1·(>B:AS1000_PFD_1_COM_Swap_Push)·1·(>B:AS1000_PFD_1_COM_Swap_Release)·

On the other hand IE:AS1000_PFD_1_COM_SWAP is still working normally.

To me this looks like a bug in MSFS 2024. Then again, when I looked into the Library today (for the first time ever), most of these aircraft had warnings that they are not "developer approved" or something. So I wouldn't expect them to work either. Possibly Asobo changed something in the IE configuration that the old aircraft no longer match. "Planned obsolescence" ?

Edited March 2, 20251 yr by Lorby_SI

In place of "Planned obsolescence"  I would submit "Accidental Aggravation" 

Their support of legacy models has be uneven although SU1 Beta helps more than it hurts.
 

On 3/5/2025 at 2:52 PM, JJBZ0053 said:

In place of "Planned obsolescence"  I would submit "Accidental Aggravation" 

Their support of legacy models has be uneven although SU1 Beta helps more than it hurts.
 

I noticed the same problems with IEs in native models too. I looked at the MSFS developer forum today and was surprised to find no mention of this. So I posted my own report, we'll see what happens.