New to BMS. Startup help
-
Your join date is 2013. Have you been trying to start the Viper all this time?
Just a little humor. Settle down.
-
Gray, you may well be correct. I tend to “rekey” the critical functions to non-combo keystokes(my Saitek doesn’t like those) , and this may very well have been one. On the bright side, it’s a good example to Persius of exactly what we were talking about
Nice to know about the Saitek not liking combo keys. I’m researching stick/HOTAS combos for purchase and prefer to buy those that DO accept the combos because I don’t really like messing around with rekeying from default settings, especially since I tend to install/reinstall software quite a bit.
-
drtbkj said it before and I think he’s right:
- Use DX programming for your HOTAS to avoid keystrokes and possible related problems alltogether (even though there are quite a few people who got key combo’s to work on a Saitek, it takes more work and attention and is not often the ideal solution).
-
drtbkj said it before and I think he’s right:
- Use DX programming for your HOTAS to avoid keystrokes and possible related problems alltogether (even though there are quite a few people who got key combo’s to work on a Saitek, it takes more work and attention and is not often the ideal solution).
Explain “DX programming”? Not familiar with the term. I’ve always used the programming technique(s) that comes with the hardware.
-
Heard enough after reading this <one thread=“”>after downloading latest BMS installer ……that this sim is not for me. I thank you all in this thread for saving me a lot of time and frustration that I frankly dont have in skinning all the system cats in BMS. Beautiful sim but not what I need.</one>
-
Explain “DX programming”? Not familiar with the term. I’ve always used the programming technique(s) that comes with the hardware.
Like “joystick button 6” for weapon release instead of “keyboard space.”
-
Like “joystick button 6” for weapon release instead of “keyboard space.”
I was last used to using the joystick manufacturer’s software to program the output keycodes. After studying the BMS manual and experimenting with the BMS config page, I’ve realized that the joystick manufacturer’s software does not have to be programmed for output keycodes, instead associating them within the BMS config page. I assume that is what was meant by “DX programming”. Learning all the time. I’ll master this “puppy” yet!
-
Explain “DX programming”? Not familiar with the term. I’ve always used the programming technique(s) that comes with the hardware.
Firstly, Fluke, thanks for the kind words.
Gray, “Dx Programming” is what I call the process of going into the UI, into Controller, left clicking on a command , then hitting a HOTAS button. It assigns it a DX command.
The “combo keystroke” thing is something I used to use a lot. I would often have problems with thing like getting TMS up to work. I don’t use it as much these days. In fact, I don’t know if the UI has improved, I’ve gotten better at it , or both (likely ) but currently the only thing that’s not “DX” on my HOTAS is the speedbrake on the microstick.
Finally, I strongly recommend checking out the BMS Alternate Launcher. Excellent. Through it I was even able to finally achieve shifted functionality.
One note on the AL. Once you have our HOTAS buttons set , on subsequent launches go in with “sign in without override” checked. The reason is that I was having issues with the throttle axis’ not staying set. ‘Burner would engage on half throttle, etc. If you click “…without overide” it lets the main UI set the axis’, and that seems more stable. And, you don’t lose the HOTAS settings. -
Firstly, Fluke, thanks for the kind words.
Gray, “Dx Programming” is what I call the process of going into the UI, into Controller, left clicking on a command , then hitting a HOTAS button. It assigns it a DX command.
The “combo keystroke” thing is something I used to use a lot. I would often have problems with thing like getting TMS up to work. I don’t use it as much these days. In fact, I don’t know if the UI has improved, I’ve gotten better at it , or both (likely ) but currently the only thing that’s not “DX” on my HOTAS is the speedbrake on the microstick.
Finally, I strongly recommend checking out the BMS Alternate Launcher. Excellent. Through it I was even able to finally achieve shifted functionality.
One note on the AL. Once you have our HOTAS buttons set , on subsequent launches go in with “sign in without override” checked. The reason is that I was having issues with the throttle axis’ not staying set. ‘Burner would engage on half throttle, etc. If you click “…without overide” it lets the main UI set the axis’, and that seems more stable. And, you don’t lose the HOTAS settings.Thanks… I had finally somewhat deduced that “DX programming” was what the BMS Setup Configuration was doing. I’m currently following another thread here: https://www.benchmarksims.org/forum/showthread.php?37485-Beginner-questions where grebbben is trying to set up a ThrustMaster Warthog FLCS but he is having some issues with the Thrustmaster “Target” software. Maybe you could drop in and add some input.
-
I wonder if joy2key is an option? If it is it would be DEAD SIMPLE for anyone to use with I believe the ability to share the setups.
I note it has deadzones since version 5.7
I use it for many things (VPinball - zero delay circuit with home made box with leaf and arcade buttons, VirtualOn - warthog and t16000, Evochron Legacy button box - another zero delay circuit board) as buttons/switches but have not tested the gradual input of a joystick.
Not sure it even has that ability so I will test tonight
Just thinking aloud here - Even if it didn’t have that axis functionality it could be used for everything else so then once a single setup was shared ONLY the axis stuff would need to be mapped? I am intrigued by the possibility seeing as I have little faith in the TARGET software continuing to work (I have another post on this topic elsewhere).