Kolbe's Key File Editor issues
-
I cannot seem to locate the article on DX shifting that is referred to in Kolbe’s key file manual. I know it used to be on the opening page of the BMS web site, but it seems to have disappeared.
“The DirectX button numbers in the BMS UI are shown as Windows DX numbers. From reading the DirectX Shifting Facility Article you should remember that BMS counts DX button numbers slightly different than Windows.”
-
I cannot seem to locate the article on DX shifting that is referred to in Kolbe’s key file manual. I know it used to be on the opening page of the BMS web site, but it seems to have disappeared.
“The DirectX button numbers in the BMS UI are shown as Windows DX numbers. From reading the DirectX Shifting Facility Article you should remember that BMS counts DX button numbers slightly different than Windows.”
None of the articles are up. Some (apparently) weren’t up-to-date for 4.33 and others, from what I’ve read, are now covered in the new manuals.
-
Can anyone post a copy of the original article?
-
Can anyone post a copy of the original article?
I’m am pretty sure (Kolbe would know for absolute certainty) that the content of that article has been incorporated into the updated keyfile documents provided in the Docs folder of the install.
If I had a copy, I’d gladly post, but unfortunately only have a saved link/bookmark.
-
I’m am pretty sure (Kolbe would know for absolute certainty) that the content of that article has been incorporated into the updated keyfile documents provided in the Docs folder of the install.
If I had a copy, I’d gladly post, but unfortunately only have a saved link/bookmark.
Reading through the BMS 4.33 keyfile doc today:
“Button 1 means in this context DirectX button 1. The DirectX button numbers in the BMS UI are shown as Windows DX numbers. From reading the DirectX Shifting Facility Article you should remember that BMS counts DX button numbers slightly different than Windows. You haven’t read it yet? No Problem, I will explain it. Win DX # 1 = BMS DX # 0.
All clear? No? Too bad. Read the article”Underlined parts are links to the forum post. If the significant information in the post is that BMS UI dx numbers and Windows dx numbers are offset by 1, then users have all the information we need.
Though of course never having seen the forum post, I’m not sure whether there are other gold nuggets of information there. -
The information in the article is still valid.
I see if I can integrate the content into my Key File Manual. Need to ask the author first. -
I hope somebody out there can help me with this. I am using Ices profile with keystrokes, no problem there, but it seems as though I can only manipulate the DirectX shift on the joystick. I have read everything I could get my hands on, but it appears as though the warthog throttle is unshiftable. Is there some version of Excel that works with the key file editor? I am renting Excel from Microsoft and it doesn’t seem to be able to export correctly. I guess I really mean the DirectX doesn’t export without error 2023, I believe. I have done everything in notepad++. I thank you Kolby And Ice for all the work you have done.
-
I also want to add that the joystick should be 0-31 and 256-288.
Throttle should be 32-63 and 288-319. Am I missing something? Those are the only two controllers. I use assigned to DirectX. -
it appears as though the warthog throttle is unshiftable.
I am not sure why you say this. The HOTAS is perfectly working with shifted functions and if you refer to my .key file, line 1272 onwards is the shifted state of the joystick and throttle.
-
Ice , Can your profile function without target?? I guess I mean keystrokes for Helios, directx for HOTAS… no Target.