X55 keyfile -BMS -Full DX Programmed
-
Snelle, I just wanted to thank you for your hard work and dedication. I’ve struggled with X55 and BMS for some time. Then I found your post, I knew nothing about DX programming but followed the posts and read your instructions. Turned out my joystick throttle was ID swopped, but my rudder pedals (Milan) seems to have taken the first numbers so I used IDS version and renumbered the throttle unit buttons. Works a dream!
My only issue is my mini stick only seems to want to go up and left, probably hardware issue, I’ll see if I can change the cursor control to the current trim hat.
Thanks again!
Worther_1Sent from my Nexus 7 using Tapatalk
-
My only issue is my mini stick only seems to want to go up and left, probably hardware issue, I’ll see if I can change the cursor control to the current trim hat.
No other HUD profile active?
I assume you allready re-installed and recalibrated the X-55, else it is indeed probably hardware related.
EDIT :I wonder if it could be due to registry error of X-55?? If a reg-fix patch can make the cursor alive, is sure could malfunction easily to.
Look at the reg-fix inside and examine your registry if all content made it into the registry.
You have hardware conflict? check device manager.
Perhaps try delete all registry setting of X-55 manually, un-install and then re-install with Administrator privilige, after that apply reg-fix.It that does not help I would program the cursor on the H3 or H4. From the main page you can download an older version 3.0 developed before mouse x/y fix and with mouse programmed on H3.
You could use it as reference.
Good luck!-sorry for editing this answer a few times over.
-
Hi Snelle, thanks for reply. I had no HUD profile running, not even the speed break one. As for the recalibrate advice, would you recommend doing that in Windows (I’m running Win10) or HUD software?
I’ll check device manager tomorrow.
Thanks again, everything else works great.
BTW as my joystick is at address 30 something +, and throttle is at 60 something +, do the shifted button address’s need changing? Hope you can understand this I can’t remember exact DX address’s.Worther_1
Sent from my Nexus 7 using Tapatalk
-
Recalibrate in windows, in HUD the x/y mouse is not recognized. Do the re-installation of Saitek’s, and next try eliminating as much hardware as you can to get a grip on it, perhaps even installing on another machine just to get verified if it is software issue or hardware conflicting, or hardware failure.
Your DX numbering in keyfile should match deviceorder in windows, so stick=#2 and should there for starts with 32-63, throttle=#3… 64-95, so that matches your findings.
The shifted buttons also need to match device order: ad 256 for the numbering. Look in a keyfile for an example. btw shiftstate offset is standard set at 256 in BMS config. -
Hi Snelle, the recalibration helped but I still experienced substantial drift from the cursor so I reverted to your V3.0, with your instructions I even managed to modify it to suit me better. So thanks for all you help.
Worther_1
Sent from my Nexus 7 using Tapatalk
-
Everything works good on my stick, but nothing works on my throttle.
-
Everything works good on my stick, but nothing works on my throttle.
Please be more specific.
-
The key inputs on my flight stick match what they’re supposed to do. The button in the CMS position does slapswitch, the gray hat does DMS, etc. However none of the buttons on the throttle seem properly mapped. The sim recognizes their input, but they’re not tied to specific functions. Also had a hard time mapping my axis, I couldn’t unmap pitch and roll from my throttle. Restarted everything and it freed that up, but my top rotary won’t map as an axis to radar range. I can tweak that stuff later, but the DX file doesn’t link itself to my throttle, just my joystick. Really weird.
-
Hhhhmmm,
Can I assume you have the current drivers loaded? Saiteks seem finicky about drivers.
Can you map the throttle axis?
You mention rotary one, is rotary 2 working?
Are you by chance trying to run through a USB hub? If so, try direct to pc -
Hhhhmmm,
Can I assume you have the current drivers loaded? Saiteks seem finicky about drivers.
Can you map the throttle axis?
You mention rotary one, is rotary 2 working?
Are you by chance trying to run through a USB hub? If so, try direct to pcI am running current drivers, BUT the first time I installed them I had already plugged joysticks in. Second time I re-ran the exe with them unplugged and waited for the prompt to plug them in. I didn’t delete the drivers first, just reinstalled over them. Still not working, so going to try deleting, unplugging, installing, then plugging them in.
I’m able to map the throttle axis but only after selecting down or side to side for the yaw and roll deadzone. Most recent attempt couldn’t map those to any other position. Sold my Warthog for a bit of cash and these, because I feel they’re better suited for the F16. Frustrating. No usb hubs. Rotary G is detected and works in game for radar elevation. Rotary F can be mapped, but doesn’t affect radar range. FCR, specifically….which I’m wondering if it should or just HSD?
OH…I also have Saitek rudder pedals which I have not unplugged. That just gave me an ah-ha moment. I wonder if the DX is set for 1&2 and by leaving my pedals plugged in the throttle is being assigned to #3?
EDIT: That’s what it was. Detecting throttle keys now, must have been too many saitek controllers plugged in wrong order.
-
Cam I make one suggestion? Maybe a Shift TMS UP for the AA on the ICP, and Shift TMS Down to Cycle A/G weapons?
-
I can tweak that stuff later, but the DX file doesn’t link itself to my throttle, just my joystick. Really weird.
It is almost for certain that your PC and hardware configuration are not matching the device order as explained in documentation, your rudder most likely mixed them up. Once configured it does not matter if you unplug it, the next devices will be added accordingly in windows i.e.
I assume in windows all buttons respond , i.e. in hardware device?
What specific type of key file did you load in BMS?
What excact respond does throttle buttons give in BMS UI?
Did you try to understand the documentation?, because it probably holds the solution to your misconfig. -
It is almost for certain that your PC and hardware configuration are not matching the device order as explained in documentation, your rudder most likely mixed them up. Once configured it does not matter if you unplug it, the next devices will be added accordingly in windows i.e.
I assume in windows all buttons respond , i.e. in hardware device?
What specific type of key file did you load in BMS?
What excact respond does throttle buttons give in BMS UI?
Did you try to understand the documentation?, because it probably holds the solution to your misconfig.I read all the documentation. I just disconnected the rudder pedals and it worked fine. I’ll just use the twist grip until I can find time to reorder things.
Thanks for the profile. It would be awesome for those with track IR to use the hat for views to change waypoints and cycle hardpoints. Perfect then
-
It would be awesome for those with track IR to use the hat for views to change waypoints and cycle hardpoints. Perfect then
I might have a slightly different view on perfect, but that is ok to me You are free to adjust it for to your own likings.
Cheers and have fun. -
How would I edit it, since you can’t save it in the UI?
-
How would I edit it, since you can’t save it in the UI?
It is all much simpler then most think it is.
Open the key file with notepad and look at bottom section where all the magic is stored.
With someknowledge of DX programming you can also make the adjustmenst and keep you rudder attached.
Suggest you study the documentation of my keyfile and understand every word of it as a start.
Also do read the BMS keyfile manual and BMS keystrokes.pdf in docs section. -
I found this page a useful place to start as well: https://www.benchmarksims.org/forum/content.php?153-DirectX-Shifting-Facility
But personally I don’t need it anymore, as thanks to Snelle, I have a brilliant set of x55 mappings that I could get working in 10 minutes! (partly thanks also to my previous knowledge about stick/throttle ID’s and all the messing about I’d done with DX functions for my 4.32 keyfile) even my SLD switch and ministick now have a purpose
You sir, have saved me countless hours of headaches. Too bad I can only thank you once.
-
I’ve been continuing to fly with this profile for several months and am still loving it. I wanted to share some experience with it. I dran into a problem in a multiplayer flight a few weeks ago. During taxi I had to rapidly apply my wheelbrakes a few times due to unexpected deceleration from my flight lead. By the time I lined up on the runway my speedbrakes were slightly open (I apparently wasn’t giving the shift button enough time before pressing the wheelbrake button, and was instead just slightly opening the speedbrakes each time). I failed to recognized this and started my takeoff roll. I realized something was wrong, but by the time I had the speedbrakes retracted I was out of runway and crashed. Using the slider for speedbrakes is not ideal, as it doesn’t allow you to have fine control over opening / closing them which you need to AAR. I removed speedbrake open / close from the buttons H and I and rebound speedbrake open and close to forward and back on the upper throttle hat (the one labelled EWS) which originally would cycle countermeasure programs and modes. I removed the mode select from the hat as I don’t believe it is really on a HOTAS control in the jet, and I never found myself using it. This is also a similar location to the speedbrake switch in the jet. Now I have unshifted H bound to wheelbrake and unshifted I bound to trackIR recenter.
-Rabbit
-
@Rabbit: Though your setup seems perfectly reasonable, and is similar to what I was using in 4.32, isn’t Spdbrk open/close already bound unshifted to the two buttons on the front of the throttle? I’ve just used the slider since finding Snelle’s profile…
-
During taxi I had to rapidly apply my wheelbrakes a few times due to unexpected deceleration from my flight lead. By the time I lined up on the runway my speedbrakes were slightly open (I apparently wasn’t giving the shift button enough time before pressing the wheelbrake button, and was instead just slightly opening the speedbrakes each time).
-RabbitWith wheelbraking the nose dive is hard to miss imho, or when it does not occur u are not braking , anyway a cross check of the jet is mandetory before take off.
I agree that using buttons for a wheel brake is a significant trade off for not using feetrudder with brakes, but whatever button u use -including the feetrudder-the scenario remains the same.
At initial profiles the wheelbrake where located at shift/paddle, this would still be my first choice but unfortunately this gave throttle issues and I have no clue if that issue was solved in U1.