SLangner last edited by
A ‘glitch’ that plagued me when programming DirectX functions in 4.32 seems to have been eliminated in 4.33.
My system includes MFD panels, Saitek’s X-55 Rhino stick, and Saitek’s X-65F TQS. Both versions of the sim (4.32 and 4.33) recognize button numbers from 1 to 142.
Anyway, while doing DirectX programming in 4.32, for some unknown reason, the display beneath the keyfile callback box would suddenly show that button 143 had been activated. This caused considerable consternation when I had selected a line in the box to assign to a button. The ‘gremlin’ would often strike and assign that function to button 143. Then while flying, if I hadn’t caught it during programming, that same gremlin would strike again, and whatever function assigned to that same button would be executed. After a lot of hair-pulling, I figured out a way to negate any function assignments to that phantom button by manually adding a ‘no function’ assignment to it at the end of the keyfile.
This has not caused me any problems so far in 4.33.
Blu3wolf last edited by
It has not caused me problems, but I have seen it. However, in my case, the button in question was not ‘suddenly activated’ so much as ‘still activated’, as a lot of my switch panels are constantly sending DX keypress events due to their design. For instance, my RF switch is almost always in NORM, and also always sending the button is depressed signal to the sim, and so in setup, its not unusual for me to see it show up in the display.
EDIT: I see now your bug was due to an button out of your normal range. Mine was just a normal button press within the range, somewhere around 150~ for my keyfile I think. Not the same behavior then.