Alternative to SST software for x52 control?

[ShuRugal]

I am trying to find a better solution than the Saitek SST software for interfacing my x52 with BS2.

 

The problem i am running up against with SST is that since it outputs keystrokes for button presses, i can only operate one button at a time for the desired result. It also causes considerable headache with commands that require multiple keypresses to be commanded, especially when the framerate is low, and BS2 will often misinterpret the commands from SST and instead of getting the desired switch flipped, something else entirely happens because BS missed some of the keystrokes that SST was trying to feed it.

 

Someone suggested helios, and ive gone an grabbed a copy and started fiddling with it, and it appears to be capable of what i want to do (map x52 button presses directly to BS2 controls, instead of to keystrokes) but i cannot for the life of me figure out how to go about doing it.

 

Essentially, i want to preserve the SST functions of multiple modes and the shift trigger, but i want to be rid of the cumbersome keystroke-output method of interfacing with the simulator.

 

any help appreciated.

[cichlidfan]

I am trying to find a better solution than the Saitek SST software for interfacing my x52 with BS2.

 

The problem i am running up against with SST is that since it outputs keystrokes for button presses, i can only operate one button at a time for the desired result. It also causes considerable headache with commands that require multiple keypresses to be commanded, especially when the framerate is low, and BS2 will often misinterpret the commands from SST and instead of getting the desired switch flipped, something else entirely happens because BS missed some of the keystrokes that SST was trying to feed it.

 

Someone suggested helios, and ive gone an grabbed a copy and started fiddling with it, and it appears to be capable of what i want to do (map x52 button presses directly to BS2 controls, instead of to keystrokes) but i cannot for the life of me figure out how to go about doing it.

 

Essentially, i want to preserve the SST functions of multiple modes and the shift trigger, but i want to be rid of the cumbersome keystroke-output method of interfacing with the simulator.

 

any help appreciated.

 

To the best of my knowledge, Helios is not going to do it because it has no tools to support the X-52.

 

Your best bet is to PM Gadroc, the creator of Helios, or post on the SCSimulations forum.

[ShuRugal]

okay, how about a different software then?

[HiJack]

You must be doing something wrong in the programming. Do you set "Quantize Time" to 0 and "Set Delay" 0,100 on the key you want to be pressed?

[PeterP]

Autohotkey gives you way more than you would ever need - it comes not with a fancy GUI but it is more advanced as SST/FOXY/Target when in the right hands ...: http://www.autohotkey.com/

 

IMHO: And when you have made your first steps how to use the scripting language you will never look back and think to use other solutions.

 

Please use the AHK help function and very detailed documentation to write your scripts.

 

A simple examples of "advanced" ;) controller scripting: http://forums.eagle.ru/showpost.php?p=1397590&postcount=17

[ShuRugal]

You must be doing something wrong in the programming. Do you set "Quantize Time" to 0 and "Set Delay" 0,100 on the key you want to be pressed?

 

 

yes, i am doing something wrong. What i am doing wrong is playing BS2 on a computer that was high-end three years ago, but is only middle of the road now, and sometimes the frame-rate gets low enough that BS2 doesn't properly receive SST keystrokes.

 

and even if that weren't a problem, it's still a PITA not to be able to press more than one button on the x52 simultaneously.

 

Autohotkey gives you way more than you would ever need - it comes not with a fancy GUI but it is more advanced as SST/FOXY/Target when in the right hands ...: http://www.autohotkey.com/

 

IMHO: And when you have made your first steps how to use the scripting language you will never look back and think to use other solutions.

 

Please use the AHK help function and very detailed documentation to write your scripts.

 

A simple examples of "advanced" controller scripting: http://forums.eagle.ru/showpost.php?p=1397590&postcount=17

 

unless i am reading something wrong, AHK still translates button presses into keystroke macros, which is exactly what i don't want.

Edited March 10, 2012 by ShuRugal

[cichlidfan]

It is begining to sound like you want something that you are not going to get unless you build your own controller. You really have two choices, either you get DX codes out of the X-52 and process them through something that will generate a key sequence (AHK, SST or something else); or you map the DX codes directly to the sim.

 

Once you want multiple modes from the Saitek you can't just send out raw data because there are not enough DX codes (32 buttons, 8way hat and your axis functions).

[Sel94]

I have an X-52(pro), and also not a very good computer, but I don't get the problems you are getting. Are you sure you're using SST correctly?

[PeterP]

unless i am reading something wrong, AHK still translates button presses into keystroke macros, which is exactly what i don't want.

No - AHK translate directly DirectX commands into key-strokes.

AHK is not HID-Makro

 

 

...but I get also the feeling that something isn't set-up right in your system....

[ShuRugal]

Once you want multiple modes from the Saitek you can't just send out raw data because there are not enough DX codes (32 buttons, 8way hat and your axis functions).

 

this is what i was afraid of. It wouldn't be a problem if DCS would recognize a joy button as a shift modifier (and if the mode switch could be set to behave as 3 different shift modifiers). any way to do this perhaps?

[cichlidfan]

this is what i was afraid of. It wouldn't be a problem if DCS would recognize a joy button as a shift modifier (and if the mode switch could be set to behave as 3 different shift modifiers). any way to do this perhaps?

 

DCS will recognize a joystick button as a shift modifier. As many as you wish for that matter. Look in the GUI manual starting around page 19.

 

The mode switch is an issue with how Saitek implimented it.

 

EDIT: BTW, I agree that you have another issue here.

[Puddlemonkey]

I scrapped the mode button and set button D on the throttle as a modifier in DCS - kind of a shift button on my joystick. Having done that, every joystick button has two modes which brings it close to that of the SST (which has 3).

 

I found that to be plenty.

 

It is a shame that DCS haven't programmed BS so that joystick modifier buttons are separate to keyboard modifier buttons. You could emulate the SST completely then as you would set each position of the mode knob as a modifier. I tested this and it works but to use it, I would have to edit every single keyboard command to include all permutations of the mode knob.

[Bungle_uk]

For some reason DCS removed the ability to have both a modifier and a switch function in BS2(this was present in BS1). I dont know why that has been done otherwise you could have used that system. Maybe a dev can chime in on that one.

 

But to be honest, the Shark doesnt have so many controls that you need to get at quickly and using the shift function is more than adequete I find myself to create enough functions on the stick, note I am using the cougar though but I believe the Saitek has about the same buttons available.

[cichlidfan]

For some reason DCS removed the ability to have both a modifier and a switch function in BS2(this was present in BS1). I dont know why that has been done otherwise you could have used that system. Maybe a dev can chime in on that one.

 

The lack of a switch option is true for A-10 as well, although the 'up-to-date' manual still shows the switch information. It took a two page thread just to get someone to realize what had been done but no explanation has been given.

[sungsam]

Maybe you can use Pinnacle Game Profiler software. I use it to program xbox360 controller profiles for games that dont support it. It works perfect, it is not free and it detects my X52 and saitek pedals. But i dont ever use it like that. It is beter to ask on Pinnacles forum. :smartass::)

[MeerCaT]

Just a quick note to say that I have several buttons on my X52 setup as 'modifiers' within BlackShark. It is possible to configure any keyboard, mouse or joystick button as a modifier. Just click the "Add Modifier" button and the rest is fairly intuative, as ar as I can remember. Oh I think I remember one small 'quirk' being that one of the buttons (I think it was "OK" or "Add") on the popup dialig box was visually represented as being disabled when in actual fact it was enabled/functional.

[Fjodow]

...IMHO: And when you have made your first steps how to use the scripting language you will never look back and think to use other solutions...

 

I would use this to combine e.g. 3 commands to one button in Black Shark.

 

Is this the right tool for it?

[Fjodow]

O.K.

But I mean, do the following when I press e.g. "fire":

activate:

Laser standby

Moving ground target

Auto track

[Fjodow]

O.K.

But I mean, do the following when I press e.g. "fire":

activate:

Laser standby

Moving ground target

Auto track

 

SOLVED:

 

The SST software is the solution.

I programmed macros - different keys with different time delays, so this works.

But there's much more to do:

 

Press and hold fire, then you follow your rocket flight for e.g. 3 secs, then e.g. 3 secs you see your target, then back to your cockpit view - only until you hold the fire button. If you leave the fire button, you have your "normal" view again.

This is my task this weekend...

[HiJack]

That should be possible in SST but the software (or the stick) have a tendensy to lock up if the macro gets to complex. And if you then ALT+TAB back to the desktop the macro is still running and awesome things can happen ;) So take care and test each step in the macro. Hope you make it.

 

(HJ)

[Fjodow]

Thank's a lot.

:book: I'll do my very best...