Which Hotas do you use for BMS
-
just upgraded to Warthog with virpil warbrd base, but not only that is not working, but even the Throttle doesn’t work anymore. I guess I need to wait for other sims to catch up with what this one have for years now.
I had to remap the stick since it shows up differently to the game with the warbrd base, but once that was set up it has been working perfectly in Falcon and DCS. What specifically is the issue? Is your throttle not showing up as a game controller in falcon?
-
I had to remap the stick since it shows up differently to the game with the warbrd base, but once that was set up it has been working perfectly in Falcon and DCS. What specifically is the issue? Is your throttle not showing up as a game controller in falcon?
Everything shows up, everything works if you select that specific device, but once you save it, and exit nothing works anymore. It defaults to keyboard that is that. Even the throttle does not work anymore, unless I select it, but then the stick axes are out of commission. overall it is unusable. I tried with alternative launcher and that broke the game entirely. Sure I could reinstall but the game is clearly at it’s EoL and I would just and up where I started from in the first place.
-
Everything shows up, everything works if you select that specific device, but once you save it, and exit nothing works anymore. It defaults to keyboard that is that. Even the throttle does not work anymore, unless I select it,
Didn’t you change primary device? that should select stick only and should not select anything other.
Or if you are setting joystick.cal and axismapping.dat read only, uncheck it.
I tried with alternative launcher and that broke the game entirely. Sure I could reinstall but the game is clearly at it’s EoL and I would just and up where I started from in the first place.
Could you tell me how did it broke your falcon?
Sure I could reinstall but the game is clearly at it’s EoL and I would just and up where I started from in the first place.
BMS4.32 U7 to 4.33 took a year or more, it’s clear BMS devs are testing 4.34 (See Radium posting his new 3D model for next version!) and they are even developing 4.35, just we don’t know when to release. So it’S not EoL at all;)
-
Didn’t you change primary device? that should select stick only and should not select anything other.
I can select the device, but the axes will not work unless the proper device is selected. If I select the joystick, throttle and pedals will not work for example.
Could you tell me how did it broke your falcon?
It would not launch anymore, but after all I did a re-install and manually created a link to the hub.exe and that fixed the problem.
BMS4.32 U7 to 4.33 took a year or more, it’s clear BMS devs are testing 4.34 (See Radium posting his new 3D model for next version!) and they are even developing 4.35, just we don’t know when to release. So it’S not EoL at all;)
That is really great news. This game have something special that DCS will never have even after voice chat, dynamic mission and F16 block 52 will be added.
-
I can select the device, but the axes will not work unless the proper device is selected. If I select the joystick, throttle and pedals will not work for example.
Thank you, Let’s get things more precise.
Now you are not using Alternative Launcher and trying to assign axis via BMS UI, right?
If so, Usual step to assign axis via BMS UI is:
1. You choose your stick from “PRIMARY DEVICE” dropdown bar. (NOTE changing PROMARY DEVICE resets axis assign)
2. You choose which axis to assign from “ADVANCED” window.now your symptom is …
1. You choose your stick as a PRIMARY DEVICE and didn’t change it.
2. You then go to “ADVANCED” window and tried assigning axis but any axis except those of stick would not work: axis bar does not move.Is this what you see?
That is really great news. This game have something special that DCS will never have even after voice chat, dynamic mission and F16 block 52 will be added.
Exactly:D
-
Hello,
I had the same problem and then read in the Virpil forum what I have to do.
You have to change the VID / PID / POL with your configuration tool to the PID of the TMWarthog stick
and then save, then your stick is recognized as TMWarthog stick.
You can also load the target scripts with it.
I attached a few screen shots and my device sorting text.
Where you have to change something I framed red.
Unfortunately, I do not speak English and have the text translated with Google.Kind regards. Backfire
-
I did a full reinstall with reg cleaning and stuff before, and this time I manage to make all my devices to work just fine with the normal launcher, and no changes in Virpil or TARGET software. Thank you very much for your time and support. I think I will start using RS Mapper to map some switches from the throttle, but that would be just about it. I am not a fan of using scripts.
-
Ch fighterstick pro usb and satik x52 for its throttle now…I like to see how to set the stick buttons and the throttle buttons if I were truly new, regedit issues aside. The fighterstick is almost akin to the thrustmaster buttonwise…just no 2 trigger detents and no ap slap switch, so maybe a vote to see the saetik setup though I must vote other
-
TM Warthog with FSSB R3 Lighting. Since I moved the PCB over it is being handled just like a normal TM Warthog. I voted in the other please specify since it wasn’t a default TM Warthog.
-
I got it working. I had to calibrate the Cougar and download the profile to my Cougar. Next, set BMS to Cougar and setup the detents and advanced setup for that crazy rudder/toe brake thing for the micro stick X & Y axis(hope we can fix that by renaming it to micro-stick). After that, save and switch to the Warthog as the joystick, set the detents for the throttle again, then save again.
By the way guys, the joystick advanced settings do not save to your profile. By that I mean, if you switch from Warthog to Cougar then back to Warthog you have to resetup everything in the advanced menu(e.g., microstick, rudders, etc). Every other setting outside of the advanced menu saves to your profile in BMS. Hopefully that can be fixed in the next patch.