So excited and then so disappointed..the coaster ride that is f4 bms controller sett
-
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.