RShift in SST

[JD_LincsUK]

This may have been covered before - on searching, there were hundreds of results, the first few dozen were nothing to do with my issue.

 

Basically, I've been having some issues on the rookie missions which turned out to be due to actions programmed to my X52 via SST, that were not activating on button push.

 

For example the laser rangefinder switch and some other targeting actions.

 

On inspecting the profile in SST, I find that it is not accepting the right shift key as a qualifier, or at all, in fact.

 

Neither in key-press, macro or record mode.

 

Does anyone have a solution to this, or am I going to have to start reassigning functions in the controls menu? (again :bored: )

 

TiA

 

JD

[Haukka81]

This may have been covered before - on searching, there were hundreds of results, the first few dozen were nothing to do with my issue.

 

Basically, I've been having some issues on the rookie missions which turned out to be due to actions programmed to my X52 via SST, that were not activating on button push.

 

For example the laser rangefinder switch and some other targeting actions.

 

On inspecting the profile in SST, I find that it is not accepting the right shift key as a qualifier, or at all, in fact.

 

Neither in key-press, macro or record mode.

 

Does anyone have a solution to this, or am I going to have to start reassigning functions in the controls menu? (again :bored: )

 

TiA

 

JD

 

Hi, do you have latest saitek SST software ?

 

I have X52pro and with latest SST software it records right shift just fine :thumbup:

 

 

And btw.. here is my current profile :joystick:

[Speed_2]

Hmm... my Saitek software is version 6.6.6.9, and it also doesn't recongize RShift (I think it also has a problem with RAlt or RCntrl too). I just had to reassign RShift keystrokes to something else in the BS UI to get it to work.

[MTFDarkEagle]

Sounds to me like you have a outdated sst software. Just as haukka81 said, I too have no problems macro-ing right shift and ctrl.

[CyBerkut]

Along with checking the SST software version, also make sure you have the latest drivers (appropriate to your operating system).

[Boulund]

I remember a year ago a lot of people on these forums where asking the same thing. Saitek solved this issue in the latest version of SST (which was almost a year ago now).

Try updating drivers and software

[JD_LincsUK]

Thanks for the replies - I'll check it out.

 

I usually keep up to date with drivers and software, but I currently have so many, it's easy to miss one out :)

 

I also recall having lots of problems with some SST releases in the past. I probably thought I'd stick with one that worked - I've not had problems with the version I'm on before now (updated when Win7 retail was released).

 

I just checked and it's 6.0.10.7 - it's the 64bit version (if there's any difference).

 

I downloaded it on 30 Dec 09, but it is dated 21 Jan 09. I'll go look what they are offering at Saitek.

 

JD

Edited February 2, 2010 by JD_LincsUK

[JD_LincsUK]

Turns out I do have the latest - reinstalled anyway and it still won't work.

 

Re-assign it is, then. :disgust:

 

JD

[CAT_101st]

OK guys here is the problem with using the SST softwair. Lits say you program button C as your trimer. theproblem you will run into is that the DX button is still active and programed in game setting. so you get 2 actions for 1 button push. some times the combonation of the two make a diffrent switch flip in game. The only real way to program the X52 for DCS is to load a blank SST profile and go in the options of BS and set the DX butons to what you want. This is the only sure fire way to have zero problems with the X52. T1-T6 are the only buttons that I have found not to have a conflict in the game.

The other option is to go thrue the BS controles and find all the actions assined to the DX buttons and clear them. But buy the time you do that you culd have created your own in game profile. But if you want to use the mode option of the X52 you will have to go thrue and clear all the DX acttions.

[JD_LincsUK]

That doesn't address the issue being discussed.

 

However, I have re-assigned the required actions with qualifiers other than RShift and RAlt and have the problem sorted.

 

JD

[airtom]

This is weird. I have X52 and don't have problem with any keyboard shortcut at all. Some of shortcuts you must set via advanced command and not just simple keypress. That's the problem with all SST versions as far as I know (also discussed somewhere in the forum). But can be solved the way I just described.

Edited February 3, 2010 by airtom

[JD_LincsUK]

Yes, it is weird - but it's nice to at least see that I'm not alone with this problem.

 

As mentioned, I have tried all the available methods of input and those keys just aren't recognised at all by SST.

 

It may be the keyboard itself, it may be something with the version of windows - who knows? Something is preventing SST from recognising right shift.

 

Later today, I'll try using it with Voice Buddy and see how I get on - just to check if it acknowledges that input or not.

If not, I'll try a different keyboard - but I'm not gonna spend too much time trying to solve it, as the initial issue is resolved.

 

JD

[airtom]

Later, this evening, I'll take a look at my SST X52 config again and will try to reproduce your RSHIFT problem. I can post here my X52 profile for you to try it on your pc.

 

Also check, if on your system is not running another software binding global keyboard shorcuts. Could be graphic card software, Fraps, etc.

[Ramstein]

Yes, it is weird - but it's nice to at least see that I'm not alone with this problem.

 

..............

JD

 

 

are you sure you are not programming both the Saitek SST Profile long with the BS ingame controls? As you cannot map the keys for both.

 

The only in game controls you should map are what already are mapped along with the Saitek stick Axis for Joystick.. and Rudder Pedals (if any..)

 

here is a snapshot at:

http://forums.eagle.ru/showthread.php?t=39314

 

all other keyboard commands are through the Saitek SST profile.

 

Also,

 

I really think no one else is having any key problems since the later Saitek SST and driver versions came out in 2009.

 

IMHO

Edited February 3, 2010 by Ramstein

[CyBerkut]

JD, which Operating System are you using, and which version numbers of the SST software and drivers do you have installed?

[airtom]

I looked at my profile and all keyboard shortcuts using any qualifier are working. But as I said, they are set via "Advanced Command". So do it also this way - "New Advanced Command" in context menu (not New Key Press!).

 

SST version: 6.6.6.9 (64bit)

OS: Windows Vista 64bit

(also used both 32bit version and worked fine)

 

I attach my profile. Take a look at it.

BlackShark.zip

[Haukka81]

Or take a look my profile, i use just new key press. No need for adv.command :)

[airtom]

Or take a look my profile, i use just new key press. No need for adv.command :)

 

I'm pretty sure, you will not be able to do all my advanced commands via simple key press ;) Some qualifiers were not working as key press. I used advanced commands for all qualifiers just in case, as I didn't have any problem.

 

And JD doesn't have X52 Pro, but non-Pro version. Or you do JD?

Edited February 4, 2010 by airtom

[JD_LincsUK]

It's the standard X52.

 

I've tried a second keybaord - same story.

 

Anyway, as I said - I have got around the issue by re-assigning the actions and functions that require the right shift keypress.

 

I mentioned R Alt (or Alt Gr if ya like) in a previous post, but that's okay.

 

Thanks for the input - I have a few years' experience of SST, but I won't feel insulted by the one or two painfully obvious suggestions here or not reading my posts properly :smartass: , I know you don't know that. (and I'm a sceptical old git :D )

 

My SST profiles for LO:FC have, in fact, been downloaded around 3,000 times - so I must be doing it competently.

 

Anyway, like I said before, I really don't want to make the big investigation on this - I've got around it and I'm happy with the result - I actually stopped subscribing to this thread yesterday as I though it was finished with - that's why I am late responding to queries :)

 

I tested my SST profile last night and all is working well.

 

See you on the front :joystick:

 

JD

Edited February 4, 2010 by JD_LincsUK

[Ramstein]

I am curious, regarding the issue,,

 

When you installed the latest SST an Drivers, did you write over the old ones, or did you completely uninstall the old ones and only then install the new ones?

 

:joystick: