Solved Alt launcher key assignment error - can't solve it
-
Hi guys,
just did a vanilla reinstall of everything, twice. I can’t get rid of this and can’t assign any keys…
Any help greatly appreciated.Thanks!
-
-
Oh dang, I think I realize what’s happening… new theory…
There is a “Stock” subfolder of default XML templates, for popular hotas devices. It appears many of those templates were never updated for the DX32->DX128 transition.
That’s where the 32-slot XML files are coming from. Those templates are loaded at first-time startup, if you haven’t already saved any mappings for that particular device.
(Older versions of AL must either have failed silently, or crashed later, when attempting to bind a button number >=32 … new version of AL is failing sooner)
If anyone is game to do a quick validation:
-
rename your
"...\Falcon BMS 4.37\Launcher\Stock"
folder … toStock_backup
or something -
delete (or better, move to a backup folder) any
"Setup\*.xml"
files in your...\Falcon BMS 4.37\user\Config
folder
Let me know if that helps.
-
-
I have the same issue. I also installed the new launcher. I can map the F15 controls though but not the F16. Can you also map the F15 controls?
-
Same Issue, There is another post with us complaining as well.
-
Same issue here.
-
@thunder @travissgrey @Jambo @Rakamora thanks – I believe this is the old bug https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/62 resurfacing … happens when forward-porting an older XML file that only has 32 button slots. BMS uses up to 128 buttons per device, now.
we’re working on a fix … only workaround, for now, is to delete (backup first) those old XML files, and recreate them from scratch.
-
@airtex2019 thanks but i don’t have any idea where those files are nor how to manually recreate them. I did a vanilla install, twice. I don’t see how anything could have been forward-ported, but i’m no expert…
I guess I’ll wait for the fix
-
deleting those files doesn’t fix the issue.
-
I have the same problem. In addition, when I close the luncher and try to open it again, nothing happens. No message, it just doesn’t start. Deleting it including registry-clean so that there is absolut nothing left and reinstalling didn’t help.
-
@Jack-Daniels @Jambo @thunder @travissgrey @Rakamora would you please share with me your AL logs?
start /run “%LocalAppData%\Benchmark_Sims\Launcher_Log.txt”
https://pastebin … or paste here using a
code-format block
-
I have the same issue of it not closing properly. So the reason it does start again is because it is still running but you cant see that unless you open task manager and search for it. this is only way i can get it to stop. i have to go in there and end task. I see on another thread that the full installer may be causing the issue. and we should try and run in admin or change reg setting to allow edit of the files. I did a full install and am having all the same issues you are. When i get home i can send my log file. i can say in the log it shows like it is trying to find a file in C:\1\xxxxx. and i have no folder in C drive.
-
@airtex2019
As requested[27.10.2023 19:12:51] [INFO] :: Application Initialization starting. [27.10.2023 19:12:51] [INFO] :: Post_OnInitialized. [27.10.2023 19:12:51] [INFO] :: AutoUpdate-check initiated. [27.10.2023 19:12:51] [INFO] :: FalconBMS Launcher v2.4.0 [27.10.2023 19:12:51] [INFO] :: Start Reading Launcher Settings. [27.10.2023 19:12:51] [INFO] :: Finished Reading Launcher Settings. [27.10.2023 19:12:51] [INFO] :: Start Reading Registry. [27.10.2023 19:12:51] [INFO] :: Finished Reading Registry. [27.10.2023 19:12:51] [INFO] :: Start Init Devices. [27.10.2023 19:12:52] [INFO] :: Completed RSS fetch on background-thread. [27.10.2023 19:12:52] [INFO] :: Finished Init Devices. [27.10.2023 19:12:52] [INFO] :: Start VR Check. [27.10.2023 19:12:52] [INFO] :: Finished VR Check. [27.10.2023 19:12:52] [INFO] :: Start Timers. [27.10.2023 19:12:52] [INFO] :: Timers Started. [27.10.2023 19:12:52] [INFO] :: Post_OnInitialized complete. [27.10.2023 19:12:53] [INFO] :: RSS update finished. [27.10.2023 19:13:08] [EXCEPTION] Das Quellarray ist nicht lang genug. Überprüfen Sie srcIndex, die Länge und die Untergrenze des Arrays.:: Source: mscorlib Target Site: Void Copy(System.Array, Int32, System.Array, Int32, Int32, Boolean) Message: Das Quellarray ist nicht lang genug. Überprüfen Sie srcIndex, die Länge und die Untergrenze des Arrays. Details: Exception Data: System.Collections.ListDictionaryInternal Stack Trace: bei System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable) bei System.Array.Copy(Array sourceArray, Array destinationArray, Int32 length) bei FalconBMS.Launcher.Input.JoyAssgn.CopyButtonsAndHatsFromCurrentProfile(JoyAssgn otherJoy) in C:\1\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\Input\JoyAssgn.cs:Zeile 414. bei FalconBMS.Launcher.Input.JoyAssgn.MakeTempCloneForKeyMappingDialog() in C:\1\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\Input\JoyAssgn.cs:Zeile 485. bei FalconBMS.Launcher.Windows.KeyMappingWindow.Reset() in C:\1\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\Windows\KeyMappingWindow.xaml.cs:Zeile 88. bei FalconBMS.Launcher.Windows.KeyMappingWindow..ctor(DeviceControl deviceControl, KeyAssgn SelectedCallback) in C:\1\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\Windows\KeyMappingWindow.xaml.cs:Zeile 54. bei FalconBMS.Launcher.Windows.KeyMappingWindow.ShowKeyMappingWindow(Window owner, DeviceControl deviceControl, KeyAssgn SelectedCallback) in C:\1\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\Windows\KeyMappingWindow.xaml.cs:Zeile 59. bei FalconBMS.Launcher.Windows.MainWindow.DataGrid_MouseButtonDoubleClick(Object sender, MouseButtonEventArgs e) in C:\1\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\Windows\MainWindowKeyMapping.cs:Zeile 132. bei System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget) bei System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) bei System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) bei System.Windows.UIElement.RaiseEvent(RoutedEventArgs e) bei System.Windows.Controls.Control.OnMouseDoubleClick(MouseButtonEventArgs e) bei System.Windows.Controls.Control.HandleDoubleClick(Object sender, MouseButtonEventArgs e) bei System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget) bei System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) bei System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent) bei System.Windows.UIElement.OnMouseDownThunk(Object sender, MouseButtonEventArgs e) bei System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget) bei System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) bei System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) bei System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args) bei System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted) bei System.Windows.Input.InputManager.ProcessStagingArea() bei System.Windows.Input.InputManager.ProcessInput(InputEventArgs input) bei System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport) bei System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel) bei System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled) bei System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) bei MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) ============
-
yes, yours is showing the same as mine.
-
@Jack-Daniels this is for the original problem report – the error message about array not big enough, when trying to do a key or button mapping – got it.
do you have any logs for the “fails to start at all” problem?
-
@airtex2019 Nope, but @Jambo ist right here, in TaskManager I see it’s still running. If I close it there I can restart.
-
@airtex2019 The fail to start issue is because even though we exit out of BMS and AL , it is still running in the background. So something is failing to close the app. The only way i can close it is to end task in Task Manager. Not sure how we can get a log for this.
-
Does anyone have the full installer for 4.37.2 or any other 4.37
I would like to try and install this version then do a incremental update to 4.37.3 to see if this fixes the issue.
-
@Jambo @airtex2019 and this is only after you tried to edit the keybindings and get the array error. If you don’t go to the settings, it’s closeing proper.
-
Also i just noticed that Max has posted a newer full installer. We should try this installer and see if the problem is resolved. I will in a couple of hours when i get home.
-
@Jambo I tried the new installer. Same issue.
-
@Jambo got it … interesting … thanks.
I believe you all, when you tell me this is a fresh install and you’re not updating an existing older BMS folder… or manually copying older XML files into your Config folder.
But I currently have no other theory. Obviously this isn’t happening for me or any of the beta testers…
I’m wondering, is there any other point of commonality? OS? (Win10 or 11?) Maybe some unusual device(s) that the code is not accounting for… can you share your DeviceSorting.txt contents?
Maybe more file/directory permissions problems? Can you share the full installation path of where
C:\Falcon BMS 4.37\Launcher\FalconBMS_Alternative_Launcher.exe
resides?