Identify controller type in LOG file

[Alhard Horstmann]

Hello, I use the LOG to see what happens when I click on a MSFS aircraft function.

Now I can see a lot of lines, but how can I idenfy which controller or what button is firing ?

here are 2 example lines:

82031 *** EVENT: Cntrl= 67194 (0x0001067a), Param= 2 (0x00000002) FUELSYSTEM_PUMP_ON
82031 *** EVENT: Cntrl= 67193 (0x00010679), Param= 2 (0x00000002) FUELSYSTEM_PUMP_OFF

I am looking for the SAS button in the Westland WASP helicopter. What is the correct binding with FSUIPC7?

[John Dowson]

1 minute ago, Alhard Horstmann said:

I use the LOG to see what happens when I click on a MSFS aircraft function.

Now I can see a lot of lines, but how can I idenfy which controller or what button is firing ?

You can do this by having the logging console window open (Log -> Open Console) and then press the button in the VC and see what event(s) is/are logged. If you see events logged when you are not doing anything, then these are most probably events continually triggered by the aircraft. Best to ignore such events by setting the DontLogThese ini parameter (see Advanced User guide for details).

4 minutes ago, Alhard Horstmann said:

I am looking for the SAS button in the Westland WASP helicopter. What is the correct binding with FSUIPC7?

I don't know (and don't know what "SAS" is!) and as I don't have this I cannot advise. Use logging to see id any events are logged. Also try listing input events and lvars to see if any of those look applicable. As a last resort, you can also inspect the behavior of the switch using MSFS's behavior debugging facilities - see https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ for details on how to do this.

John