X-55 Aircraft Starts Every Mission Trimmed to the Extreme Right
-
A powered USB hub resolved all the ghosting issues for me. Somehow, I still believe you have some ghosting. The hubs are cheap and may be an easy fix. Before I got the hub, I had to make sure I did not program any critical commands to my throttle…like gears, etc. I did not find a way to unmap the buttons. I just put commands that did not affect flight, but was still annoying. No problem at all now with the powered USB hub.
I am already running both of mine through a powered USB Hub.
-
I am already running both of mine through a powered USB Hub.
Roger that. When you set up your trims to the rotaries, are you using the Saitek software, or are you using the BMS setup page?
-
Topic title pretty much says it all. I have an X-55, and every mission I start off the aircraft starts off trimmed to the extreme right, in just a few seconds my plane is completely inverted unless I immediately correct with my stick when the mission loads in.
I tried mapping my trim commands to stick buttons and using those to trim the aircraft in, this works about 50% of the time. I tried mapping them to an adjustable knob (AKA: Axis) on the throttle and that doesn’t work at all, it’s either full left full right or centered, but with the knob set to the center if the aircraft loaded in trimmed right it continues to lean to the right even when the trim knob is set to center.
I tried calibrating my stick outside of Falcon (in Windows) and I made sure to center it (hands off the stick) using the button in Falcon. Tried restarting, tried unplugging the hardware and plugging it back in, tried updating my drivers, tried re-installing my drivers. I make sure hands are off-stick when the mission loads too. Doesn’t matter.
Any other creative ideas?
1) Did you get the latest drivers from saitek (not madcatz) page?
- X55_Rhino_7_0_33_91_x64_Software / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_33_91_x64_Software.exe
- X55_Rhino_7_0_32_81_x64_Drivers / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_32_81_x64_Drivers.exe
2) Have you properly calibrated you axes in the HUD software window [CALIBRATE AXES]?
3) After having calibrated and having moved the stick afterwards for test, does it re-center properly after the release?
IF not, your magnet holding “hat” (picture one in link below) might be shaking and throwing it off *:
https://www.benchmarksims.org/forum/showthread.php?18306-Project-X55-GERMANY-%28Mod%29&highlight=germany+modIF OK, have you centered the device (stick) in the UI of BMS itself aswell?
- This mechanical “play” of the magnet carrying “hat” is a reason, why i modded the whole thing.
-
@A.S:
1) Did you get the latest drivers from saitek (not madcatz) page?
- X55_Rhino_7_0_33_91_x64_Software / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_33_91_x64_Software.exe
- X55_Rhino_7_0_32_81_x64_Drivers / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_32_81_x64_Drivers.exe
I did this, no change.
@A.S:
2) Have you properly calibrated you axes in the HUD software window [CALIBRATE AXES]?
I did this too, still no change.
@A.S:
3) After having calibrated and having moved the stick afterwards for test, does it re-center properly after the release?
Yes it does, in the SAITEK software
@A.S:
IF not, your magnet holding “hat” (picture one in link below) might be shaking and throwing it off *:
https://www.benchmarksims.org/forum/showthread.php?18306-Project-X55-GERMANY-%28Mod%29&highlight=germany+modYes, I want, but shipping to Europe is expensive and I am not brave enough to try to mod it on my own. I fried an X52 (non pro, fortunately) trying to upgrade it. Electronics are not my forte. Programming, on the other hand…
@A.S:
IF OK, have you centered the device (stick) in the UI of BMS itself aswell?
Yes, moving the stick in the UI shows full range of motion. Letting it go centers it again perfectly with no problems.
@A.S:
- This mechanical “play” of the magnet carrying “hat” is a reason, why i modded the whole thing.
I hope that’s not the issue, but all I can do now is hope.
-
Well.
In desperation, I removed them from the powered hub. Last flight? Totally level. Go figure.
EDIT:
Nope, still broken on subsequent launch. This is maddening.
EDIT AGAIN:
Cannot explain - I created a NEW keystrokes file and remapped all my keys (no small feat, I assure you). Whatever was in the old keystrokes file was breaking it. If I load it back up, problem comes back. Switch keystrokes file again? Problem resolved. Go figure.
-
Very wicked….from hardware point of view and from test screens it seems your stick is 100% fine.
-
Can you connect them directly to your PC rather than using the USB hub? I found that issue with other joysticks. My USB hub was not providing the signals correctly.
-
EDIT AGAIN:
Cannot explain - I created a NEW keystrokes file and remapped all my keys (no small feat, I assure you). Whatever was in the old keystrokes file was breaking it. If I load it back up, problem comes back. Switch keystrokes file again? Problem resolved. Go figure.
Well, that simply “smells” like input errors or conflicts in your input defintions (keystrokes). In other words your stick is fine and no warranty usage is required (which is good news).
-
Can you connect them directly to your PC rather than using the USB hub? I found that issue with other joysticks. My USB hub was not providing the signals correctly.
Yes, you can connect the X-55 directly to your PC. For some that have ghosting issues, there is an option to use the powered USB hub.
-
Yes, you can connect the X-55 directly to your PC. For some that have ghosting issues, there is an option to use the powered USB hub.
I think he was suggesting I try that (which I did: initially it seemed to work because it reset all my key-binds, but after I restarted the PC it recognized it was the same stick, restored the keybinds, and I had the trim issue again).
@A.S:
Well, that simply “smells” like input errors or conflicts in your input defintions (keystrokes). In other words your stick is fine and no warranty usage is required (which is good news).
Yes indeed, it seems to be just optimum now, except that I am using the BMS file instead of the keystrokes file and I have no idea what some of the controls are.
The thing that confuses me about this is that it seems like the keystrokes file is JUST for keybinds, I don’t understand how it relates to the stick centering, but apparently it does or I wouldn’t have had this issue.
-
Hmm… i am not using keystrokes anymore for my x55… instead BMS DirectX assignments.
-
….
The thing that confuses me about this is that it seems like the keystrokes file is JUST for keybinds, I don’t understand how it relates to the stick centering, but apparently it does or I wouldn’t have had this issue.
:hmmmm: …. that’s not necessarily correct. If there are DX assignments (i.e. direct call backs for the joystick/HOTAS) those are in the keyfile as well. Although not certain, I agree with A.S. that it was some unintended command in the keyfile, which you’ve now eliminated. I’d guess it was something commanding the roll input, not so much a stick centering issue.
@A.S:
Hmm… i am not using keystrokes anymore for my x55… instead BMS DirectX assignments.
I am convinced that this (DX) is absolutely the way to go for joystick/HOTAS programming. Unfortunately it ‘looks’ intimidating and I think people avoid it because they don’t understand it. In reality, especially if you work from Kolbe’s spreadsheet (C:\Falcon BMS 4.32\User\Joystick\Generic\Kolbe\BMS-DX-Generator 1_6.xls), it’s fairly easy to setup and use in most cases.
-
Well I have a new fun glitch for you. Today my keyboard was spazzing out (I thought) the up arrow was stuck. Like, the key was okay, but the computer seemed to think my up arrow was stuck on.
I reached over and nudged my X-55 throttle, and it stopped.
Ghosts in the machine, indeed.
-
Well I have a new fun glitch for you. Today my keyboard was spazzing out (I thought) the up arrow was stuck. Like, the key was okay, but the computer seemed to think my up arrow was stuck on.
I reached over and nudged my X-55 throttle, and it stopped.
Ghosts in the machine, indeed.
Ive had some pretty great ghosts in the machine… my X-65F for the longest time would have random stick inputs. Like, I could take my hand off the stick, watch the setup page, and watch the stick position wander around in the square. Swapped for a new one courtesy the warranty department - no fix. Plugged into a new computer, just fine… but other types of stick worked fine in my rig too.
my working hypothesis is that there is some ungrounded stray voltage somewhere that is present in my USB circuits. Not being a hardware expert, thats my best guess.
Yours I would not accuse of random voltage variances. screwy stick board is the lazy diagnosis.
-
I cannot get the DX mapper application you guys linked me to to work. It spazzes out every time I try to load it.
I’m run Win7 64 Bit, would that be an issue?
-
I hope not. Ive not had any luck with it myself, actually. Win7 64 bit here too.
EDIT: Just loaded it fine here. Guess its not the OS at fault.
-
I hope not. Ive not had any luck with it myself, actually. Win7 64 bit here too.
EDIT: Just loaded it fine here. Guess its not the OS at fault.
Okay, I will give it a run when I get home (I know it will fail) but I will describe for you in obscene detail that will make you want to curse my children exactly what it’s doing and you can tell me what a dumbass I am for not checking the one box that would solve my problem but I don’t even know exists.
-
Okay, I will give it a run when I get home (I know it will fail) but I will describe for you in obscene detail that will make you want to curse my children exactly what it’s doing and you can tell me what a dumbass I am for not checking the one box that would solve my problem but I don’t even know exists.
Most interested in the creation of DX assignments (how) and then how (and where) you’re putting them in your keyfile. The better we understand that, the better we can rule in or rule out a problem with creating the DX commands themselves.
-
Okay. Just got home, I’m on my teamspeak:
ts8.gameservers.com:9132If anyone wants to live chat this through. I opened up Keyfile Editor. I clicked on File -> Load -> I selected sharpe.key (This is the new keyfile I setup, off of the BMS.key when my ketstrokes.key file was causing issues with the trim.
It opened a new window, it’s scanning through things and finding functions assigned to keys and missing functions etc etc. Now it’s stopped. It seems to be locked up. Now the second window closed. Back to the first one. It’s letting me scroll through the list, both the keyboard blue lights are flashing, even when I stop typing. But I can scroll the list. SimEWSModeByp isn’t in the list. I see a green + button, I click it, it adds an option that says SimDoNothing, after a moment a tooltip pops up and says double click to edit. I double click to edit, a new dialog pops up, I start scrolling through the list, I get all the way to the top and the entire application shuts down.
I’m trying it again now. This is really annoying.
EDIT #1: Decided to start with trim because I could actually find it in the tool. This reminds of things I program for myself, utterly clunky and completely not user friendly. I click on trim. It says device assigned. I open the drop down, nothing is there. I click go to, application just shut down again.
Edit #2: Okay, so this time I went back in, it said it found a backup file, I loaded it. I added two new entries: One for trim left, one for trim right. I double click the button assigned field - the keyboard blue lights are flashing again and the ‘key selected’ box (not the right name) has keys flashing in and out of it. I close this window and click on the blue light that is flickering, it instantly stops. I double click the field again and twist my trim knob. Great! it registers. But it says EWS not TRIM for the command so I cancel out of the dialog. I double click EWS again (changing my mind, I know) and this time assign it to a switch. After staring at the confusing default/activate on press and other options for amoment I just close the window. I hit save as. I select sharpe.key. Then I realize there are only three entries in the file now, and I think I might have just over written all my button assignments. That is really going to piss me off. Right on que, the application crashes. This time I get an error log - copy to clipboard, ignore, or close. I copy to clipboard, I hit ignore. Application shuts down.
Technical details: Exception type: System.InvalidOperationException Message: Form that is already visible cannot be displayed as a modal dialog box. Set the form's visible property to false before calling Show. Object members: Message: Form that is already visible cannot be displayed as a modal dialog box. Set the form's visible property to false before calling Show. Data: System.Collections.ListDictionaryInternal InnerException: TargetSite: Void Show(System.Windows.Forms.IWin32Window) StackTrace: at System.Windows.Forms.Form.Show(IWin32Window owner) at Keyfile_editor.Form1.openKeyFileDialog_FileOk(Object sender, CancelEventArgs e) at System.Windows.Forms.FileDialog.OnFileOk(CancelEventArgs e) at System.Windows.Forms.FileDialog.HandleVistaFileOk(IFileDialog dialog) HelpLink: Source: System.Windows.Forms HResult: -2146233079 Comment: Unhandled thread exception in thread "Mainthread" Suspected objects: No suspected objects. Managed threads (workers): Worker: Monitoring thread for keyboard Threadstate: Background, WaitSleepJoin Is finished: True Threadstack: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at Keyfile_editor.JoystickWrapper.DXDevice.InputMonitor(Object data) at Keyfile_editor.ThreadPoolManager.Worker.BeginWork(Object o) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Worker: Monitoring thread for keyboard Threadstate: Background, WaitSleepJoin Is finished: False Threadstack: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at Keyfile_editor.JoystickWrapper.DXDevice.InputMonitor(Object data) at Keyfile_editor.ThreadPoolManager.Worker.BeginWork(Object o) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Worker: Monitoring thread forJoy 1 - F16 MFD 1 Threadstate: Background, WaitSleepJoin Is finished: False Threadstack: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at Keyfile_editor.JoystickWrapper.DXDevice.InputMonitor(Object data) at Keyfile_editor.ThreadPoolManager.Worker.BeginWork(Object o) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Worker: Monitoring thread forJoy 2 - F16 MFD 2 Threadstate: Background, WaitSleepJoin Is finished: False Threadstack: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at Keyfile_editor.JoystickWrapper.DXDevice.InputMonitor(Object data) at Keyfile_editor.ThreadPoolManager.Worker.BeginWork(Object o) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Worker: Monitoring thread forJoy 3 - Saitek Pro Flight Rudder Pedals Threadstate: Background, WaitSleepJoin Is finished: False Threadstack: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at Keyfile_editor.JoystickWrapper.DXDevice.InputMonitor(Object data) at Keyfile_editor.ThreadPoolManager.Worker.BeginWork(Object o) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Worker: Monitoring thread forJoy 4 - Saitek Pro Flight X-55 Rhino Stick Threadstate: Background, WaitSleepJoin Is finished: False Threadstack: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at Keyfile_editor.JoystickWrapper.DXDevice.InputMonitor(Object data) at Keyfile_editor.ThreadPoolManager.Worker.BeginWork(Object o) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Worker: Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle Threadstate: Background, WaitSleepJoin Is finished: False Threadstack: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at Keyfile_editor.JoystickWrapper.DXDevice.InputMonitor(Object data) at Keyfile_editor.ThreadPoolManager.Worker.BeginWork(Object o) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Worker: Threadstate: Background Is finished: True Threadstack: Worker: Threadstate: Background Is finished: True Threadstack: Worker: Threadstate: Background Is finished: True Threadstack: Worker: Threadstate: Background Is finished: True Threadstack: Worker: Threadstate: Background Is finished: True Threadstack: Debug log: 18:50:13:950 - This is the log-file created by Keyfile editor 0.0.1.0 for debugging reasons. If you encounter a bug you should include this file in the bug-report. 18:50:13:983 - Running on: Microsoft Windows NT 6.1.7601 Service Pack 1 18:50:14:7 - Culture: en-US 18:50:14:32 - Program started. 18:50:14:132 Mainthread - Loading mainform on thread:Mainthread 18:50:14:179 Mainthread - FunctionDialog.BeginInit on thread:Mainthread 18:50:14:209 Mainthread - Begin work: InitTreeViewThread 18:50:14:233 Mainthread - Finished FD begininit on thread:Mainthread 18:50:14:234 - InitTreeViewThread worker starting. 18:50:14:285 Mainthread - Constructing JoystickWrapper... 18:50:14:287 InitTreeViewThread - Populating TreeView... 18:50:14:352 InitTreeViewThread - Finished populating treeview on thread:InitTreeViewThread 18:50:14:383 InitTreeViewThread - InitTreeViewThread worker have returned. 18:50:14:660 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:14:686 Mainthread - Setting up keyboard on thread:Mainthread 18:50:15:103 Mainthread - Begin work: Monitoring thread for keyboard 18:50:15:124 - Monitoring thread for keyboard worker starting. 18:50:15:149 Mainthread - Finished setting up keyboard on thread:Mainthread 18:50:15:184 Mainthread - Getting all device bindings on thread:Mainthread 18:50:15:207 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:15:601 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:15:659 Mainthread - Begin work: Monitoring thread forJoy 1 - F16 MFD 1 18:50:15:682 - Monitoring thread forJoy 1 - F16 MFD 1 worker starting. 18:50:15:707 Mainthread - Getting all device bindings on thread:Mainthread 18:50:15:732 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:15:783 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:15:853 Mainthread - Getting all device bindings on thread:Mainthread 18:50:15:874 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:16:272 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:16:343 Mainthread - Begin work: Monitoring thread forJoy 2 - F16 MFD 2 18:50:16:374 - Monitoring thread forJoy 2 - F16 MFD 2 worker starting. 18:50:16:390 Mainthread - Getting all device bindings on thread:Mainthread 18:50:16:407 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:16:424 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:16:485 Mainthread - Getting all device bindings on thread:Mainthread 18:50:16:507 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:16:856 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:16:888 Mainthread - Begin work: Monitoring thread forJoy 3 - Saitek Pro Flight Rudder Pedals 18:50:16:907 - Monitoring thread forJoy 3 - Saitek Pro Flight Rudder Pedals worker starting. 18:50:16:924 Mainthread - Getting all device bindings on thread:Mainthread 18:50:16:940 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:16:957 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:16:995 Mainthread - Getting all device bindings on thread:Mainthread 18:50:17:24 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:17:353 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:17:420 Mainthread - Begin work: Monitoring thread forJoy 4 - Saitek Pro Flight X-55 Rhino Stick 18:50:17:440 - Monitoring thread forJoy 4 - Saitek Pro Flight X-55 Rhino Stick worker starting. 18:50:17:457 Mainthread - Getting all device bindings on thread:Mainthread 18:50:17:473 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:17:499 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:17:557 Mainthread - Getting all device bindings on thread:Mainthread 18:50:17:573 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:17:970 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:18:37 Mainthread - Begin work: Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:18:57 - Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle worker starting. 18:50:18:82 Mainthread - Getting all device bindings on thread:Mainthread 18:50:18:98 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:18:115 Mainthread - Constructing DXDevice on thread:Mainthread 18:50:18:169 Mainthread - Getting all device bindings on thread:Mainthread 18:50:18:190 Mainthread - Finished getting all devicebindings on thread:Mainthread 18:50:18:362 Mainthread - JoystickWrapper constructed. 18:50:18:468 Mainthread - Finished load mainform on thread:Mainthread 18:50:18:512 Mainthread - UndoHandler: File: Temporary.key 18:50:20:35 Mainthread - Begin work: HistoryWriter 18:50:20:58 - HistoryWriter worker starting. 18:50:20:89 HistoryWriter - HistoryWriter worker have returned. 18:50:23:618 Mainthread - Begin work: Load keyfile thread 18:50:23:649 - Load keyfile thread worker starting. 18:50:23:674 Load keyfile thread - Load keyfile thread started 18:50:23:696 Load keyfile thread - File size: 227 18:50:23:717 - AsyncReadCallback 18:50:23:740 - Completed read. Amount read: 227 18:50:23:757 - Finished reading. 18:50:23:774 - 227 bytes read. 18:50:23:799 - File closed. 18:50:23:815 - Text buffer now: 227 characters long 18:50:23:832 - Setting waithandle 18:50:23:892 Load keyfile thread - Full match: SimEWSModeByp - Joy 5 Button 18 18:50:24:11 Load keyfile thread - MarkAllConflicts... 18:50:24:33 Load keyfile thread - MarkAllConflicts returning. 18:50:24:72 Load keyfile thread - Updating shift buttons on thread:Load keyfile thread 18:50:24:91 Load keyfile thread - Not found HOTASPinkyShift... 18:50:24:107 Load keyfile thread - hidden. 18:50:24:124 Load keyfile thread - Joy 1 - F16 MFD 1 hidden. 18:50:24:140 Load keyfile thread - Joy 1 - F16 MFD 1 <shifted>hidden. 18:50:24:157 Load keyfile thread - Joy 2 - F16 MFD 2 hidden. 18:50:24:183 Load keyfile thread - Joy 2 - F16 MFD 2 <shifted>hidden. 18:50:24:207 Load keyfile thread - Joy 3 - Saitek Pro Flight Rudder Pedals hidden. 18:50:24:223 Load keyfile thread - Joy 3 - Saitek Pro Flight Rudder Pedals <shifted>hidden. 18:50:24:240 Load keyfile thread - Joy 4 - Saitek Pro Flight X-55 Rhino Stick hidden. 18:50:24:257 Load keyfile thread - Joy 4 - Saitek Pro Flight X-55 Rhino Stick <shifted>hidden. 18:50:24:273 Load keyfile thread - Joy 5 - Saitek Pro Flight X-55 Rhino Throttle hidden. 18:50:24:299 Load keyfile thread - Joy 5 - Saitek Pro Flight X-55 Rhino Throttle <shifted>hidden. 18:50:24:323 Load keyfile thread - Finished updating shift buttons on thread:Load keyfile thread 18:50:24:340 Load keyfile thread - UndoHandler: File: sharpe.key 18:50:26:765 Load keyfile thread - Begin work: HistoryWriter 18:50:26:782 - HistoryWriter worker starting. 18:50:26:785 Mainthread - Load keyfile thread exiting. 18:50:26:816 Load keyfile thread - Load keyfile thread worker have returned. 18:50:26:799 HistoryWriter - HistoryWriter worker have returned. 18:50:41:976 Mainthread - Begin work: Load keyfile thread 18:50:42:6 - Load keyfile thread worker starting. 18:50:42:30 Load keyfile thread - Load keyfile thread started 18:50:42:47 Load keyfile thread - File size: 227 18:50:42:64 - AsyncReadCallback 18:50:42:80 - Completed read. Amount read: 227 18:50:42:97 - Finished reading. 18:50:42:115 - 227 bytes read. 18:50:42:139 - File closed. 18:50:42:155 - Text buffer now: 227 characters long 18:50:42:172 - Setting waithandle 18:50:42:214 Load keyfile thread - Full match: SimEWSModeByp - Joy 5 Button 18 18:50:42:303 Load keyfile thread - MarkAllConflicts... 18:50:42:331 Load keyfile thread - MarkAllConflicts returning. 18:50:42:356 Load keyfile thread - Updating shift buttons on thread:Load keyfile thread 18:50:42:372 Load keyfile thread - Not found HOTASPinkyShift... 18:50:42:389 Load keyfile thread - hidden. 18:50:42:405 Load keyfile thread - Joy 1 - F16 MFD 1 hidden. 18:50:42:422 Load keyfile thread - Joy 1 - F16 MFD 1 <shifted>hidden. 18:50:42:448 Load keyfile thread - Joy 2 - F16 MFD 2 hidden. 18:50:42:472 Load keyfile thread - Joy 2 - F16 MFD 2 <shifted>hidden. 18:50:42:489 Load keyfile thread - Joy 3 - Saitek Pro Flight Rudder Pedals hidden. 18:50:42:505 Load keyfile thread - Joy 3 - Saitek Pro Flight Rudder Pedals <shifted>hidden. 18:50:42:522 Load keyfile thread - Joy 4 - Saitek Pro Flight X-55 Rhino Stick hidden. 18:50:42:539 Load keyfile thread - Joy 4 - Saitek Pro Flight X-55 Rhino Stick <shifted>hidden. 18:50:42:556 Load keyfile thread - Joy 5 - Saitek Pro Flight X-55 Rhino Throttle hidden. 18:50:42:580 Load keyfile thread - Joy 5 - Saitek Pro Flight X-55 Rhino Throttle <shifted>hidden. 18:50:42:597 Load keyfile thread - Finished updating shift buttons on thread:Load keyfile thread 18:50:42:614 Load keyfile thread - UndoHandler: File: sharpe.key 18:50:42:630 Load keyfile thread - Begin work: HistoryWriter 18:50:42:647 - HistoryWriter worker starting. 18:50:42:649 Mainthread - Load keyfile thread exiting. 18:50:42:665 HistoryWriter - HistoryWriter worker have returned. 18:50:42:682 Load keyfile thread - Load keyfile thread worker have returned. 18:50:49:562 Mainthread - lv_MouseDown on thread:Mainthread 18:50:49:813 Mainthread - ListViewMouseUp on thread:Mainthread 18:50:51:289 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button pressed on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:51:307 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button pressed on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:51:330 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button pressed on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:51:555 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button pressed on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:51:776 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button released on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:52:497 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button released on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:54:623 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button pressed on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:55:39 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button released on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:56:255 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button pressed on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:56:773 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button released on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:57:905 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button pressed on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle 18:50:58:422 Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle - Button released on thread:Monitoring thread forJoy 5 - Saitek Pro Flight X-55 Rhino Throttle</shifted></shifted></shifted></shifted></shifted></shifted></shifted></shifted></shifted></shifted>
EDIT: #4:
I restart the application. This is #4 in case you aren’t counting along with me. The application starts up, it says DO YOU WANT TO LOAD BACKUP. I say NO THANK YOU but I don’t really say THANK I have another four letter word there instead. The application opens, the search screen comes up searching for inputs. It stops at four. And then goes away. I close and reopen the application (#5) no back up prompt this time. Loading keyfile comes up. It gets to four. The application crashes.I am restarting the application (#6). This time the same thing as above happens, except it doesn’t crash. Now my keyfile is loaded with three things in it. I’m giving up. Life is not worth living if this is the kind of thing I have to do to bind the BYPASS switch to my X55. Goodbye cruel Falcon coder world, you have bested me. Just kidding. Except I am giving up. But only on this piece of kludge.
EDIT #6:
Keybinds are all gone. I am beyond enraged. -
Id probably look at making the keyfile through the BMS UI if its giving you that much hassle. How many binds do you need to map?
The way I got mine set up was I saved a copy of the keyfile I wanted (Kolbe’s) and loaded the copy in BMS, then assigned bindings by clicking on the command and then pressing the DX button. After assigning all the keybindings, I saved the file, and opened it with a text editor. I copied the bottom section of the keyfile that was created by BMS, into the original document, and saved it.