Testing for Event or InputEvent for an action

[DaveSCUSA]

Often when activating a switch or button in a cockpit, the FSUIPC7 Log shows several entries.

An example is a battery switch on activation may show a master battery control event, a toggle bus control event and a "B:Battery" input event. Is there any way to obtain which event was triggered by the switch on.

Or must one test each separately to observe the action?

[John Dowson]

2 hours ago, DaveSCUSA said:

Often when activating a switch or button in a cockpit, the FSUIPC7 Log shows several entries.

An example is a battery switch on activation may show a master battery control event, a toggle bus control event and a "B:Battery" input event. Is there any way to obtain which event was triggered by the switch on.

Or must one test each separately to observe the action?

FSUIPC just reports what events are seen. And this is completely dependent on how the aircraft is implemented.
Usually, when an input event is triggered, this can then send various other events - lvar updates, k-evenrs (standard FS controls), h-var updates, etc.
BUT, the input event may not trigger everything. So there may be some aircraft when you can send an input event and nothing else, and that is sufficient. For other aircraft, maybe the input event (or b-var) only triggers some actions, and you may also need to add a k-var trgger, or an lvar update, or something else.

But this is completely dependent on how the aircraft model is implemented. Some developers/aircraft respect the norms (i.e. an imput event should be sufficient, and the input event code will do everything, including sending necessary k-events, updating lvars, triggering hvars, etc). If badly implemented, you may need to send the Input Event and also perform other actions.

But this is nothing to do with FSUIPC. With FSUIPC, you can log what is happening and then try and replicate that with assignments. I cannot control how an aircraft is implemented, only provide the facilities for users to investigate and determine what to use.

But generally, if an Input Event is available, use that. If that is not sufficient, then investigate. Or look to see if a preset is available.
Presets cover all other control mechanisms (i.e. K-events, lvar updates, hvar updates) apart from input events (or b-vars). So, most things should work with either input events, presets, or a combination of both.

And please understand that FSUIPC only provides access to such things. How they are implemented and used in various aircraft is defined by the aircraft developers, over which I have no control.

 

[DaveSCUSA]

Thank you