Leo Bodnar inputs partially working in Falcon BMS
-
Or in AL
-
But yes, the best is to test in 3d, I have had same problem in AL with some dx; appears the dx is not assigned but works fine in the pit
-
-
Well, the switch doesn’t hold a command, I click in the command list and flip the switch on that moment. Worked as a charm in the past. So I must do it in 2D. I know sometimes it’s not always top but I was able to manage it all the times. As long as I have a button appearing I can work with it.
Just a silly question, with AL you mean … ?
-
@PopTops said in Leo Bodnar inputs partially working in Falcon BMS:
Well, the switch doesn’t hold a command, I click in the command list and flip the switch on that moment. Worked as a charm in the past. So I must do it in 2D. I know sometimes it’s not always top but I was able to manage it all the times. As long as I have a button appearing I can work with it.
Just a silly question, with AL you mean … ?
I think with AL he is refering to Alternate Launcher.
-
@PopTops map your stuff in AL (alternate launcher), start your sim via AL, and test in 3D cockpit.
-
@Atlas Just gave it a try and no luck neither.
When double clicking so I can assign a button in the “Keymapping” section, I get this;
When checking the log file I’ve got this;
*Source array was not long enough. Check srcIndex and length, and the array’s lower bounds.::Source: mscorlib
Target Site: Void Copy(System.Array, Int32, System.Array, Int32, Int32, Boolean)
Message: Source array was not long enough. Check srcIndex and length, and the array’s lower bounds.
Details:Exception Data: System.Collections.ListDictionaryInternal*
-
@Atlas said in Leo Bodnar inputs partially working in Falcon BMS:
@PopTops map your stuff in AL (alternate launcher), start your sim via AL, and test in 3D cockpit.
Even if you don’t see the assignation in some cases in AL
-
@PopTops this is a known bug in AL.
Fixed in latest daily build… if you’re willing to help alpha-test it, send me a DM.
If not that’s ok, there’s a workaround possible
-
So, just wanted to update you all.
Using the AL, it first was giving me the error msg I mentioned above so I used the test version. This one worked at first and the day after it was not working anymore. Again my inputs were not working.
In the meanwhile the latest AL was released and this one is doing the job. I have no explanation or I didn’t do anything in particular.
In 2D I still have the same fishy behavior but AL saved me! -
I’m having this same issue, though it seems only when trying to assign keys to the F-16, F-15 seems to work. Any help would be appreciated. running 3.37.3 and launcher v2.4.0.
-
@ProbablyaLich said in Leo Bodnar inputs partially working in Falcon BMS:
I’m having this same issue, though it seems only when trying to assign keys to the F-16, F-15 seems to work. Any help would be appreciated. running 3.37.3 and launcher v2.4.0.
Try running the latest build of the alt launcher. I ran into something similar this week and that helped the issue for me.
-
@Jumpstart5179 Thank you, 2.4.1.4 works the perfectly!
-
@ProbablyaLich your welcome.
-
Did you solve the problem ? I have some related issue here: https://forum.falcon-bms.com/topic/26435/falcon-bms-stop-reading-some-buttons-via-leo-bodnar-card?_=1703936903579