So excited and then so disappointed..the coaster ride that is f4 bms controller sett
-
“Issues…
1. BMS keeps losing controller settings… I believe this was fixed via setting permissions on the controller files 'axismapping.dat and joystick.cal. Not extensively tested but prob ok nonethe less as the 2 times I fired BMS up the setting remained the same.”I had a similar issue with my ancient hardware and OS:
What helped despite looking for the future and a PC upgrade:
Choosing one of the BMS default key bindings, I chose the BMS basic key, setting meticulously one of my old stick and key settings at a time, if I did not know what the old keys stood for as related to the new ones, check 4.32…each new application hit with the “apply” button and in between and finally save as a “New” named key profile.Somehow BMS did not like me leaving any key options open which were previously assigned. And I tried to keep as many key bindings default as possible and only changing things I can never get used to like Chaff and Flare etc.
Took me 4 attempts but worked it seems.
Good Luck with your issue.
PS
What I really love: Now you can assign a zoom key to the stick (like IL-2 or DCS/LockOn), and of course the new ground terrain engine, looks also similar to IL-2 now down low. -
I, and 4 other very experienced simmers spent hours of our flying time last night battling this problem. It’s not an “OS problem”, it’s a Falcon/BMS problem. I’m going to continue today to try and find a way to get the setting to stick and find a consistent way to map keys. This part of the sim is broken and really needs to be looked at. Thanks to everyone that worked on this at BMS, it’s going to be great to fly it, but only if we can get controls mapped and saved without having to sacrifice a goat!
-
Never had any problem with my cougar , keymapping and BMS.
did i mention i NEVER , EVER , NEVER, EVER touch the keystroke ?
-
I, and 4 other very experienced simmers spent hours of our flying time last night battling this problem. It’s not an “OS problem”, it’s a Falcon/BMS problem. I’m going to continue today to try and find a way to get the setting to stick and find a consistent way to map keys. This part of the sim is broken and really needs to be looked at. Thanks to everyone that worked on this at BMS, it’s going to be great to fly it, but only if we can get controls mapped and saved without having to sacrifice a goat!
Guys,
such kind of posts are not really helpful.
If you think you found a bug or somithing is not working as you expected we need a lot of more information rather than “It’s BMS, not the os”. -
Guys,
such kind of posts are not really helpful.
If you think you found a bug or somithing is not working as you expected we need a lot of more information rather than “It’s BMS, not the os”.“It’s BMS, not the os” was in response to
and to clear things up this is not a bms 4.33 issue but an OS issue… You can post your problem on Microsoft forum… better chances for a solution than here.
. If that’s your idea of being helpful and informative then a guess this is the wrong place for BMS issues. We had Windows 7 Pro, 8.1 64 and 10 all having the same problems. The key mapping would work once, then stop working. Going out of the sim and coming back in would sometimes allow you to reset keys again only to be all lost once you left the sim and came back. Also the stick and throttle was a one or the other scenario as if you had the stick selected in the drop down menu in the set up screen, only the stick worked and not the throttle. We used a target script to “combine” the stick and throttle and that atleast allowed for both to work ingame once. I came back into the sim online and the controls were gone again and I had neither the stick or throttle. At this point we had been at this for hours and called it a night. This was happening with 4 different TM Warthogs and a Saitek.
It’s entirely possible that we just aren’t doing something right or that there’s a lot more to mapping keys and controllers then simply remapping from the set up screen. Hopefully it’s just something we’re doing wrong and someone can point me in the right direction to fix it. Any help would be greatly appreciated!!
-
I can tell you right now that the problem of windows reordering your controllers when they are unplugged/plugged in, is a microsoft windows problem, not a BMS one. I can also tell you that there is a lot more to mapping keys, than the setup screen. Still when using TARGET and a Warthog, there is definitely multiple things that could be the problem.
-
Thanks to all those that took time to post a response.
coupe of followups to the comments…
1. This issue has occurred since prior to 4.32 including 4.32 and now 4.33
2. Issue is consistent across win 7, win 8 win 8.1 and now 10 both home and pro versions
3. Hardware -exotic yes one could place a point on that, however most of this kit is established and the only new exotic bespoke piece of hardware - the SLAW Device rudder pedals - have actually been the single aspect that has NOT caused any issues
4. Unplugging and plugging in hardware - At this stage I don;t believe this is an issue as the whole lot of controllers has been affected ie they all disappear - I’ve not unplugged them to replicate the issue.MAV-JP not too sure what you mean by keystroke…“did i mention i NEVER , EVER , NEVER, EVER touch the keystroke ?” are you referring to the keymapping on the controller page ?
the problem has also followed several hardware upgrades and changes consistently - Hence my belief in the fact that this is primarily and issue with the Flacon 4 BMS code base for controller handling- Motherbords, G cards sound etc have all changed since I’ve been using BMS (not that I’m saying its purely a BMS issue)-
Now I just wish that locking the axis mapping and joystick.cal files down would yield a locked in controller mapping to the hardware…but as soon as I go back to the TQS (tusba R2) entry in the falcon menue under controllers to centre the hat moustick wham all the other settings are lost even if I set the ‘main’ controller back to the hotas joystick …
is there a file I could edit externally to centre the mousstick on the TQS post setup and locking of the files ?
-
Not shure if it really helps you but I have the same problem, OS and hardware. I’m also not shure if the problem with the radar cursor relay to BMS or TUSBA Device Tool or Windows10. The OS caused me many troubles with my multimonitor setup, I get lines all over my screens even when I scroll in my browser. This comes and goes…by now unsolved…
In BMS setup I can’t center the radar cursor axis too.My setup:
2 TS MFDs
1 TS Cougar FCC
1 TS Cougar Throttle/HAL sensor mod/TUSBA R2
1 Saitek Rudder Pedals
OS: Windows10
You could check your calibration and deadzones within the TUSBA HID Tool. When I calibrate it there it’s centered when I enter BMS setup but after the first axis movement both axis didn’t return to center again. I also had a hard time with my thottle axis, it works now but I lost about 25% of axisrange and have no idea why.
So I think it’s a TUSBA Tool calibration problem and realsimulator maybe needs to change something. And when this windows10 mouse flikkering continues I for my self will revert to windows7. In 4.32 all Realsimulator TUSBA axis are named correctly within the BMS Setup UI but 4.33 changed that or Windows 10 did…:(
But Windows 10, BMS 4.32 and the same hardware worked before…centered… -
I solved my axis problem….mybe it helps you too plehmann.
I thougt it’s okay to only use the Realsimulator HID Tool to calibrate all the Throttle axises but this is wrong. You need to calibrate your TUSBA still within the windows device settings according to the RS manual . Now my Radar Cursor is centered and I have 100% throttle range. The axies names are a windows issue too. Wählscheibe for example…;)
So for me there was only one problem and it was sitting right in front of my monitor…Hope this helps
Snapper -
A few questions:
1. Do you plug and unplug your gear (HOTAS, rudder, MFDs, etc.)?
2. How many USB hubs are you using? Are they all powered USB hubs?
3. How many and which devices connect directly to the motherboard USB ports?Do yourself a favor and “reset everything” and start fresh.
a. Unplug your controllers.
b. Go to Control Panel -> Device Manager -> Human Interface Devices and remove everything you can.
c. Turn off your computer, leave for a few minutes, relax, then come back and do a cold boot.
d. Go to \Falcon BMS 4.33\User\Config and make sure axismapping.dat and joystick.cal are NOT read-only
e. Plug in your controllers.
f. Run TARGET/FOXY or whatever you use, turn on all other programs you need such as TrackIR, voice command software, MFDE, etc.
g. When ready, start up Falcon. Go to Setup and assign your controllers as necessary. Click Apply a few times before clicking Done.
h. Do a test flight or two to make sure everything works and none of the axii need to be reversed (sometimes needed for toe brakes).
i. Turn off Falcon. Do not touch anything else on your computer.
j. Turn on Falcon again. Double-check that your controllers are still assigned as before, but do not click Done, just Cancel. *** Are they still assigned properly as they should be?? ***
k. Do another couple of test flights to make sure everything works.
l. Turn off Falcon. Go back into \Falcon BMS 4.33\User\Config and make axismapping.dat and joystick.cal READ ONLY.I greatly advise you try this method because after the initial install of 4.32 and also 4.33, I’ve had smooth sailing with regards to controllers. I play BMS with a TM WH profile and with my monitors on an Eyefinity setup and all my controls work as they should. However, sometimes I forget to start up the profile or I start up the profile then realize I’ve not connected my joystick handle to the base. Sometimes I just want to do some testing and don’t bother to switch to my Eyefinity setup (5896x1080 res) and stay on my Desktop setup (4 monitors at 1920x1080 res each). It doesn’t matter. When I’m ready to play again, I just do my little “dance” and when Falcon starts up, everything works as they should……
One little bug is that if I fiddle with BMS on my Desktop setup, when I go back to my Eyefinity setup, I’ll need to reset my display to the Eyefinity res otherwise Falcon will just display at 1920x1080 on my left monitor
Hope that helps!
-
This is not new ppl, 4.32 had the very same effect.
We cockpit builders have dealt with this issues for agesIf one controller got disconnected the order of the josytick ID is changed and reassigned by the OS and has conséquences in the game.
Solution:
1. don’t change your controllers, never unplug them
2. Ensure you have stable hardware. Depending on USB power available, some controllers may disconnect on their own because they don’t have sufficient power
3. Check that your USB don’t go to sleep on their own (system settings, USB properties)
4. Minimize as much as possible the number of required controllers to decrease the symptoms
5. place config files to read only, and once all config is done. Backup these files so you can restore them at any time
6. always check all controllers before launching BMSOnce again, it’s not a BMS issue. But it’s an issue that BMS couldn’t plan accordingly because of the OS action some levels down.
It’s annoying but it can be dealt with. The pitbuilder community learned to deal with this issue as we by définitions have a lot of controller ID present
-
I’ve kept an up to date config file on my desktop for years to replace it when this happens. Its not a big deal.
-
2 x MFD’s (swapped in relation to physical location - they are attached to 2 x 8" lilliput USB LCD’s) –-arrrg
1 set of Thrustmaster Wathog Joy/throttle
1x cougar TQS via TUSBA R2 USB interface
1 x SLAW device Rudder pedalsI would recommend you get USBDView and delete these items from your system, then plug them in using the following order;
Warthog
TUSBA
Rudder
Left MFD
Right MFDthen see how it goes from there. I think it is an OS issue before BMS, but other sims might handle USB devices in a more user-friendly way (well, they have to do something better than BMS…! )
-
(well, they have to do something better than BMS…! )
Hehehe…. BMS can’t have everything, now, can it? No, that would be too selfish!
And yeah, +1 to RD’s suggestion of never unplugging your stuff… or at least minimize doing it. All of my gear goes into a powered USB hub and the only thing that plugs into my motherboard is the HUB and the TrackIR camera. Having said that, I relocated my pit earlier this year and didn’t have any issues when re-connecting the gear.
-
@Red:
This is not new ppl, 4.32 had the very same effect.
We cockpit builders have dealt with this issues for agesIf one controller got disconnected the order of the josytick ID is changed and reassigned by the OS and has conséquences in the game.
Solution:
1. don’t change your controllers, never unplug them
2. Ensure you have stable hardware. Depending on USB power available, some controllers may disconnect on their own because they don’t have sufficient power
3. Check that your USB don’t go to sleep on their own (system settings, USB properties)
4. Minimize as much as possible the number of required controllers to decrease the symptoms
5. place config files to read only, and once all config is done. Backup these files so you can restore them at any time
6. always check all controllers before launching BMSOnce again, it’s not a BMS issue. But it’s an issue that BMS couldn’t plan accordingly because of the OS action some levels down.
It’s annoying but it can be dealt with. The pitbuilder community learned to deal with this issue as we by définitions have a lot of controller ID present
Any tips on how to prevent USB devices from powering off and back on? My TM MFDs like to switch off and back on again while flying every so often. So far, doing so mid flight has actually had no effect on the controls, but Im concerned it could do. The MFDs are plugged into a powered hub so I would be surprised if they werent getting sufficient power.
-
Any tips on how to prevent USB devices from powering off and back on? My TM MFDs like to switch off and back on again while flying every so often. So far, doing so mid flight has actually had no effect on the controls, but Im concerned it could do. The MFDs are plugged into a powered hub so I would be surprised if they werent getting sufficient power.
Go to windows power saving options -> there go advanced -> find usb column and disable selective powering etc…
http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html
Works fine in win10 too.
-
Already disabled selective suspend.
-
I would like to know why I never have any problems ?
I have the warthog plugged into a USB extension bracket that connects to one of the additional MoBo headers.
A pair of MFDs that connect through a monitor hub (unpowered & now powered)
Track IR.
Some times two mices. Bluetooth with adapter and normal.
To gain access to my bios I MUST unplug the hog, the MFDs can remain.
I have changed GPUs, firmware updates, run dual boot with XP & Win 7, pasted back OS images, overclocked.
Started BMS with out the stick/throttle plugged in, just plug it back in and restart BMS.
I don’t understand, I’m on GA Z77 board, its nothing special.
The only thing that hasn’t changed is the onboard header port that the stick is on.
There has to be a common thread some where.