Jump to content

Recommended Posts

Posted

This drives me crazy. I had now two problems trying to program commands to the x52 Pro with the Saitek software. With an Su-25 profile and a huey.

 

I map Mode 1 T1 (switch 1) to Flaps up (shift+f) and T2 flaps down (ctrl+f) and it works perfect. Then I switch to Mode 2 and map T1 to Ripple Number (LCtrl+space) and T2 to Ripple interval (V) and T1 doesn't respond!

 

There is no way for me to program Lctrl+space to either T1 or T2 or fire A or anything, no matter what mode. I'm so damn frustrated with this I don't even want to play. I know it's a small detail, but I pay so much money for something I expect it to work the way it's advertised.

 

If anyone has ANY suggestions, I'd be really appreciative.

Posted

Sounds like you're mapping keyboard commands to the buttons with the SST software, is that right?

 

If so, forget that and do it in DCS.

i5-4670K@4.5GHz / 16 GB RAM / SSD / GTX1080

Rift CV1 / G-seat / modded FFB HOTAS

Posted

That's exactly what I've been doing. So just map directly through DCS? Am I still able to use the Mode modifier when I do that? I like my modes lol. I know I can use the pinkie modifier but I'm just curious if the mode selector will work. I'll try it out.

 

Also, has anyone used vJoystick or similar software? Basically, a similar keymapping program? It is much easier to do outside DCS but if it's no choice it's no choice.

 

Thanks for the reply.

Posted

Blooze, thanks for the tips. But it didn't effect anything. While I was testing it, I noticed the Ctrl Space Ctrl Space works. But Ctrl Ctrl Space Space doesn't. And I literally didn't nothing different. There is no time delay set either. So bizarre.

 

7fFij5b.jpg

 

What I'm just doing is setting the command I want to a more simple keystroke in DCS and then mapping that button in the SST software. It's a work around but I just want it to work normal lol.

 

Thanks again.

Posted

Joystick assignments are per-aircraft in DCS. If you want to use modes to switch aircraft, that'd be redundant.

 

If you want modes for "Fly-Shoot-Land" or something like that, the mode selector switch can be recognized as a button in DCS, which you could use as the modifier.

 

The SST software is so infuriating, I use it as little as possible. Mainly I have it setup with bands on the spiking sliders and dials, mapping the ministick to slew keys, and that's about it.

i5-4670K@4.5GHz / 16 GB RAM / SSD / GTX1080

Rift CV1 / G-seat / modded FFB HOTAS

Posted (edited)

When you are pressing the keyboard keys to program a button and you are assigning a combination of 2 keystrokes for one button you must press both keys at exactly the same time rather than one after another with a pause in between. When you test and see this Ctrl Ctrl Space that indicates that you didn't press both keys at exactly the same time but rather one key after another and that will never work.

Edited by Blooze
Posted (edited)

Blooze, you are 100% right. Thank you so much! cough and sorry for saying SST is shit cough

 

I thought with the time delay set to 0 there won't be any difference. Plus there was no interface distinguishing between Ctrl Space and Ctrl + Space on the SST software. But again, thanks everyone for all the replies! I'll make sure to return the favor if anyone has the same problem.

 

Cheers to an awesome community.

Edited by skendzie
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...