Seriously impressed!
-
And that only works, if the joystick is the only interface you have. Add in extras, and it stops working.
Nope it won’t thanks to devicesorting.txt. You can set your hardwares so it stays ordered the same, even if you unplug and plug back one. So if you happen to unplug device #1, device #2 Dx id’s won’t change.
-
All I know is that I use a cougar and TM MFDs and all the buttons worked out of the box just fine. All I did extra was to reassign 4 of the rocker switches to be used elsewhere. For example, the right 2 rockers on each MFD are not implemented in BMS, so I made use of the VERY usefule STEP UP/DOWN Dx mappings for things like AP Roll/Pitch, MASTER ARM, Stores Config and assigned those switches to the rockers. The step up/down codings make it very easy to assign a 3 position pit switch to the 2 position physical switch.
For me, it’s purely DX mappings on my devices (cougar/MFDs) and click everything else. The only keystrokes I really ever use are LG, canopy, ICP and TACAN/ILS knob
-
Nope sir
DX bindings are already full coded in the default BMS key file for all f16 HOTAS functions
This is only true for joysticks where:
Button 1 = trigger
Button 2 = pickle
Button 3 = pinky (shift)
Button 4 = missile step
etc.For an arbitrary joystick who knows. For example an X-52 the trigger is buttons 1 and 15 not 1 and 6. A user plugs in X-52 and uses DirectX bindings for HOTAS… he must alter key file.
-
@Red:
….
You guys are doing it on purpose, just to piss ppl off while you ALL perfectly understands what he means
This has to stop, right now !!No. I honestly don’t understand what he means. It does not match my experience, or I am misunderstanding it. But the default keyfile DX HOTAS bindings (for example, Full.key, Basic.key, Minimum.key) do not work ‘as is’ with various commonly used Joysticks and HOTASs.
If I load any of those key files (Full, Basic or Minimum) with an X52 Pro plugged in, the HOTAS buttons are nearly unusable; the standard F16 HOTAS commands are all over the place. The user must modify the keyfile DX bindings for it to be functional.
-
@Switch:
Nope it won’t thanks to devicesorting.txt. You can set your hardwares so it stays ordered the same, even if you unplug and plug back one. So if you happen to unplug device #1, device #2 Dx id’s won’t change.
Actually Im taking that for granted. What I mean is, your second device wont have functions on it unless you modify the keyfile.
-
I did not read the entire thread but I find it interesting that someone who indicated they did not care for the sim would get sooo many replies. While some folks who clearly have an interest but have unique questions barely get a peep. Reverse psychology I guess “Just an observation folks”
-
The OP made a mistake. He admitted it. He was having a bad day. He apologized.
Lets move on……
C9
-
he apologized on like page 2
tbh he probably should have just deleted a thread because we’ve gotten ten pages of outrage over it already and there’s no end in sight
that said i’m making it worse but :^)
-
Each of default BMS keyfiles already have complete setup for HOTAS COUGAR users, BMS - Full.key also has complete setup for 2x COUGAR MFD. It’s really user friendly like as DCS:A-10C - has complete HOTAS setup for HOTAS WARTHOG by default.
HOTAS WARTHOG user will also have full functional HOTAS setup for there stick by default as its DX number order is as same as that of COUGAR, but will not see correct(EDIT:sorry I meant “suitable” as there is no “correct” setup for WH as it was never F-16 replica) setup for the throttle, CH/Saitek user will never see suitable setup by default so they must setup there joysticks. Its also same for DCS:A-10C, it should have blank setup for any other joysticks than WARTHOG too.However, Even though BMS is not different from current flightsims at this point, I have seen many people who are already familiar with flightsims - some of them even plays DCS not only FC3 but also some clickable cockpit modules, got an interest in BMS, but they give up when it comes to setup BMS HOTAS and stops there.
They think they can’t find out essential key to bind when they see so long scroll-able callbacks table before they find what all they need to bind are in TQS and STICK section. Some of them might have not found the table is divided by F-16 cockpit panel section.
Even after they completed there setup they find there setup will be gone when they add/forgot to connect some devices and this eliminates there motivation. Yes we have DeviceSorting.txt now but they don’t notice it until I explain. They get so shocked when they first see his setup gone.Really sad to see such a case as its rare to meet active BMS wingmen who can fly same timezone.
-
The user must modify the keyfile DX bindings for it to be functional.
What I am saying is that in that case the user shall modify the joystick DX binding rather than the keystroke . This is why joystick softwares are designed and provided with the stick
PROGRAM theJOYSTICK to match the KEYFILE , NOT the opposite!
Is that more clear ?
-
At which point, we are using keystrokes, not DX.
A few noteworthy exceptions aside, most joysticks are unable to modify their DX bindings. BMS can, and has a very useful keyfile system for that express purpose.
-
At which point, we are using keystrokes, not DX.
A few noteworthy exceptions aside, most joysticks are unable to modify their DX bindings. BMS can, and has a very useful keyfile system for that express purpose.
Are you saying that SST or HUD are unable to change the joystick DX bindings ???
I was not aware of those shitty joystick , time to complain to saitek for that !!!
Ok so what you are suggesting is that for every joystick on the market , we should include a KEYFILE with proper DX binding that matches the joystick config ?
I thought it was what he did already with the profiles included in default install.
Note again I am talking DX only , keystroke shall be prohibited at all costs
-
I am saying that SST is unable to change the joystick DX bindings. I was surprised when I discovered TM software could.
I am not suggesting that you should include extra keyfiles. It would be infeasible, and would not work for many joysticks well anyway.
The profiles in the main install, I have not most of the sticks, and have not examined them. I would personally just suggest people modify their keyfiles as appropriate to their stick, ensuring they have access to the HOTAS commands.
-
I am saying that SST is unable to change the joystick DX bindings. I was surprised when I discovered TM software could.
I am not suggesting that you should include extra keyfiles. It would be infeasible, and would not work for many joysticks well anyway.
The profiles in the main install, I have not most of the sticks, and have not examined them. I would personally just suggest people modify their keyfiles as appropriate to their stick, ensuring they have access to the HOTAS commands.
Well the main complain is about setup beeing difficult , and people would prefer their joystick to work out of the box
The only way to do that is to create as many keyfiles necessary in BMS default install adapted to each joystick
I am talking DX binding only , all the rest would be identical
I don’t think it would be difficult…how many joysticks commonly on the market , 10 maybe ?
-
What I am saying is that in that case the user shall modify the joystick DX binding rather than the keystroke . This is why joystick softwares are designed and provided with the stick
PROGRAM theJOYSTICK to match the KEYFILE , NOT the opposite!
Is that more clear ?
Mav-jp, thats much much more hard things to advice for new comers unless wright down how each F-16 HOTAS switches relate to DX order setup on preset keyfiles to BMS-Manual or TO-BMS1F-16CM-34-1-1 for next update, we can’t say “RTFM” with current manual anymore than.
1.Start with a 4.33 keyfile. Do not use 4.32 keyfile.
2.Do Not change keystrokes setups on keyfile unless you are familiar with BMS.
3.Setup DX bindings from BMS CONTROL setup page as written on BMS-Manual.
–-3.1. If your joystick does not have enough number of DX buttons or HAT swithces, use your joystick driver to emulate keyboard to add shift buttons, without changing BMS keyfile.These rules are enough for newbie advice without updating manuals for 4.33.3.
-
Well the main complain is about setup beeing difficult , and people would prefer their joystick to work out of the box
The only way to do that is to create as many keyfiles necessary in BMS default install adapted to each joystick
I am talking DX binding only , all the rest would be identical
I don’t think it would be difficult…how many joysticks commonly on the market , 10 maybe ?
I had same idea. Preparing “BMS - TM Warthog.key” “BMS - CH Products.key” “BMS - Saitek X56.key” etc. to came with installation of BMS, may solve the problem. Which will be not perfect for each person but good starting point for new comers until they find there best settings for themselves after they came familiar with BMS. Also I would like to update DeviceDefault.txt which seems lacking some comon joysticks.
keyfiles must only contain F-16 HOTAS and not things like FOV change/track IR center etc. Just like current keyfiles are for COUGAR. I can make a keyfile and DeviceDefaults.txt for Warthog and TUSBA R1, other community member might be able to help this idea by creating keyfiles for other devices they own.
-
I was not aware of those shitty joystick , time to complain to saitek for that !!!
Then it is also time to complain to 99% of joysticks produced in history. Being able to change the DX output is a rarity. Foxy, TARGET, and CH managed are the only ones I know. It takes a sheltered flight sim career to not have experienced the limits of the most common joysticks.
Ok so what you are suggesting is that for every joystick on the market , we should include a KEYFILE with proper DX binding that matches the joystick config ?
Not at all. What is commonly done is to take fixed joystick output and have game conform binding to it. It wouldn’t be practical to issue simple DX bound key files even if you wanted to. Most joysticks can’t be bound 1:1 with the F-16 HOTAS due to lack of buttons. X-52s and the like practically require a profile with (hopefully minimal) keystroke emulation.
I thought it was what he did already with the profiles included in default install.
Key files designed to be used with “naked” default controller input are not distributed with BMS except for Cougar which is funny because it is also in the default key file as well. I’m surprised the Warthog doesn’t have a premade packaged. Most joysticks require some kind of profile along with a key file as well. Perhaps this is a good time to construct some pre-mades to be included in he next release.
What I have found however is that universal solutions aren’t universal. I’ve helped enough people with 0 hours flying that INSISTED on specific control features for their setup. Sometimes they have a good reason but sometimes it’s just because their mind is made up. Some people have TrackIR, some don’t. Some have pedals, some don’t. Some will scream bloody murder if they don’t have some obscure cockpit clickable command on HOTAS. Some want TeamSpeak PTT keys. Some have no interest in multiplayer-oriented controls like UHF/VHF transmit. Some just want “chaff n’ flare” keys and won’t listen to what CMS is. It’s a minefield.
-
The folks who complain the system is too hard, are the folks who cant be bothered reading a short manual explaining in detail how to set it up, quickly and painlessly (thanks Kolbe!).
Are these folks going to be bothered to read a much longer manual about how to fly the jet? Are they going to read a manual explaining how to operate the avionics? Of course not. Instead, they will complain how BMS is too hard, and agitate for brief tutorial videos that give the Cliff’s Notes version of operation (Thanks to those few who have done so, without putting major errors into their tuition).
Seriously - not having immediate access to a personalised profile based on your exact controller, out of the box? Its a non-issue.
-
Seriously - not having immediate access to a personalised profile based on your exact controller, out of the box? Its a non-issue.
Actually, thanks to people who post their setups on the forum, you kind of do… that’s how I did it, thanks to Morphine. Not to mention those in the install. I should put mine for the Warthog in the install too one of these days.
-
Seriously - not having immediate access to a personalised profile based on your exact controller, out of the box? Its a non-issue.
I think that’s not the core of the problem, Actually.
Any sims require joysticks setup, its same for DCS,IL-2,FSX etc.
However, I have seen that sometimes even simmers who can handle another aircraft than F-16 gives up his setup when it came to BMS. I guessed several reasons in former post. than I thought having several presets are good solution to solve them, my reason was not mainly to use joysticks out of the box. so If Mav-jp were to suggest same idea I’ll on his side. Perhaps reason he suggested the idea was different from mine though.Anyway if its not possible, I’ll give up the idea and I only continue to advice people when they need it.