Ff you could have one thing in the next update it would be…
-
If its COUGAR you don’t even need setup as they are already done by stock. If you have a stick-throttle integrated device with enough DX/axis like COUGAR, BMS is pretty good. But if not…
- Need pinky shift assignment editing a key file by a text editor.
- If stick and throttle are separate devices, POV on the throttle does not work.
- Radar Elevation has to be set to an axis or it does not work continuously when using DX callback. But do you have enough axis?
IMO these are leading users to script HOTAS rather than setting them up from BMS UI. Makes many troubles.
Having ready-made full configuration files by stock is a really good idea. Maybe we can prepare sets of .key file and DeviceSorting.txt for each popular joysticks.
Theirs also is DeviceDefaults.txt in User/Config which defines default axis setup but, currently, it only works for stick device even though there already is premade setups defined for separate throttles. If its fixed, separated throttle and pedals also have default axis setup so BMS can have a true ready-made full configuration for any joystick.
Newbies often find their setup “suddenly disabled” while flying which is, in fact, pinky shift stuck. There is a way to resume it and can be written to the next manual, but I think it has to be fixed as it seems unwanted bug.
-
Newbies often find their setup “suddenly disabled” while flying which is, in fact, pinky shift stuck. There is a way to resume it and can be written to the next manual, but I think it has to be fixed as it seems unwanted bug.
On what assumption is this based?
Is this joystick relevant? if yes, which one?
Is this BMS relevant, Ifso how come most of us never reported Something like thisNeed more information as the guy writing the manuals are not aware of such problems
-
@Red:
On what assumption is this based?
Is this joystick relevant? if yes, which one?
Is this BMS relevant, Ifso how come most of us never reported Something like thisNeed more information as the guy writing the manuals are not aware of such problems
I’ve had this but it’s a worn button the cougar. I suspect it’s the case for many that have had similar ‘stuck keys’ problems with these aging cougars.
-
It’s not about a physical worn button problem.
It happens in any joystick.
It’s obvious BMS glitch.
I got a similar report at Hoggit, at my launcher mod thread, and at Twitter several times.Edit: It is already reported here.
https://www.benchmarksims.org/forum/showthread.php?34800-Pinky-Shift-state-sticking&p=483483&viewfull=1#post483483
https://www.benchmarksims.org/forum/showthread.php?34367-DX-Shift-Stuck-freezes-my-stick-s-buttons-whenever-I-hit-the-Pinky-Switch-(DX-Shift)&p=478655&viewfull=1#post478655Try press and hold pinky shift button, hold 1.0 sec or more to enable DX shift. then release it without pressing any other joystick button. BMS will stuck DX number are shifted. So any button you press appears DX shifted even if you not pressing pinky.
-
okay, so it’s DX only when shifting is invoked right?
-
both DX and POV shifts and stuck.
-
In any case, whats great about BMS is, that you just map the virtual HOTAS Functions to the stick and then the behave correctly depending on the current mode (i.e. AA/AG) and simply do what they are supposed to do.
Even sticky dogfight mode was eventually supported.
That allowed me to get rid of so much Cougar programming using a pure DX setup instead. No complex profiles anymore that always work only so good before something gets out-of sync with the sim…Always was a fan of that!
-
+1
-
In any case, whats great about BMS is, that you just map the virtual HOTAS Functions to the stick and then the behave correctly depending on the current mode (i.e. AA/AG) and simply do what they are supposed to do.
Even sticky dogfight mode was eventually supported.
That allowed me to get rid of so much Cougar programming using a pure DX setup instead. No complex profiles anymore that always work only so good before something gets out-of sync with the sim…Always was a fan of that!
Yep. that works pretty fine, problems for ppl start to arise as soon as they want to push that to the next step which often is … shifter layers with DX. and then ppl get confused a lot…
-
@Red:
Yep. that works pretty fine, problems for ppl start to arise as soon as they want to push that to the next step which often is … shifter layers with DX. and then ppl get confused a lot…
Yes, there still are some nut’s n bolts. Suffered from those as well.
Greets
-
I wish radio calls from AI could be pushed through IVC :). It’s really cool immersion other human pilots have the radio effects, then you hear a clear as a bell AI and like ah man……
I know that would be a monumental task but one can dream lol
-
This post is deleted! -
Red Dog, in light of the above post, you might want to consider a flight document wherein any acronym is mouse-hover sensitive to show the expanded meaning of the acronym, and possibly even an Index page number where the reader could quickly access more info about that acronym…
Lot of work, I know…
-
Idea is good! But why always “Red Dog should consider”?!? Why not you SoBad especially if English is your mother-thong … Or anybody else reading those lines … Why?
Personally I think Red Dog (& Co.) is doing a “perfect” job.
-
-
mother-thong
:icon_e_surprised::icon_e_surprised::icon_e_surprised::icon_e_surprised:
Really??? How bout tongue!!!
Mower’s thong thread is a thing of the past!!!
C9
-
Idea is good! But why always “Red Dog should consider”?!? Why not you SoBad especially if English is your mother-thong … Or anybody else reading those lines … Why?
Personally I think Red Dog (& Co.) is doing a “perfect” job.
DJ, a large part of my career included writing technical manuals before I retired 15 years ago, and I’m good at it. Red Dog has done an outstanding job and is open to editing feedback from forum users. But no one from BMS, including Red Dog, or you, ever said in all these years that they were interested in anyone else helping with the documentation, so don’t give me your attitude like I should know to offer help.
Also, my mother never had a thong. There were no ‘thongs’ back when my mother was alive.
-
-
I think newer players would benefit more from a short(ish) down and dirty on a few things, as opposed to a premade set of keyfiles. For instance:
8-10 page “exerpt” from the -1 about the different ESSENTIAL systems; what they are, what they are used for, and the acronym: DMS, CMS, TMS, FCR - and the value of having quick access to it from the HOTAS. The setup process itself is not all that complicated. It’s a new player who knows nothing about any of these systems trying to figure why it’s important to keep DMS UP/Down (If not room for all 4) on a HOTAS. Or understanding what SimTMSUp actually means. The UI Description in the setup screen says : STICK: TMS Up. Isn’t that kind of like using a word in it’s own definition?
I know almost all the callbacks are addressed in the manuals at various levels and places. But for a new(er) player, it is asking quite a lot to search 4 different documents for every single key command in the list to a) try to figure out what it does, and b) guess from the description if it’s actually important. For instance, someone familiar with “aviation” might see the Flap controls, and think, “Oh, flaps are important. I need that mapped…” But in an F-16 that command is more or less worthless. Conversely, if you don’t know what CZ and C-Enable do, they are easy to gloss over in the list without a second thought, but they’re actually quite valuable in the game.
A quick 2-3 paragraphs about some of the key systems that players who are just “testing the waters” could run through in a few minutes I think would help to eliminate a lot of the Key/Command setup frustrations. And as much as a pain as I know it would be, an actual description of all the callbacks listed in the BMS - Keystrokes file would probably solve 70% of them. Or even just a simple “Use Case” for some of it… like how many people who on the very first time in an F-16 look at the setup menu and wonder why they use JFS2 instead of JFS1… is there ever a reason to use JFS1? Is it even implemented? Wait… what the **** is a JFS again?
I’m all about making things easier for new people to catch the bug by selling the immersion and study-sim factor. But I’m also a big fan of teaching someone to fish before I give them a free dinner. I just think sometimes it’s better to teach them to fish at the local fishing spot just for fun, and not in the survival raft where their life depends on it. The manuals are big, and long, and technical, and detailed (And great, don’t get me wrong)… they’re just a LOT for a new player, with no friends or VFS there to help get them through the initial struggles.
EDIT: As a side note, I do REALLY like that there is now a file included with the default keystrokes. And that many of the callback references in the training manual have been replaced with the default keystrokes. I think that helps immensely for newer players.
Nailed it.
-
Well maybe Reddog didn’t ask for help but one can produce it and offer it.
I don’t think anyone will say don’t do it.Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk