These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
I need some help with map switch iniBuild L1011 !
MSFS 2024 – iniBuilds TriStar L-1011
I need to map cockpit switches to an external hardware device.
The developers provide very little information on how to do this. More precisely, the available documentation is extremely limited.
I’ve been using DevMode → Tools → Behaviors for this purpose, and it has worked for me in most cases. However, there are some switches that I can’t get to work this way.
Here’s one example.
The ALARM push-button switch on the Captain’s side (ID: SWITCH_AFCS_CPT_ALERT).
Below is a screenshot and video showing the fully expanded Behaviors tree for this switch
There is a specific issue with this switch (and other similar switches in the L-1011).
When I select “Select for FS control” in FSUIPC for INSTRUMENT_SWITCH_AFCS_CPT_ALERT (or click Execute under Behaviors → Binding(s)), the button briefly moves, as if it were being pressed, and then immediately returns to its original position.
The same thing happens in Mouserect under Behaviors: the Current value instantly jumps to 100% and then immediately drops back to 0%.
However, when I physically click and hold the ALERT button in the cockpit, the Current value in Mouserect increases to 100% and stays at 100% for as long as I hold the button down.
My question is: How can I properly bind this type of momentary push-button switch to an external hardware device via FSUIPC so that it behaves the same way as when I press and hold it with the mouse in the cockpit?
I am away atthe moment and respond fully when I return, so eti e tomorrow afternoon.
But are you sure that is an FS control and not an input event? Could you please list the available input events, and maybe log them as well and see how they change when you press and release the switch. This may be possible by setting an input event to a certain vakue in press, then another on release. But need to see your logs, with correct logging activated. Also looks Like there are some *_PUSH & *_PULL b-vars that could be used via calculator code or a preset. You can maybe try/testthese as well. I can show you how to do that tomorow as well.
In the mean-time, set logging for Input Events and activate the switch in the VC and show me a logfile. Also list the available input events.
Posted by: @fsuipc-support
But are you sure that is an FS control and not an input event?
Sorry! Of course I was wrong—it's an input event.
Posted by: @fsuipc-support
This may be possible by setting an input event to a certain vakue in press, then another on release
That's exactly what I did
Here is the log when the ALERT switch in the VC is pressed and released
Posted by: @fsuipc-support
Also list the available input events
Where is that?
Is that them?
Posted by: @fsuipc-support
Also list the available input events.
I found it—here it is
Posted by: @smn204Here is the log when the ALERT switch in the VC is pressed and release
That is a log extract of when you press your button assigned to the input event. I need to see the log when you press the button in the visual cockpit (VC) so that I can see the input events when you do this:
.Posted by: @smn204
However, when I physically click and hold the ALERT button in the cockpit, the Current value in Mouserect increases to 100% and stays at 100% for as long as I hold the button down.
You can also try sending the button press event on repeat to see if this helps - check the repeat checkbox in the assignment.
You can also try/test the B events. Use the Add-ons->WASM->Execute Calculator code option, and try/test the following calculator code string:
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_PUSH)
to simulate the click and hold, and then
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_RELEASE)
to release. Do they work? If so, you can define your own presets to use that.
May also be worth checking:
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_INC)
and
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_DEC)
to see if they move the switch.
Posted by: @fsuipc-support
I need to see the log when you press the button in the visual cockpit (VC) so that I can see the input events when you do this:
Attached (I pressed and released the ALERT button in VC several times)
These all four commands perform the exact same action—the switch "ALERT” in VC is pressed and released very quickly (in a fraction of a second).
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_PUSH)
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_RELEASE)
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_INC)
1 (>B:INSTRUMENT_SWITCH_AFCS_CPT_ALERT_DEC)