Closed omrygin closed 4 years ago
See #597
The tl;dr here is that this is really out of our control at the moment. The simvars we introduce for various buttons are really more for our internal use, but not because we want it that way. If we knew of a way we could expose them over simconnect we would.
I'm going to close this issue since we can't really do much right now. If anyone knows of a method we could use to expose simvars then feel free to comment or open a new issue.
Hi,
I've found a thread in FSDeveloper about this subject https://www.fsdeveloper.com/forum/threads/simconnect-accessing-local-variables.448704/
from what I understood, currently it's not easy to expose custom simvar
It seems as some variables are exposed. How can that be? Here's what I found using spad.next:
Those are default SimVars.
Specific commands (example: PTU button ON/OFF) can't be exposed from default SimVars. But for your initial request @omrygin I think it's possible to enable/disable smoke sign & seat belts sign by using default SimVars. A32NX must use these simvars:
CABIN_SEATBELTS_ALERT_SWITCH CABIN_NO_SMOKING_ALERT_SWITCH
Is your feature request related to a problem? Please describe.
FSUIPC not recognizing switch toggling of smoke sign, seat belts, emergency exists etc.
Describe the feature you'd like to see implemented
For interfacing with e.g. Arduino to make home cockpits, one needs these EventIDs to bind them to switches on the board.
References
Additional context
Discord username (if different from GitHub): omryg