X-55 Aircraft Starts Every Mission Trimmed to the Extreme Right
-
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).
-
@A.S:
- 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.
I am not sure what to say here - when I went into the software, the X axis was off by a few pixels. As I have plugged them in and unplugged them constantly, I re-calibrated them. Now it’s centering properly. I did the test you ask, moved it around and let it recenter, it’s snapping back correctly now. I’ve done this for twenty minutes without any hint of it not being centered when it comes back to the middle.
I wasn’t sure what was going on, so I did a quick dogfight. Nailed 7 fighters and then flew through a fireball and my Jet was going to explode, so I quit the sim. I went back to the calibration panel, unfortunately, it’s a little bit off. So I went back in the game, this time it’s trimming left. No matter how much counter trim I give it, there is always a pronounced left trim. Not sure why it was going right before, but whatever.
This strongly indicates to me a hardware problem - but the stick was previously trimming to the right, so I am not sure what to think.
EDIT:
I loaded up a new Keystrokes file (BMS). Jet is flying level again. -
If the stick off centers (in the HUD test software ie) then it is a hardware problem - caused by a “mechanical play” (click pic).
THIS particular issue is a reason why i personally came up with this solution (mod)
If it is a constant “bank” or “trim” input, then it is either a hardware problem - which can be checked for false inputs in the control panel of Windows -
or it is really just a conflict in your BMS input key-assigments.
As this constant “bank” or trimm happnes randomly …it almost sounds like an unintented electric contact (wires torn off ie.) causing a false input
or 2 device-axes assigned as “roll” axis on jet - thus conflicting.IF everything is “ok” in your device-control application (outside of sim), then you are lucky…because then you don´t need to send it back to warranty appartment as it is not a hardware issue and we can start localizing the issue inside BMS. I also can sent you my DX x55 assignments with enough pictures and elaborations …but then i first need to know if windows pics your x55 up as device 1 or device 2, so i can adjust the values in the key-file before i sent it over to you as a test-plattform (as you can see in my case stick is device 2 and thruttle device 3 as my rudder pedal is device 1 in OS).