An event list like ‘brakes_right’ along with event feedback values to allow programming into devices like StreamDeck. A good percentage of those in FS2020 don’t work in FS2024.
1 Like
Voted (for what it’s worth…)
I’ve found that many events are mapped to differing variables in different aircraft. For example: Landing lights might be ‘LVAR:Lights_Landing’ in one plane, and ‘SIMCONNECT:Light_Potentiometer_10’ in another. Then there’s the problem with control code and animation events being different. Some 3rd Party devs use B: events to drive both, and that’s a welcome evolution indeed.
Some offer event documentation to one degree or another. It’s up to the individual devs to decide how much. But if a plane is in the Marketplace (or part of the core sim, such documentaion should be mandatory.
We’re allowed to map them in the sim’s UI using generic descriptions, but there’s zero documentation of the underlying code. It was this way in FS2020, and nothing has changed. I’d love it if developers (Asobo, along with every 3rd Party dev whose aircraft have been made available on the Marketplace) were required to publish a complete data variable list for those of us who use tools like SPAD, A&O, Mobiflight to program our peripherals (like Streamdecks.)
But we’re considered “edge case” or “fringe users” and I’m afraid that no one at Microsobo really cares about the collaborative work we have to do to drill into the code in order to fully enjoy our sim cockpits. It may be an ROI situation, but that doesn’t make it any less frustrating.
1 Like
This one?
1 Like
That’s very helpful.
But I think it’s only relevant to Asobo aircraft, not for 3rd Party aircraft that are only available on the Marketplace (FSReborn FSR500 for example.) I’d like to see it be mandatory for those devs to publish a similar document for their aircraft, since they often use custom events that aren’t in the SDK.