Blindside Posted November 8, 2020 Report Share Posted November 8, 2020 (edited) Hi, what I am trying to do is to activcate multiple key presses sequentally on TM HOTAS Warthog 3-way toggle. When the toggle (registering as key 12) is pressed, ctrl+L should register (works)! When the toggle key 12 is released, first ctrl+L should register and then tab+T should register --> only ctrl-L register, tab+T does not I have edited the INI the following way hoping it would work: 28=PA,12,K76,10 -{Key press: ctl+L}- 29=UA,12,K76,10 -{Key press: ctl+L}- 30=UA,12,K76,10 -{Key press: tab+T}- Am I doing something wrong or why won't the key presses not register correctly in the sim? EDIT: Some additional information which might be necessery for understanding: I am trying to control multiple lights in the TBM 930 with the switch. The TBM has a 3 way light switch which reads OFF - TAXI - LDG. I have bound one key combination (tab+T) to control multiple lights, including taxi toggle. When I now release key 13 on the HOTAS, strobe and NAV turn on and the 3 way switch in the TBM moves from OFF -> TAXI. When I know activate key 12 (ie move my physical 3-way toggle on the HOTAS one way up), only ctrl+L is sent and the 3-way switch in the TBM moves from TAXI -> LDG. When I now move my physical toggle in the middle position, I am releasing key 12. What I would like to happen is a) ctrl+L is sent again, the TBM switch moves from LDG -> OFF and then immediately after I would like tab+T to be sent, so the 3 way switch in the game moves from OFF -> TAXI. What happens now is, that ctrl+L is apparantly sent since the switch moves from LDG -> OFF but the tab+T message is never sent, since the switch never moves to OFF -> TAXI. If I try to do it on the physical keyboard, it works as it should. Edited November 8, 2020 by Blindside Link to comment Share on other sites More sharing options...
John Dowson Posted November 8, 2020 Report Share Posted November 8, 2020 1 hour ago, Blindside said: I have edited the INI the following way hoping it would work: 28=PA,12,K76,10 -{Key press: ctl+L}- 29=UA,12,K76,10 -{Key press: ctl+L}- 30=UA,12,K76,10 -{Key press: tab+T}- You cannot just change the annotation/comment - the assignment are all sending the same key (K76 or 'L') and the same modifier (10 or ctrl). Change the values to the key and modifier you require - see the advanced user guide for details. Or, you could program the release sending the tab+T in the FSUIPC UI, then duplicate the press assignment and change that to a release. Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 Sorry, that was a bit stupid to edit the comments instead of the actual command. I have changed the ini according to your description, but in the game, still only the ctr+L is registered, that tab+T is not. Is there still something wrong with the code? 40=PA,12,K76,10 -{Key press: ctl+L}- 41=UA,12,K76,10 -{Key press: ctl+L}- 42=UA,12,K84,12 -{Key press: tab+T}- Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 Looks ok. Try activating logging for buttons & keys and see what you can see. Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 (edited) Hi, I did and attached the log file. I started a new log, pressed buton 12 (ie moved the toggle) and unpressed button 12 (ie moved the toggle back to neutral). FWIW, the keyboard shortcuts themselves work without issues. FSUIPC7.log Edited November 9, 2020 by Blindside Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 Can you also attach your FSUIPC7.ini file. And when you attach a log, please always attach the full log, not a continuation. There is also information at the beginning of the file that I need to see. John Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 Please find attached the ini. And sorry, I do not know what you mean with full log. The only row that I edited out is my mail adress and name. Otherwise this is the complete file as I find it in the folder. FSUIPC7.ini Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 1 minute ago, Blindside said: , I do not know what you mean with full log I mean that you should not start a new log by selecting 'New Log' from the log menu. I'll investigate and get back to you. Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 Sorry, the whole log file is too large to upload it here (38kb, I get an error message). Additonally, "unpressing" key 12 for ctr+L now works only every 2nd time. Every other time nothing happens if I release key 12. tab+t never registers, independent of that. Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 Just tried it and it works ok here.... Did you edit the ini file with FSUIPC7 still running and not 'reload' it? Try exiting FSUIPC7 and check your ini to make sure the assignments are still there. Here's my log with those assignments (different device and button number) - it is sending two Ctrl+L and one tab+T: Quote 490797 JoystickValues PCnum=0, dwCount=1, data[2]={000000af 00000040} 490797 Button changed: bRef=0, Joy=175, Btn=6, Pressed 490797 [Buttons] 72=P175,6,K76,10 490797 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 490797 [Buttons] 73=U175,6,K76,10 490797 [Buttons] 74=U175,6,K84,12 490797 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 490812 Sending WM_KEYDOWN, Key=76 (Scan code 38), Ctr=1 490859 *** EVENT: Cntrl= 65751 (0x000100d7), Param= 0 (0x00000000) LANDING_LIGHTS_TOGGLE 490859 EV_KEYDOWN received: 0x4C (L) 490859 KEYDOWN: VK=76, Waiting=0, Repeat=N, Shifts=2 490859 .. KeyDown received from FS but not programmed 490875 *** EVENT: Cntrl= 66240 (0x000102c0), Param= 0 (0x00000000) TOGGLE_TAXI_LIGHTS 490906 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=0 490906 EV_KEYDOWN received: 0x4C (L): repeat set 490906 KEYDOWN: VK=76, Waiting=0, Repeat=Y, Shifts=2 490906 .. KeyDown received from FS but not programmed 490922 Sending WM_KEYUP, Key=76 (Scan code 38), Ctr=2 490937 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 490937 JoystickValues PCnum=0, dwCount=1, data[2]={000000af 00000000} 490937 Button changed: bRef=0, Joy=175, Btn=6, Released 490937 [Buttons] 72=P175,6,K76,10 490937 [Buttons] 73=U175,6,K76,10 490937 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 490937 [Buttons] 74=U175,6,K84,12 490937 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=2 490937 SendKeyToFS(00080054=[tab+T], KEYDOWN) ctr=4 490953 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=6 490969 EV_KEYUP received: 0x4C (L) 490969 KEYUP: VK=76, Waiting=0, Shifts=2 490969 .. KeyUp received from FS but not programmed 490969 Sending WM_KEYDOWN, Key=76 (Scan code 38), Ctr=5 490984 Sending WM_KEYUP, Key=76 (Scan code 38), Ctr=4 491000 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=3 491000 Sending WM_KEYDOWN, Key=9 (Tab) (Scan code 15), Ctr=3 491015 Sending WM_KEYDOWN, Key=84 (Scan code 20), Ctr=1 491047 SendKeyToFS(00080054=[tab+T], KEYUP) ctr=0 491062 Sending WM_KEYUP, Key=84 (Scan code 20), Ctr=2 491062 *** EVENT: Cntrl= 65556 (0x00010014), Param= 0 (0x00000000) XPNDR 491062 EV_KEYDOWN received: 0x54 (T) 491062 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=16 491062 .. KeyDown received from FS but not programmed 491062 EV_KEYDOWN received: 0x9 ( ) 491062 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=16 491062 .. KeyDown received from FS but not programmed 491062 *** EVENT: Cntrl= 66240 (0x000102c0), Param= 0 (0x00000000) TOGGLE_TAXI_LIGHTS 491078 Sending WM_KEYUP, Key=9 (Tab) (Scan code 15), Ctr=1 491109 EV_KEYUP received: 0x54 (T) 491109 KEYUP: VK=84, Waiting=0, Shifts=0 491109 .. KeyUp received from FS but not programmed 491109 EV_KEYUP received: 0x9 ( ) 491109 KEYUP: VK=9, Waiting=0, Shifts=0 491109 .. KeyUp received from FS but not programmed I am wondering if you have programmed this to a "sticky" button, i.e. one that on first press sends a button down, and on second press sends a button up. Even so, it should still be sending the two keys on the button up. 16 minutes ago, Blindside said: Sorry, the whole log file is too large to upload it here (38kb, I get an error message). You can zip it if its too big. John Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 Thanks for trying to help. I have zipped and attached the log file. I have restarted the PC etc. between editing the INI, nothing sticks. I also tried to remap the command to another three way switch on the throttle (button 26), but it had no effect. I can see in the console that each toggle movement is registered, but it appears that the key presses are not sent to MSFS. What I currently see when I either press and unpress button 12 or 26 (wach time waiting 1-2 seconds): Only ctr+L is send every 3-4 times even not ctr+L is sent, ie nothing happens at all every ~10 times: ctr+L AND tab+T are sent correctly So for me it appears that only every n'th time a keystroke is sent, but each and every movement of the switches is registered in the console and log file. I am trying to program the 3-way switches on the HOTAS thurster, ie these silver switches which have 3 positions in which the remain by themselve and the middle position is off. FSUIPC7.zip Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 3 minutes ago, Blindside said: I am trying to program the 3-way switches on the HOTAS thurster, ie these silver switches which have 3 positions in which the remain by themselve and the middle position is off. I think you should remove any assignments to that switch, activate button logging and then move the switch between the three settings to see what is actually being sent on each change. If its a 3-position switch, it must be using more than one button number, otherwise I don't know how it can function properly. I don't have any 3 position switches so cannot advise. Try operating it with logging on (and the console open), and see what button presses/releases you see when you change its position: off -> up up -> off off -> down down->off ? Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 That is what I tried and this is what I see in th console (bold by me): switch 1: off - up: 13235 FirstButtonChange res=0000000C (0.0, 12) switch 1: up - off:switch 1: off - down: 14110 FirstButtonChange res=0000000D (0.0, 13) switch 1: down - off: So in the console I do not see anything happening when I move the three way switch from one of the "on" positions to off. Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 Please repeat but with the assignment UI panel closed. I am interested in the 'Button changed' log messages..... That log shows the switch has two "buttons", but its not logging the releases with the ui panel open. Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 But if I don't have the assignment window open, nothing registers in the console or log. Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 7 minutes ago, Blindside said: But if I don't have the assignment window open, nothing registers in the console or log. Is MSFS running? Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 It wasn't, thanks for your patience.... I hope this is what you were looking for: Off (middle position) to up [button 12]: 18125 Button changed: bRef=0, Joy=0 (A), Btn=12, Pressed 18125 [Buttons] 40=PA,12,K76,10 18125 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 18125 [Buttons] 41=UA,12,K76,10 18125 [Buttons] 42=UA,12,K84,12 18125 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 18140 Sending WM_KEYDOWN, Key=76 (Scan code 38), Ctr=1 18140 EV_KEYDOWN received: 0x4C (L) 18140 KEYDOWN: VK=76, Waiting=0, Repeat=N, Shifts=2 18140 .. KeyDown received from FS but not programmed 18234 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=0 18234 Sending WM_KEYUP, Key=76 (Scan code 38), Ctr=2 18250 EV_KEYUP received: 0x4C (L) 18250 KEYUP: VK=76, Waiting=0, Shifts=2 18250 .. KeyUp received from FS but not programmed 18250 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 Up [button 12] to off (middle position): 28359 Button changed: bRef=0, Joy=0 (A), Btn=12, Released 28359 [Buttons] 40=PA,12,K76,10 28359 [Buttons] 41=UA,12,K76,10 28359 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 28359 [Buttons] 42=UA,12,K84,12 28359 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=2 28359 SendKeyToFS(00080054=[tab+T], KEYDOWN) ctr=4 28359 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=6 28375 Sending WM_KEYDOWN, Key=76 (Scan code 38), Ctr=5 28375 EV_KEYDOWN received: 0x4C (L) 28375 KEYDOWN: VK=76, Waiting=0, Repeat=N, Shifts=2 28375 .. KeyDown received from FS but not programmed 28390 Sending WM_KEYUP, Key=76 (Scan code 38), Ctr=4 28390 EV_KEYUP received: 0x4C (L) 28390 KEYUP: VK=76, Waiting=0, Shifts=2 28390 .. KeyUp received from FS but not programmed 28406 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=3 28406 Sending WM_KEYDOWN, Key=9 (Tab) (Scan code 15), Ctr=3 28406 EV_KEYDOWN received: 0x9 ( ) 28406 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=16 28406 .. KeyDown received from FS but not programmed 28422 Sending WM_KEYDOWN, Key=84 (Scan code 20), Ctr=1 28468 SendKeyToFS(00080054=[tab+T], KEYUP) ctr=0 28468 Sending WM_KEYUP, Key=84 (Scan code 20), Ctr=2 28484 Sending WM_KEYUP, Key=9 (Tab) (Scan code 15), Ctr=1 28484 EV_KEYDOWN received: 0x54 (T) 28484 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=0 28484 .. KeyDown received from FS but not programmed 28500 EV_KEYUP received: 0x54 (T) 28500 KEYUP: VK=84, Waiting=0, Shifts=0 28515 .. KeyUp received from FS but not programmed 28515 EV_KEYUP received: 0x9 ( ) 28515 KEYUP: VK=9, Waiting=0, Shifts=0 28515 .. KeyUp received from FS but not programmed Off (middle position) to down [button 13]: 32547 Button changed: bRef=0, Joy=0 (A), Btn=13, Pressed 32547 [Buttons] 25=PA,13,K79,12 32547 SendKeyToFS(0008004F=[tab+O], KEYDOWN) ctr=0 32547 [Buttons] 26=UA,13,K79,12 32562 Sending WM_KEYDOWN, Key=9 (Tab) (Scan code 15), Ctr=2 32578 Sending WM_KEYDOWN, Key=79 (Scan code 24), Ctr=1 32578 EV_KEYDOWN received: 0x4F (O) 32578 KEYDOWN: VK=79, Waiting=0, Repeat=N, Shifts=16 32578 .. KeyDown received from FS but not programmed 32578 EV_KEYDOWN received: 0x9 ( ) 32578 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=16 32578 .. KeyDown received from FS but not programmed 32656 SendKeyToFS(0008004F=[tab+O], KEYUP) ctr=0 32656 Sending WM_KEYUP, Key=79 (Scan code 24), Ctr=2 32672 EV_KEYUP received: 0x4F (O) 32672 KEYUP: VK=79, Waiting=0, Shifts=16 32672 .. KeyUp received from FS but not programmed 32672 EV_KEYDOWN received: 0x9 ( ) 32672 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=16 32672 .. KeyDown received from FS but not programmed 32672 Sending WM_KEYUP, Key=9 (Tab) (Scan code 15), Ctr=1 32687 EV_KEYUP received: 0x9 ( ) 32687 KEYUP: VK=9, Waiting=0, Shifts=0 32687 .. KeyUp received from FS but not programmed Down [button 13] to off (middle position): 34422 Button changed: bRef=0, Joy=0 (A), Btn=13, Released 34422 [Buttons] 25=PA,13,K79,12 34422 [Buttons] 26=UA,13,K79,12 34422 SendKeyToFS(0008004F=[tab+O], KEYDOWN) ctr=0 34437 Sending WM_KEYDOWN, Key=9 (Tab) (Scan code 15), Ctr=2 34453 Sending WM_KEYDOWN, Key=79 (Scan code 24), Ctr=1 34453 EV_KEYDOWN received: 0x9 ( ) 34453 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=16 34453 .. KeyDown received from FS but not programmed 34468 EV_KEYDOWN received: 0x4F (O) 34468 KEYDOWN: VK=79, Waiting=0, Repeat=N, Shifts=16 34468 .. KeyDown received from FS but not programmed 34531 SendKeyToFS(0008004F=[tab+O], KEYUP) ctr=0 34531 Sending WM_KEYUP, Key=79 (Scan code 24), Ctr=2 34547 Sending WM_KEYUP, Key=9 (Tab) (Scan code 15), Ctr=1 34547 EV_KEYUP received: 0x4F (O) 34547 KEYUP: VK=79, Waiting=0, Shifts=0 34547 .. KeyUp received from FS but not programmed 34547 EV_KEYDOWN received: 0x9 ( ) 34547 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=0 34547 .. KeyDown received from FS but not programmed 34562 EV_KEYUP received: 0x9 ( ) 34562 KEYUP: VK=9, Waiting=0, Shifts=0 34562 .. KeyUp received from FS but not programmed Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 So the switch has two buttons, with the press being sent on each when iy goes to up/down, and a release sent when you put ity back to the centre. This is what I expected. 12 minutes ago, Blindside said: Off (middle position) to up [button 12]: 18125 Button changed: bRef=0, Joy=0 (A), Btn=12, Pressed 18125 [Buttons] 40=PA,12,K76,10 18125 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 18125 [Buttons] 41=UA,12,K76,10 18125 [Buttons] 42=UA,12,K84,12 18125 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2 18140 Sending WM_KEYDOWN, Key=76 (Scan code 38), Ctr=1 18140 EV_KEYDOWN received: 0x4C (L) 18140 KEYDOWN: VK=76, Waiting=0, Repeat=N, Shifts=2 18140 .. KeyDown received from FS but not programmed 18234 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=0 18234 Sending WM_KEYUP, Key=76 (Scan code 38), Ctr=2 18250 EV_KEYUP received: 0x4C (L) 18250 KEYUP: VK=76, Waiting=0, Shifts=2 18250 .. KeyUp received from FS but not programmed 18250 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1 So this is sending the ctrl+L, as expected: 18125 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 18234 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=0 12 minutes ago, Blindside said: Up [button 12] to off (middle position): 28359 Button changed: bRef=0, Joy=0 (A), Btn=12, Released 28359 [Buttons] 40=PA,12,K76,10 28359 [Buttons] 41=UA,12,K76,10 28359 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 28359 [Buttons] 42=UA,12,K84,12 28359 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=2 28359 SendKeyToFS(00080054=[tab+T], KEYDOWN) ctr=4 28359 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=6 28375 Sending WM_KEYDOWN, Key=76 (Scan code 38), Ctr=5 28375 EV_KEYDOWN received: 0x4C (L) 28375 KEYDOWN: VK=76, Waiting=0, Repeat=N, Shifts=2 28375 .. KeyDown received from FS but not programmed 28390 Sending WM_KEYUP, Key=76 (Scan code 38), Ctr=4 28390 EV_KEYUP received: 0x4C (L) 28390 KEYUP: VK=76, Waiting=0, Shifts=2 28390 .. KeyUp received from FS but not programmed 28406 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=3 28406 Sending WM_KEYDOWN, Key=9 (Tab) (Scan code 15), Ctr=3 28406 EV_KEYDOWN received: 0x9 ( ) 28406 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=16 28406 .. KeyDown received from FS but not programmed 28422 Sending WM_KEYDOWN, Key=84 (Scan code 20), Ctr=1 28468 SendKeyToFS(00080054=[tab+T], KEYUP) ctr=0 28468 Sending WM_KEYUP, Key=84 (Scan code 20), Ctr=2 28484 Sending WM_KEYUP, Key=9 (Tab) (Scan code 15), Ctr=1 28484 EV_KEYDOWN received: 0x54 (T) 28484 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=0 28484 .. KeyDown received from FS but not programmed 28500 EV_KEYUP received: 0x54 (T) 28500 KEYUP: VK=84, Waiting=0, Shifts=0 28515 .. KeyUp received from FS but not programmed 28515 EV_KEYUP received: 0x9 ( ) 28515 KEYUP: VK=9, Waiting=0, Shifts=0 28515 .. KeyUp received from FS but not programmed This is your release, and is sending the Ctrl+L followed by the Tab+T:: 28359 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 28359 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=2 28359 SendKeyToFS(00080054=[tab+T], KEYDOWN) ctr=4 28468 SendKeyToFS(00080054=[tab+T], KEYUP) ctr=0 So it looks to me that its sending exactly what you have assigned. So what exactly is the issue? Maybe its the timing... with the tab+T down being sent at the same time as the keyup for the Ctr+L? Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 I'm also wondering maybe if its the use of the tab key. Iy is being treated as a modifier key when it isn't really. I'll do some tests over the next few days and get back to you. Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 Quote So what exactly is the issue? Maybe its the timing... with the tab+T down being sent at the same time as the keyup for the Ctr+L? The issue is that the tab+T never registers in the sim (although it is being sent). Desired behaviour: Upon releasing key 12, the ingame 3-way switch should move from LDG --> Off (ctrl+L) and then from Off --> Taxi (tab+T). Observed behaviour: Upon releasing key 12, the ingame 3-way switch either does not move at all or only moves from LDG --> Off (ctrl+L) and NOT from Off --> Taxi (tab+T). As I wrote initially: I am trying to control multiple lights in the TBM 930 with the switch. The TBM has a 3 way light switch which reads OFF - TAXI - LDG. I have bound one key combination (tab+O) to control multiple lights, including taxi toggle. [Taxi toggle is also bound to tab+T. So 2 key combinations are bound to taxi toggle: tab+O and tab+T]. When I now release key 13, strobe and NAV turn on and the 3 way switch in the TBM moves from OFF -> TAXI. When I know activate key 12 (ie move my physical 3-way toggle on the HOTAS one way up), only ctrl+L is sent and the 3-way switch in the TBM moves from TAXI -> LDG. When I now move my physical toggle in the middle position, I am releasing key 12. What I would like to happen is a) ctrl+L is sent again, the TBM switch moves from LDG -> OFF and then immediately after I would like tab+T to be sent, so the 3 way switch in the game moves from OFF -> TAXI. So could it be the timing, that it takes a few fractions of a secod to animate the 3 way button in game from LDG --> OFF? I have attached a screenshot of the in game button to visualize it (I do not use tab+O a second time because 2 other in game buttons are bound to it and if I would assign tab+O for releasing 12, the other lights which are mapped to tab+O would turn off). EDIT: for clarity. Step "2." of release 12 is the one not working. Link to comment Share on other sites More sharing options...
John Dowson Posted November 9, 2020 Report Share Posted November 9, 2020 3 minutes ago, Blindside said: The issue is that the tab+T never registers in the sim (although it is being sent). Ok! I thought your issue was that it wasn't being sent! Could you try assigning the Tab-T on its own, to see if it works like that. However, it may be a timing issue when you are overloading the keypresses on a single button. It may be better to use the controls directly, or maybe a lua script. Leave it with me and I''ll get back to you, but it may take a day or two. John Link to comment Share on other sites More sharing options...
Blindside Posted November 9, 2020 Author Report Share Posted November 9, 2020 Quote Could you try assigning the Tab-T on its own, to see if it works like that. I just tried it: works perfectly fine. On the same physical switch or another. So ctrl+L on its own: fine. tab+T on its own: fine. ctrl+L and tab+T: not working properly. Quote However, it may be a timing issue when you are overloading the keypresses on a single button. It may be better to use the controls directly, or maybe a lua script. Leave it with me and I''ll get back to you, but it may take a day or two. It looks like it could be a timing issue. That would explain why rarely even ctr+L is not being registered and simply nothing happens. Thank you for your efforts! Link to comment Share on other sites More sharing options...
John Dowson Posted November 10, 2020 Report Share Posted November 10, 2020 @Blindside Just took a look at the TBM 930....why don't you just use the controls rather than the keypresses: Toggle Taxi Lights Landing Light Toggle Assign your button 12 to one of those controls for both press and release, and the other control to button 13 for press and release. Then your switch in one direction should activate the landing lights, the other the taxi lights, and when in centre (off) both will be off. Link to comment Share on other sites More sharing options...
Blindside Posted November 10, 2020 Author Report Share Posted November 10, 2020 @John Dowson Thanks for your feedback. I could to this, but this is not what I want to achieve since it does not include the NAV and Strobe lights. What I would like to happen: Switch is default in the down (13) position I move the switch to the middle (off position): Taxi, Strobe and NAV lights turn on. This works now, since all 3 are bound to tab+O I move the switch from the off to the up (12) position: The landing light is turned on, taxi is automatically off due to the TBM 930 configuration. I move the switch from up (12) to the middle (off position): The NAV and Strobe light stays on, the landing light turns off, the taxi light turns on. Repeat 2-3 as desired. I move the switch from middle (off) to down (13): Taxi, NAV and Strobe light turn off. Link to comment Share on other sites More sharing options...
John Dowson Posted November 10, 2020 Report Share Posted November 10, 2020 (edited) Then do the same but switch from using the key presses to using the provided controls for taxi and landing lights: Landing lights toggle: C65751 Taxi lights toggle: C66240 Both with a parameter 0. Remove these from your 'Tab-O' control, and overload where needed (with a mixture of the controls and keypresses). Edited November 10, 2020 by John Dowson controls added Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now