Begging for help, ready to give up.
-
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.
-
I’m not sure with 4.33.1 but with 4.33, I have my set g_fMaximumFOV at 80 with my set g_fDefaultFOV at 130 and it works. Maybe if the Max FOV is higher, you can zoom out a bit more, but never felt the need at 130 FOV.
-
Hi all, I was out of town for work all weekend, so I’m back home and tinkering with BMS now and hopefully will resolve all my issues.
Thanks again for everyone’s advice and I’ll report back with my results.
-
I’m not sure if it was mentioned earlier in the thread, and exactly how CH controllers work with the Keyfile editor, and CH software, but I did find that with TM Warthog Target software, which combines Throttle and stick into one controller, the setup was a bit messed up in how DX calls were handled for the stick/throttle, though it is very useful to see how key commands are set up, and for editing them. As mentioned before, the best way of editing the keystroke file is by loading it into Notepad++ or similar.
Most of the keyfiles are heavily commented, so that helps a lot. It also used to be the case that setting keystrokes in-game deleted all your formatting and comments. I’m not 100% sure, but I think that was fixed in the latest release, so it may be worth a play with that, do some setting up and reload the file (always back up) into a text editor to see if things are as you expected.
Another Major point to be aware of, if you aren’t already, is to use the ACTUAL RL control functions as much as possible… IE TMS, DMS, CMS etc , so rather than a separate key or button press for Lock Target, you map the button to TMS UP, which can have several commands associated with it in the sim, depending on the current Mode.
In your .key file there will be 2 entries for that command
First of all something like this for the keystroke itself that shows what command is mapped to what keystoke. In my case, SHIFT+Home :-
SimTMSUp -1 0 0xC7 1 0 0 1 “STICK: TMS Up”And then, in the last half of the file, dealing with stick, throttle and other controllers, the entry that tells BMS which controller button Calls the TMS UP command. In this case it is DX6 (Button 7 on my stick in BMS - this is always 1 more than DX).
Just bear that in mind if you are swapping between editing in BMS and in a text editor or the Keyfile Editor.
SimTMSUp 6 8 -2 0 0x0 0 -
I’m not sure if it was mentioned earlier in the thread, and exactly how CH controllers work with the Keyfile editor, and CH software, but I did find that with TM Warthog Target software, which combines Throttle and stick into one controller
The CH Control Manager enables to combine the joystick and the throttle as a single device, or use them as two separate devices (the latter option being simpler, IMHO).
The CH Control Manager is not absolutely needed, though : you can use CH devices without it. However, as Falcon can’t handle two POV hats (unless I’m mistaken), you need the software if you want to be able to use both. But using the CH Control Manager to make a POV hat act as DX buttons is quite easy. -
I just got back into this sim, after flying FSX. I have a triple monitor setup running eyefinity and Track IR 5. I was having the exact same problems, pretty much going crazy trying to find solutions . I was only able to modify the default and max FOV lines in the BMS.cfg file, following recommendations from earlier posts. I put the FOV at 130 each, no change. I put default at 130 and max at 140, no change. Out of frustration, I put both FOV settings to 140 and bingo, my view looks great. I think there was an earlier post about having to put the FOV higher than 130. Worked for me.
-
in your falcon bms.cfg file there are 3 settings that control FOV
1 is your default FOV
another is your max FOV
and another one is in which increments your FOV changes (when using mousewheel for instance)these first 2 are what you need to modify, iirc MAX supported FOV is 140, i only run a single monitor but someone else i know that runs a triple setup uses an FOV of 135
-
I am having the same problem apparently as Fast Eagle. My problem was encountered when installing U1. Looking forward to flying somewhere besides Korea. When I read these Posts I seem to remember someone helping me setup my three monitors by increasing the FOV in the .cfg file. The problem is I can’t remember where or even find the .cfg file. I did find the configuration application but it only allows me to put a check mark on an FOV of 80 and the default does not seem to change. Hope this makes sense. Obviously I am not much of an expert with computers but you all have been great about helping me with all my questions and problems. This application is terrific. I appreciate the priorities the design team has which is quite obviously reality first and foremost. Thanks again.
-
Wait! Typed in the wrong filename for the search. The number of times I have hit post reply and then realized my mistake is embarrassing. Please disregard for now. However I could be posting here again in the near future.