Begging for help, ready to give up.
-
I’m a bit with you on the “Key File Editor”, I never really could see what its function is, and I must admit I never found a reason to find out.
As for the triple monitors go I don’t recall why I gave up on them, I remember using it a lot with Black Shark, cant say for shore ??
I do remember using one monitor to display “TeamViewer” with our server as a active connection, and other things on the other monitor as well. Our squad was a bit more active back then and need access to TS2/3 on a regular basis also.
-
Not sure if this will help you but Snelle has done a fantastic document regarding editing key files for BMS. It’s based upon using a X55 (my current HOTAS) but I’m sure reading that in conjunction with the Keyfile documentation in your install will help you. I can’t post link to forum post as using tablet and tapatalk right now, but it’s in the Input/Output section, under Saitek, X55 Key file - fully programmed version 5.0. There’s a link to the documentation only you can download.
It really helped me understand how Windows and BMS ‘see’ USB controllers.
Hope it helpsSent from my Nexus 7 using Tapatalk
-
Just my 2 cents, I’ve never used a Ch stick (I’ve got X-65), but I programed my stick pretty much inside the sim options. Works perfectly fine. Only thing I had to use the profile editor for was some of the hat switches. Not sure if this helps you out at all but thought I’d throw my experience in there.
-
I can’t seem to get my controls to work. I have a CH Fighterstick and Pro Throttle. Yes its running in mapped mode. Yes I have saved and applied the profile.
Which profile?
Can we just confirm you have read and followed the instructions in the CH Fighterstick and Pro Throttle HOTAS DX Setup guide in your \Falcon BMS 4.33 U1\Docs\Key Files & Input\Device Setup Guides & Profiles\CH Fighterstick & Pro Throttle folder?
-
Worther, is that stuff from Snelle on the forum or is it inside the install directory?
Darkman, one of my issues with the Key File Editor is that its instructions are little hard to follow at times. I had posted about it in this other thread.
https://www.benchmarksims.org/forum/showthread.php?27143-How-to-use-the-Key-File-EditorAt this time I think I’ll try to print out the diagram showing the key bindings in the Key File Editor and try to enter those manually in the options menu.
-
?
I didn’t say anything about the Key File Editor. I was asking you about the profile that is included in your installation, which was designed for your CH setup. Are you using it? If not, why not try that before starting to build one from scratch?
-
Wait what? I didn’t find any sort of profile within my installation. There were instructions in a pdf to create said profile.
I am following along in the “DX CH Fighterstick and Pro Throttle” pdf file, but I don’t really understand what to do when we get to page 6 in the section which says “Define DX button map”.
I open the spreadsheet, enable Macros in Excel 2007, and then I got kinda lost so I started following the videos in the link I posted to the other thread.
Are you saying there is a pre-built profile for the CH already?
-
You tell me; I’ve never owned CH kit.
Are the .cms and .map files in that folder not a pre-built profile for your CH Fighterstick and Pro Throttle?
-
Okay I am going to uninstall BMS, clean the registry, and do a totally clean install and find out if there is a pre-built profile.
-
i can send you my config file if you would like. Then all you need to do is import it in to the BMS Key File Editor then export back user/config folder. The only thing you should need to do is make sure the fighter stick is controller1 & Throttle is controller 2 in the DX Settings tap. They both will be primary input devices. My profile would includes trackIR recenter. PM me your email if you want me to send it…
-
The CH mapping software is extremely powerful, exceeding TARGET or Foxy in key areas.
Despite the power of mapped mode, direct is a whole lot easier to work with quickly and should be sufficient. If you can express a “I want this button to do this” type scheme, you’ll get all the help in the world actualizing it.
-
Another case of convoluted answers as apposed to “Keeping It Simple Stupid” guiding the responces to a new person just wanting to get in the air.
:munch:
Joy stick or Multi monitors, Fasteagle I would have tackled one at a time.
-
In my install, the .cms and .map files are in the same folder as the pdf files.
Falcon BMS 4.33 U1>Docs>Key Files & Input>Device Setup Guides & Profiles>CH Fighterstick & Pro Throttle
-
Shep: I sent you a PM
Frederf: The instructions inside Falcon BMS 4.33 U1>Docs>Key Files & Input>Device Setup Guides & Profiles>CH Fighterstick & Pro Throttle say to use Mapped Mode.
Shadow: I think you are correct, because I am also brand new to the CH combo having come from an X52.
Icarus: I had files inside that directory also, but I didn’t know if they came with the game or if I had created them myself, so I will be doing a clean install of BMS to be extra sure.
-
Fast Eagle, the Snelle file/post was on the forum. Look in Input/Output folder then Saitek folder.
Sent from my Nexus 7 using Tapatalk
-
-
say to use Mapped Mode.
I’m sure that’s the case for a specific profile. Direct is fixed output or non-configurable. Mapped uses some configuration and since it’s a profile-type preset provided it needs to be mapped mode. Starting with mapped means that it can evolve without limit. Direct still allows you to play with BMS’s config but the output from the CH device is fixed. I’d probably go with mapped and some starter profile knowing that you can always tweak and change it over time to the full potential of the software.
-
Okay, first things first….
You will want to change two values in your falcon bms.cfg:
set g_fDefaultFOV 80 –- this is the default. Reset to 120-140 for your setup. I use 130 at 5896x1080. This limits your maximum “zoom out” function.
set g_fViewlimitPitchDown 0.0 — this is the default. Reset to 70-90 for your setup. I use 90. This limits how far down you can look inside your pit.I take it BMS recognizes your nVidia Surround resolution and displays it in the in-game UI drop-down selection menu?
As for controls, there is one thing you need to understand with Falcon — a lot of people use their own custom controller profiles. For the TM Warthog alone, there are a lot of profiles available (Mud, Morphine, etc.) and a lot of people download those profiles and use them as is… or modify a thing or two to suit their preferences. I suspect that is also the case for CH gear. I would advise you to go to the controllers sub-forum and ask for help on the CH boards.
Another thing to understand with Falcon — each profile usually comes with it’s own .key file. A .key file is basically instructions telling the game “If the player presses Button A, drop a bomb. If the player presses Button B, put the gear up”… obviously a bit more complex than that but you get the point. Understanding how a .key file works, how callbacks works, how directX controls are sent, allows you to get more control over your personal profile. My advice is to download a pre-built CH profile, try to reverse-engineer it to see how it works, play with it for a while, then tweak to suit your taste.
They don’t call it “the dance” for nothing…
-
To set controls up in the game, it “will do” if you set it up via the in-game UI, but understanding the .key file structure and layout will be to your benefit in the long run. But for now, just to get you in the air, feel free to setup the keyboard commands via the in-game UI.
Then comes the next question… what .key file to use? The default install alone comes with at least FIVE!! Well, start with the .key file provided by your downloaded CH profile. Understand which of the default .key files it used as a basis.
With regards to the Key File Editor Excel file, I only really use it to show me the “blank areas” of my .key file for when I’m looking to fit a new callback in. Otherwise, I just edit my controls via Notepad++ and directly onto the .key file. I’m sure the Excel file does serve some purpose aside from this but I’ve never bothered yet to find out.
-
I would make sure to set set g_fMaximumFOV to a much larger value like 150 as well. It would be kind of weird to set the default FOV to be larger than the maximum.
Depending on the number of devices you have their order might not line up the button numbers. Device 1 gets buttons 1-32, Device 2 gets 33-64 and so on. If the loaded profile and key file don’t line up, don’t panic! The file devicesorting.txt in the config folder easily specifies device order.