DMS up and X55
-
DMS down would do that…
DMS up move SOI from MFD to HUD
-
I have zero use for SST using the X55 beyond programming the mode selector to be my override switch. Other than that, I was able to DX everything with plenty of switches left for lights, startup procedures, etc., no modes or shifted commands. I’ll be happy to share my keyfile with you if you’d like. Actually I might just post it for all to use, but won’t have access to it until Monday.
As Badger stated, methinks you have DMS up and down confused.
-
Thanks guys. I’ll take your ideas away and test them out. I disagree with your thoughts about using DX instead of SST as you appear to lose the option of using all three modes available to you.
I want to use the DMS Up to move the SOI around, specifically from FCR to the right MFD, usually for the Maverick camera as it doesn’t move automatically.
Consider the “loss” of the 3 modes of SST to be a blessing. The X-52 has enough buttons that SimHotasPinkyShift and only a single SST mode is more than sufficient to cover the HOTAS commands plus a few luxuries. Putting the entire clickable cockpit on a joystick under a fictitious extra layer does substantial harm to user effectiveness.
If you insist on using DMS up to move SOI between the two MFDs may I recommend an aircraft other than the F-16 because in the F-16 DMS up doesn’t do that.
-
Thanks guys. I’ll take your ideas away and test them out. I disagree with your thoughts about using DX instead of SST as you appear to lose the option of using all three modes available to you.
Are you planning on using the different modes for (i.e., one for NAV, one for A/A, and one for A/G) type activities?
-
Exactly that Dracfalcon. I use mode 3 for air base operations and the other two modes (mostly mode 1) for air and ground actions. So I actually use the same switches in different modes to do different things.
Thanks to others for the heads up about the DMS direction. I’ll check that out too. I have to say that I have been happy with SST in the past as it has done everything I asked of it when I had my old X-45. The X-55 has been somewhat more difficult and a little disappointing but I paid my money and I have to deal with it.
-
Exactly that Dracfalcon. I use mode 3 for air base operations and the other two modes (mostly mode 1) for air and ground actions. So I actually use the same switches in different modes to do different things.
Roger.
-
The X-55 has been somewhat more difficult and a little disappointing but I paid my money and I have to deal with it.
Sorry for the thread derailment, but what do you not like about the 55 so far? Opinions seem quite varied. In my case, I’ve been extremely pleased and I have had zero headache interfacing it with BMS, but I also only use SST for one switch.
-
I love the X55….however, I would’ve loved to see an afterburner detent on the throttle. I don’t like that you can’t program the slider in increments for the airbrakes like the 52.
-
You can’t bust up the slider axis into bands in the X-55?
-
Unfortunately not. It’s programmed as a button.
-
-
nd@Frederf:
Consider the “loss” of the 3 modes of SST to be a blessing. The X-52 has enough buttons that SimHotasPinkyShift and only a single SST mode is more than sufficient to cover the HOTAS commands plus a few luxuries. Putting the entire clickable cockpit on a joystick under a fictitious extra layer does substantial harm to user effectiveness.
I’m still trying to understand the difference between mapping controls through BMS (DX) and through the X55 HUD program (SST you refer to?). In some cases, DX mapping seems necessary, like long press-and-hold commands (COMM Xmit), but I’ve not had any problems with any other commands. Maybe I’m missing something since I don’t understand your comments of “fictitious extra layer” and “substantial harm to user effectiveness”. Can you explain these maybe in terms of what could be ineffective on my settings on the X55?
My setting uses the three modes to coincide with NAV, AA, and AG mode, which tripples the commands for most switches on my controller, allowing me to maintain HOTAS for all flight phases except non-time sensitive commands, like gear and lights. Many commands I guess I could just click on the cockpit switch instead of mapping a controller switch, but I gain effectiveness having it on the controller where I can press it by feel, and not have to look down to a cockpit switch or keyboard. One example is on a low level bomb run, on approach I can switch CCRP to CCIP (throttle sw 4) while diving in to the target, then do a low hi G turn away and chaff/flare (stick pinky), and set CATIII to CAT1 (throttle sw 4), then AWACS Picture (throttle tgl 2), then switch to AA mode, without taking my eyes off the screen. This not only helps me now in my ‘bi-focal’ days, but I personnally feel its more realistic to hit a single switch for a command as opposed to a combo press with the pinky switch (like I used on my X45), even if I have to occasionally switch a mode selector. I suppose most of this debate on settings is ‘user preference’, so I’ve been looking to learn more of the hardware/software issues of not using DX only. I still hit the wrong darn switch and mess up a good bomb run once in a while, so I’m all about ‘user effectiveness’ if your able to shed any light for me. Thanks.
-
Back when I had a Saitek X-45 I used the Saitek Smart Technology (SST) software for the joystick. I think they changed the name after the X-52pro but if you use both software you can tell it’s approximately the same software only they changed some blue to orange. Mostly it is the same.
SST http://wargameguru.weebly.com/uploads/4/1/2/7/4127304/7237351_orig.jpg
X55 http://www.simhq.com/wp-content/uploads/2014/03/X55-TRIGGER-1.pngThere are different ways to use SST. If a profile entry for a joystick button is blank then the natural DX button is seen instead. So a completely blank profile will work mostly like not running the software at all. The common method is to put a virtual keyboard key or macro into these slots. Pressing the joystick button causes a virtual keyboard button to be pressed and the game responds to this keyboard key. Many people use profiles that reflect the default keyboard layout to save effort. In most cases the direct DX bind is superior because:
1. You are free to use that keyboard “middleman” for something else.
2. You can inadvertently press the physical keyboard middleman.
3. The software can’t distinguish between the physical keyboard and the virtual one.
4. Modifier keys occupy global command space. “Shift-A” can be one command, “B” another command and “Shift-B” might be eject. You press both buttons and accidentally eject. Unintended consequences of simultaneous buttons.Press and hold commands are no problem for SST. Keys that are white are linked to your button. Gray keys indicate macros. With a white normal bind you can press “A” the press and release events will match those of the physical button. A macro has the timing built into it which can just be a tap or a whole sequence.
The major difference between DX binding and virtual-keyboard-middleman is that if gnomes were to sneak into your house at night and rearrange BMS to be DX direct there would be zero motivation for you to change it back. You press Button X, Action Z happens just like before. You never directly benefited from the keyboard middleman except that it saves labor in initial setup. The reason people don’t change from SST to DX is mostly because the labor investment doesn’t pass a “worth it” threshold.
Switching from CCRP to CCIP is built directly into the F-16! You don’t need a special button for it. The missile step should be pressed by Button 3 on the X-55. That’s exactly where it is on the real airplane. It controls nose wheel steering, missile selection, AG submode (CCRP-CCIP-DTOS cycle), and AAR refueling. You roll in switching from CCRP to CCIP for a visual delivery using your right index finger extended just like a real viper pilot. I don’t understand why you would fly a detailed F-16 simulator using an expensive controller and not make the obvious connection.
Countermeasures on the pinky? In the real F-16 pinky does FOV for various sensors. Where is the rest of your CMS hat? It has four directions. By limiting yourself to 25% of the CMS hat you are limiting your effectiveness as a pilot. How do you release program 6? How do you use semi or fully auto CMDS? The real CMS hat is the “shelf” on the left side of the joystick. On the X-55 this is a simple single button so instead using SimHotasPinkyShift you could use one of the 3 hats on the top of the joystick. When tapped briefly the pinky switch would expand the radar and when held becomes a shift to get that 4th hat where it goes, at your fingertips.
Cat Limiter switch on the HOTAS? It’s not a particularly time-sensitive switch. It just keeps the roll rate a little lower than in Cat I. The deck of the throttle device is where I expect to find the convenience controls. The only concern is that its presence suggests you might be over-prioritizing in the list of egress actions. I know it’s a nag but there’s no harm in getting it 20nm outbound. Do you have emergency jettison, master pitch override, and RF quiet already bound?
A macro for voice comms is interesting. I use the keyboard and when feeling exotic Livrot voice activation. If you’ve got the spare switch.
You should absolutely have a MRM/DGFT switch bound to your controls. AA mode I rarely use. MRM on, deselect to AG, then MRM back on. You do have a MRM/DGFT switch set, yes?
–-
On the concrete benefits side, ditching the mode method allows you to use the mode switch for something other than switching modes. There are downsides to the keyboard emulation route. SimHotasPinkyShift’s behavior is impossible to replicate any other way if that appeals to you. You want to discount the psychological factors but my position is the mindset is a huge factor. Having so many control slots encourages one to put non-fingertip controls at fingertips which encourages poor preparation patterns. “I don’t have to set things up before combat because all my controls are so convenient.” I’ve troubleshooted situations where someone had extra fantasy callbacks bound that caused actual avionics bugs (e.g. SimNextAGWeapon). None of these were direct consequences of the Saitek 3-mode cult but were precipitated by it. I’ve had people crash or be shot down because “sorry lulz I was in the wrong mode.” I’m not saying it’s wrong but I think a happier life is had elsewhere.
-
Switching from CCRP to CCIP is built directly into the F-16! You don’t need a special button for it. The missile step should be pressed by Button 3 on the X-55. That’s exactly where it is on the real airplane. It controls nose wheel steering, missile selection, AG submode (CCRP-CCIP-DTOS cycle), and AAR refueling. You roll in switching from CCRP to CCIP for a visual delivery using your right index finger extended just like a real viper pilot. I don’t understand why you would fly a detailed F-16 simulator using an expensive controller and not make the obvious connection.
Thanks for your time detailing DX configuration and accurately identifying my obvious lack of knowledge. I’ve put hours and hours into reading manuals to teach myself this sim, and here I still learn something new about using the stick paddle switch for switching CCRP to CCIP. I actually do have my paddle switch mapped for Missile Step, but just never saw that part in the manual that it has an AG use except for switching AGM’s.
I also have only one chaff/flare operation mapped on my controller (ECM\CMDS- Slap Switch), since I’m also just not that advanced to understand all of the various release programs yet. So you’ve enlightened me to understanding that my use of the SST program is indeed a crutch to help me along until I find all of the advanced needs for controller commands I’ve yet to understand. Hopefully that explains why I’m flying this detailed sim with an expensive stick and can’t make obvious connections. You’ve also helped sell me further to going the DX route, though I’m not totally sure how to get from here to there yet, but I’ll keep looking and reading.
Most other commands you questioned are mapped on the controller except a few I don’t fully comprehend yet, like RF quiet. Again, I’m still learning this operation so I’m mostly running the radar on all the time so I can find a target. I found interest in your operation of MRM mode out of AG mode opposed to switching to AA mode. Thanks for your tips.
-
….
On the concrete benefits side, ditching the mode method allows you to use the mode switch for something other than switching modes. There are downsides to the keyboard emulation route. SimHotasPinkyShift’s behavior is impossible to replicate any other way if that appeals to you. You want to discount the psychological factors but my position is the mindset is a huge factor. Having so many control slots encourages one to put non-fingertip controls at fingertips which encourages poor preparation patterns. “I don’t have to set things up before combat because all my controls are so convenient.” I’ve troubleshooted situations where someone had extra fantasy callbacks bound that caused actual avionics bugs (e.g. SimNextAGWeapon). None of these were direct consequences of the Saitek 3-mode cult but were precipitated by it. I’ve had people crash or be shot down because “sorry lulz I was in the wrong mode.” I’m not saying it’s wrong but I think a happier life is had elsewhere.
Yes, exactly. Nice post.
Once I learned how to apply DX commands and recognized the benefit of a profile with the F16 SSC & Throttle as a foundation, I came to exactly the same conclusions ……
….
Thoughts on the ‘lost’ mode states on the X52 Pro:
As many may note, using DX functionality limits the number of programmable buttons on the X52 Pro by a significant factor compared to using the Saitek profile software and having 3 Modes each, potentially, with it’s associated shift state. I realize this limitation and accept it on the basis of:- I don’t need that many buttons;
- My opinion is that the addtional complication as far as ‘managing’ what mode and/or shift state I’m in is counter-productive (i.e. Risk > Reward);
- DX programming ‘cuts out the middle man’ reducing potential conflicts between Saitek software and BMS;
- Although not ‘Cougar Accurate’, DX programming is closer to realistic F-16 stick functionality;
Others will of course have other opinions and they may use or not use, modifiy or not modify, this profile to fit their own needs and their own view of the sim.
….
Of course, I begrudge no one their own philosophy in implementing the BMS sim and/or ‘realistic’ keyfiles …. that is a user specific decision and is ‘transparent’ (or should be) to other users.
-
I’m a grumpy puss so don’t take what I’m saying too harshly. Have a look at a diagram of the F-16 controls and again at the X-55. If you have a “direct DX” wishlist I’m more than happy to help with key files and the like.
-
Snell created an outstanding X-55 profile. It emulates the real HOTAS very closely, includes reasonable and useful things on the throttle switches, and uses only Mode 1.
See his thread at the top of this forum or here: https://www.benchmarksims.org/forum/showthread.php?24506-X55-keyfile-Full-DX-Programmed'Rabbit
-
Snell created an outstanding X-55 profile. It emulates the real HOTAS very closely, includes reasonable and useful things on the throttle switches, and uses only Mode 1.
See his thread at the top of this forum or here: https://www.benchmarksims.org/forum/showthread.php?24506-X55-keyfile-Full-DX-Programmed'Rabbit
Have to agree with AttackRabbit about Snelles profile, good package for X-55 owners wanting to ditch the saitek software for DX.