DaveSCUSA

It appears the thread that one can place a potential Beta problem has been closed. 270968 InputEvent received: 'PRESET_FADEC', Value=0.000000 (param='') Once an aircraft (DA62 Improvement Mod) has been put in the flystate, the above inputevent appears as if in a loop. Had to shut input event logging off. Is there a way to indicate that we don't want to log "InputEvent found:" at this time? Sure would save a lot of log. Thanks FSUIPC7.ini FSUIPC7.log

Sorry, the .ZIP file is still too large to upload. Even the image file of the zip results are too large. I have pared down the files and did attach them above.

Thanks for your development and attention. I tried FSUIPC7 "********* FSUIPC7, Version 7.3.26f (23rd November 2023) by John Dowson *********" I had a slight problem as there were several unrecognized input events as if in a loop. I have attached the log. I also extracted the "InputEvent received but not known:" input events, sorted by name, marked the duplicates and resorted by FSUIPC7 time. They are listed in the file FSUIPC7.sorted.txt. I'm not sure what to make of this? This the DA62 Improvement Mod. Just got a message "too large". I'll have to cut them back. The log ended at line # 47,930. 2FSUIPC7.log 2-FSUIPC7.sorted.txt

Thank you again. It is difficult using ipc.execCalcCode(“code”) when you don't know the indices used. I look forward to using the Beta version today. Is there a significance of the parameter in the event log with a toggle? apparently it shows correctly with the SET controls. The ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE seems to show multiple numbers in the param.

I have been exploring the events with the DA62 aircraft. Several of the events are toggle type events (controls). I was to understand that that toggle events have no parameters. However there are parameters displayed. One or two questions. 1. In the Event Log Entry - one of the kex values is the parameter. What is the other hex value? 2. If a toggle event has no parameter, do you know why one is shown in the entries? 3. If there are 2 indices in an event, is the param one of the indices and can Lua show both indices? Engine Master Left On 1862188 *** EVENT: Cntrl= 67063 (0x000105f7), Param= 0 (0x00000000) ENGINE_MASTER_1_TOGGLE 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 9 (0x00000009) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 5 (0x00000005) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 7 (0x00000007) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE 1862204 *** EVENT: Cntrl= 66241 (0x000102c1), Param= 2 (0x00000002) TOGGLE_MASTER_BATTERY 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 6 (0x00000006) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE [0]: Source bus index [1]: bus index Toggle bus connection state with a bus. Takes two indices, the initial bus and the second bus (see SimVars And Keys for more information). The bus index is the N index of the bus.N definition in both cases.