X-65F Keyfile
-
So, I was deleting some christmas gifts I bought people from my Amazon (UK edition) browsing history so I would starting seeing suggestions relevant to myself rather than my sister, and lo and behold, there were 7 X-65F joysticks in stock. I thought they were completely gone so obviously I had to buy one.
However, I’ve hit a snag and while the solution seems simple enough, I don’t like the solution and I’m wondering if I’m just being thick. I’ve been trying for about a day now to get a proper keyfile setup using the keyfile editor, but it seems only buttons 32 and down are recognized. I was under the impression that while Windows only allows 32 DX buttons, BMS supports something like 512 buttons, they just end up on a different DX device. However, it seems to not be working as I expect, and having looked at several X-65F keyfiles and profiles, it’s becoming clear to me that there isn’t a solution to this, as all of them appear to use the (bloody awful) Saitek profiler for the last Hat, the K-switch (two-way rocker) and the button box.
Is this the only solution or is there a way to make BMS recognize the final buttons?
-
If you work out a way to get the last few buttons recognised by windows as being on a second, virtual device, let me know?
I screwed with that for ages. My solution was to have a profile for the mode select switch, the last hat, the K switch and the box, and to set the ministick to do nothing as part of the profile; I then had the ministick set as a pair of axes, and the rudder set as a 9th axis (and so not recognised by BMS) - and the keyfiles set in BMS for all the directX buttons, and the keypresses that were set up in the Saitek profile for all the other buttons.
-
So I’m not sure what is so awful about a tool that make it easy to configure your X-65 and the million button options AND get them all working properly for ANY game. But we all have our tastes Im sorry things have not worked for you.
But I will assume you are just having problems working out some of the things you are seeing. So i will share some things that made things work like a charm.
So first of all you need 2 files and some registry entries to make things work properly. All of which can be gotten from ZELEGENDS web site. (with one caveat)
1. You will need the .pr0 file for your profile editor.
2. you will need the .key file to add to BMS. (if you use the ZELEGEND key file make sure that you make a change outlined in my CAVEAT section)
3. you will need registry entries to tie the thumb jostick as an axis (works hella better than key presses) it will take away either one of your throttle axis (the throttle has 2 you really only need one. I took away the rudder axis on the stick (my preference).)CAHEAT!! From my old email to someone.( i got help form BMS team member, IM SORRY i dont have your email/name. But it was his work that fixed the key file, you know who you are. Thank you.)
Use the stuff below and make a new .key txt file. Basically the zelegend file has some non U.S. keys that when you try to load in a U.S. computer BMS crashes. the entry was 0x56 which is HEX for a key on your keyboard. I think I replaced all of them with 0x58 which is F12 key. or something that was not already defined.
I looked up on the BMS docs what these freaking 0xXXX meant:
here is a snipit of it.
F11 87 0x57
F12 88 0x58
F13 100 0x64
F14 101 0x65
F15 102 0x66In order to make it work i load up the x-65F profile .pr0 file then go into BMS. In BMS I load up the .key file attached. You will have to map a couple of thing in BMS like Counter measures. If you have Track IR you will need to set the TrackIR reset keys to something other than F12 as it will conflict with the BMS .key file.
Hope This helps!
-
Short version is that its hard to get working and crashes for no reason, refuses to load files, refuses to edit files, refuses to play nicely with the other programs…
the other problem is that you can only assign keyboard commands using it. Which is a bit of a problem, as about the only good thing about keyboard commands is that there is a few more of them than there are DX key slots.
Out of the two, for some people the former problem is not a concern - the latter is always a problem.
-
@BlueWolf… it has never once crashed on me nor do i have issues loading profiles. I typically swing from BMS, to DCS (FC3, A-10, And BS2), with no issues. But i suppose everyones setup is different.
When you talk about key commands… are you talking about making macros? or for things like moving your cursor in the hud? or the range knobs? those all work as axis on my setup. Buttons, well they map to buttons which is not so bad.
I guess what I’m trying to say is, maybe I can help? Or not. or whatever?
-
Sure, possibly? If you could show me a way to get the X-65F to always load profiles, and to not crash loading existing profiles, that would be awesome.
Just as awesome would be the ability to map all the buttons on the stick to DirectX buttons, and the ability to map all the axes on the stick to directX axes.
For the keyboard commands, I was talking about the buttons yes. The buttons on the stick can only be assigned to keyboard commands, which is kinda a bad thing…