X-55 Aircraft Starts Every Mission Trimmed to the Extreme Right
-
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.
-
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?
Well the X-55 Stick, and the X-55 Throttle, the Cougar MFD’s, the Rudder Pedals.
It adds up.
The problem is I’d like to be able to bind SimEWSbypas so I can put countermeasures in manual mode for dogfight (because dogfights force you to reset the jet every time you spawn in) and that is not a native function to the sim.
]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.
I may have to go to text-editing the file to figure this crap out.
-
Well, the function is not included in the bms.key file.
it is included in Kolbe’s keyfiles, which are included in your install, at yourfalconinstall\User\Joystick\Generic\Kolbe\BMS Keystroke Files.
SimEWSModeByp 33 -1 -2 0 0x0 0
replace the 33 with the number of the joystick button you want to press. Sequential, in order, add one (or is it subtract one?) from the falcon setup number.
-
Well, the function is not included in the bms.key file.
it is included in Kolbe’s keyfiles, which are included in your install, at yourfalconinstall\User\Joystick\Generic\Kolbe\BMS Keystroke Files.
Okay. So if I copy it out of there and put it into my keyfile, I can map it through the UI, correct?
-
well if you copy it out of there and put it into your keyfile, you shouldnt need to map it through the UI.
Its subtract one incidentally. So go to the falcon setup UI, press the button you want to map to the bypass switch, note the number it displays.
subtract one from that number, then replace the ‘33’ in the line of text with that number, then add that line to the end of your keyfile.
save the keyfile, run BMS, and it should work.
WAIT ONE You will need to add another line before that one…. standby
Somewhere before that line add this line as well:
SimEWSModeByp -1 0 0XFFFFFFFF 0 0 0 1 "CMDS: MODE Knob - BYP"
-
Basically the file is very simple - it has two different types of lines, first key callbacks, that bind a keyboard combination to a callback (command), and then DX button assignments, that bind a DX button to a callback.
SimEWSModeByp -1 0 0XFFFFFFFF 0 0 0 1 "CMDS: MODE Knob - BYP"
This is a key callback. It doesnt actually bind any key combination to this command, but it needs to be in the keyfile before the next line.
SimEWSModeByp 33 -1 -2 0 0x0 0
This is the directx button assignment. It tells the sim that when you press button number 33 (or 34 depending on how you count - starting from 0 or from 1), you want to send the callback simEWSmodebyp - as you might have guessed.
Thats the short version. The long version is explained VERY well in the manual in your install folder, at C:\Falcon BMS 4.32\User\Joystick\Generic\Kolbe
-
Okay. So if I copy it out of there and put it into my keyfile, I can map it through the UI, correct?
well if you copy it out of there and put it into your keyfile, you shouldnt need to map it through the UI.
….
Somewhere before that line add this line as well:
SimEWSModeByp -1 0 0XFFFFFFFF 0 0 0 1 "CMDS: MODE Knob - BYP"
Yes, I was just going to post this.
If you put that line (that BW just posted) into your keyfile (copy and paste via notepad or similar), it will add the bypass command with ‘no key assigned’. Then in SETUP –> CONTROLLERS, find that item, click to highlight it, then push whatever button on your HOTAS you want to assign. Now the Bypass should be associated with that HOTAS button/switch/knob. You can confirm it by pressing any other HOTAS button, BMS will recognize that command, then press the HOTAS button you just assigned to ‘Bypass’ and BMS should show that as being the recognized command.
Note that these actions have NOT assigned a keyboard key press to that command. It should still show as ‘no key assigned’. If you want to assign a key press to that command, do the same things EXCEPT when you highlight the command, press the key (or key combination) onthe keyboard you want to use for ‘Bypass’.
-
These actions will have assigned a joystick button press to that command however, which was the aim…
-
Yeah I don’t think I really care if they have a keyboard assignment anyway. I don’t use my keyboard for anything anymore, but not because of the HOTAS more because of the Cougar MFD panels. There’s just nothing left to use the keyboard for. Anything that I would otherwise use the keyboard for, I just do with the mouse.
-
Yeah I don’t think I really care if they have a keyboard assignment anyway. I don’t use my keyboard for anything anymore, but not because of the HOTAS more because of the Cougar MFD panels. There’s just nothing left to use the keyboard for. Anything that I would otherwise use the keyboard for, I just do with the mouse.
Thats my approach : )
-
These actions will have assigned a joystick button press to that command however, which was the aim…
Yep, thanks, I think I said that ….
…. Now the Bypass should be associated with that HOTAS button/switch/knob. …
I was merely attempting to elaborate on what you’d added …. to add some ‘what’ you your ‘how’.
-
I appreciate all the help guys, I really do. I will play around with this next week sometime (Busy until then) and let you know what the results are.
I’m still having a ton of trouble with the UI in BMS. Right now when I try to bind keys, I press the keyboard command (like F3) that I know works for changing radar range, and it doesn’t scroll to it in the list. If I launch instant action, this works just fine. If I find it in the list, it says F3 is assigned. But I am having to manually find everything to map and it is seriously pissing me off.
Additionally the knobs on the throttle - which I would LIKE to use to set trim - are acting Fixed - IE: They are either full on or full off, and if I play with it for twenty minutes I can get it set to the middle using the advanced panel in the UI, but forget about trying to use them.
-
I appreciate all the help guys, I really do. I will play around with this next week sometime (Busy until then) and let you know what the results are.
I’m still having a ton of trouble with the UI in BMS. Right now when I try to bind keys, I press the keyboard command (like F3) that I know works for changing radar range, and it doesn’t scroll to it in the list. If I launch instant action, this works just fine. If I find it in the list, it says F3 is assigned. But I am having to manually find everything to map and it is seriously pissing me off.
Additionally the knobs on the throttle - which I would LIKE to use to set trim - are acting Fixed - IE: They are either full on or full off, and if I play with it for twenty minutes I can get it set to the middle using the advanced panel in the UI, but forget about trying to use them.
I really wish I had an X55 so I could better understand how it works with BMS - what switches/buttons/knobs BMS ‘sees’ and which is doesn’t, which have good functionality for DX and which might be better/necessary as key-stroke emulation, for example. I hated to see the post you made last night about the difficulty you were having. As it is, many of us (myself for sure) can only provide generalities without knowing how to apply them specifically to your case.
-
I really wish I had an X55 so I could better understand how it works with BMS
Me too. Me too. You would be way more helpful.
I really wish I had an X55 so I could better understand how it works with BMS - what switches/buttons/knobs BMS ‘sees’ and which is doesn’t, which have good functionality for DX and which might be better/necessary as key-stroke emulation, for example.
If I could think of a good way to share this info with you via screenshots I might try. There are a about 12 axis that I end up with when I pull down one of the advanced drop downs, some of them are tied to the various knobs but it is almost painfully unclear which ones. I can’t even read them all because they are longer then the input field is.
I hated to see the post you made last night about the difficulty you were having.
Well, I tried to ham up my narrative a little to make it less painful, which helped me also be less frustrated.
As it is, many of us (myself for sure) can only provide generalities without knowing how to apply them specifically to your case.
I’m aware, and once again, I greatly appreciate the help.
-
Ooook… after watching your suffering…i feel bad for you.
What exactly is your problem…maybe i can help (x55 on DX here and no issues).
-
I really wish I had an X55 so I could better understand how it works with BMS - what switches/buttons/knobs BMS ‘sees’ and which is doesn’t, which have good functionality for DX and which might be better/necessary as key-stroke emulation, for example.
A picture might help - from my profile
3 directx axis on the stick (I don’t use the rudder)
6 directx axis on the throttle (all visible and assigned in my case)
all buttons and hat switches beside speed-break-lever, mode-switch and the mouse-nipple can be directx bound (non dotted lines), the metal switches all have two directx positions up/down w/spring to normal, the wheel on the left side of the throttle is actually a two button endless-mouse-wheel thing(if you chose to re-program a button to a character function you lose that directx button’s functionality - as I’ve did for JFS/Idle detent to add a hold-one-second requirement)
-
@A.S:
Ooook… after watching your suffering…i feel bad for you.
What exactly is your problem…maybe i can help (x55 on DX here and no issues).
I’m having three intermittent problems:
First, sometimes the aircraft starts out in flight with a balanced load trimmed to the right. Sometimes this doesn’t happen, but over the course of the flight the trim becomes worse and worse until I am holding full stick left just to keep the jet in a 5 degree right hand bank.
Second, the two grey knobs on my X-55 base are registering almost as a three way switch. All the way on, all the way off, or, if I play with it for twenty minutes, somewhere in the middle.
Third, the least important and probably already resolved with some recent posts, for dogfighting I want manual chaff/flare drops and want to bind SimEWSBypass which is not in the normal key config files. But I should be able to get around that.
I am not using the Saitek software to bind, all my keybinds have been in the Falcon UI. Currently the stick is setup plugged directly into the PC. I have a powered USB hub, I ran it through the powered USB hub and I still had all of the above problems. Saitek Software, Windows, and Falcon all show the stick as properly centered, I have a full range of motion.
I have partially solved the trim issue by creating a new keybinds file, but it still crops up sometime midway through a flight.
-
Before i go to 2) and 3)
- as this problem occurs in flight… so, please go to your HUD software (where you can see the joystick response)
… move your stick around for a while… let it go (recenter) and then look if it DOES re-center properly - without deadzone - or it it sometimes is OFF-CENTER (check Y and X axis). And let me know please.
If it centers …we can move to 2) and 3) … if not …i know what the issue is, as this is a typcial x55 construction fault (trash or warranty).