how to use Saitek X52 Pro directly mapped to DCS?

[fitness88]

I don't want to use the Saitek software anymore but when I try to map directly to DCS it doesn't respond. It responds when I map only through the Saitek software.

How do I do this?

 

 

Thank you.

[MadDog-IC]

I don't want to use the Saitek software anymore but when I try to map directly to DCS it doesn't respond.

 

It responds when I map only through the Saitek software.

How do I do this?

 

Thank you.

 

Need to stop SST from loading any of it's profiles.

 

• Right click on SST profile editor on task bar and "Clear Startup".
  
• Right click on SST profile editor on task bar and "Clear Profile".
  
• MFD on X-52 Pro Throttle must read "NO PROFILE".
  
• Now go into DCSW and map buttons as normal.(May take a few presses of each button to register though)
  

Regards, Ian.

Edited March 25, 2017 by MadDog-IC

[fitness88]

Need to stop SST from loading any of it's profiles.

• Right click on SST profile editor on task bar and "Clear Startup".
  
• Right click on SST profile editor on task bar and "Clear Profile".
  
• MFD on X-52 Pro Throttle must read "NO PROFILE".
  
• Now go into DCSW and map buttons as normal.(May take a few presses of each button to register though)
  

Regards, Ian.

 

 

 

Thanks for your reply MadDog-IC.

• With the new drivers for Windows 10, 7.0.53.6 I've never seen any profiles on my MFD including NO PROFILE, just the clock time. My older drivers showed all this information but not these but they are very stable in game.
  
• Am I only able to use commands only from the SST software 'OR' DCS mapped commands when flying, not from both at the same time? I wanted to use certain commands using SST software and others using DCS mapped commands when flying.
  
• Just last night I discovered if I have the Saitek control panel open it stops any commands from the SST software to work and allows only commands that I've mapped in DCS but I want to use different commands from both SST and DCS:
  

Edited March 25, 2017 by fitness88

[ricktoberfest]

how to use Saitek X52 Pro directly mapped to DCS?

 

I use the profiler for 90% of the commands, only using DCS to program certain buttons like the first stage of a dual stage trigger. Profiler is much easier as it never gets deleted by an update. Also makes it easier to use shift functions on my pinky button

 

 

-Tapatalk

[fitness88]

I use the profiler for 90% of the commands, only using DCS to program certain buttons like the first stage of a dual stage trigger. Profiler is much easier as it never gets deleted by an update. Also makes it easier to use shift functions on my pinky button

 

 

-Tapatalk

 

 

 

 

Thanks Tapatalk,

How do you use both SST profiler and DCS commands at the same time? When I try to do that, because I too like some of the features of SST, only one or the other works not both SST profiler and DCS commands at the same time.

[ricktoberfest]

Thanks Tapatalk,

How do you use both SST profiler and DCS commands at the same time? When I try to do that, because I too like some of the features of SST, only one or the other works not both SST profiler and DCS commands at the same time.

 

 

 

Just leave the buttons you want DCS to program as unprogrammed in the saitek profiler. Then in dcs you program them as regular joystick buttons. When the saitek profile is active the unprogrammed buttons just work like regular joystick buttons

 

 

-Tapatalk

[fitness88]

Just leave the buttons you want DCS to program as unprogrammed in the saitek profiler. Then in dcs you program them as regular joystick buttons. When the saitek profile is active the unprogrammed buttons just work like regular joystick buttons

 

 

-Tapatalk

 

 

Are you saying that all buttons not used in sst should be set to 'unprogrammed' and not 'do nothing'?

I don't understand why sometimes when I map a j-stick button in DCS and it takes, other times I try and it doesn't take, what it does is show up as a modifier like alt or ctrl, etc.

Edited March 25, 2017 by fitness88

[ricktoberfest]

Are you saying that all buttons not used in sst should be set to 'unprogrammed' and not 'do nothing'?

I don't understand why sometimes when I map a j-stick button in DCS and it takes, other times I try and it doesn't take, what it does is show up as a modifier like alt or ctrl, etc.

 

 

 

Not near my computer to check the terminology but try both ways. Also it doesn't really work to use a shift button programmed in saitek and a button press in DCS.

 

Also sometimes you have to push the joystick button several times for DCS to register it on their programming end

 

 

-Tapatalk

[fitness88]

Not near my computer to check the terminology but try both ways. Also it doesn't really work to use a shift button programmed in saitek and a button press in DCS.

 

Also sometimes you have to push the joystick button several times for DCS to register it on their programming end

 

 

-Tapatalk

1. Actually if I don't do any mapping through sst, setting up Mode and Shift as modifiers actually works perfectly through DCS.
   
2. The difficultly I'm having is using the sst for a couple of 'Advanced' key setups while using #1. I use an empty sst profile with only 2 or 3 key maps on it and the rest through DCS.
   

In order for #1. to work I must have the Flight Controller Properties open [as shown previously] but when Flight Controller Properties is open it does not allow any commands mapped using SST to function...if Flight Controller Properties is closed all SST commands mapped work fine but nothing will function mapped in DCS.

 

 

I know there must be a j-stick .lua file that needs deleting besides the ones I know about in saved games.

Edited March 25, 2017 by fitness88

[Headwarp]

1. Actually if I don't do any mapping through sst, setting up Mode and Shift as modifiers actually works perfectly through DCS.
   
2. The difficultly I'm having is using the sst for a couple of 'Advanced' key setups while using #1. I use an empty sst profile with only 2 or 3 key maps on it and the rest through DCS.
   

In order for #1. to work I must have the Flight Controller Properties open [as shown previously] but when Flight Controller Properties is open it does not allow any commands mapped using SST to function...if Flight Controller Properties is closed all SST commands mapped work fine but nothing will function mapped in DCS.

 

 

I know there must be a j-stick .lua file that needs deleting besides the ones I know about in saved games.

 

This guy's got a point. As far as DCS goes when I was using my x52 pro the only thing I programmed were 3 stage bands on the mouse/slew nub x and y axes and asign that to the keys that controlled slew. I also put bands on the rotaries and turned them into china hat/boat switch on throttle. In SST I would delete any kind of shift state modifier, and in control panel I would disable clutch mode so the clutch button would perform as a normal button.

 

I'd set one of my buttons in the game as a modifier which allowed for the rest of the stick/throttle to have 2 functions each. Modified and unmodified, basically giving you all the hat switches and buttons you might need to have full hotas control of even the A-10C.

 

Good luck with your Saitek. I'm going on memory here.. as I don't use one anymore.

Edited March 25, 2017 by Headwarp

[fitness88]

This guy's got a point. When I was using my x52 pro the only thing I programmed were 3 stage bands on the mouse/slew nub x and y axes and asign that to the keys that controlled slew. In SST I would delete any kind of shift state modifier, and in control panel I would disable clutch mode so the clutch button would perform as a normal button.

 

I'd set one of my buttons in the game as a modifier which allowed for the rest of the stick/throttle to have 2 functions each. Modified and unmodified, basically giving you all the hat switches and buttons you might need to have full hotas control of even the A-10C.

 

Good luck with your Saitek. I'm going on memory here.. as I don't use one anymore.

 

 

 

Thanks for the follow up and for mentioning using the clutch button for mapping...now that the MFD and changing profiles on the fly in windows 10 doesn't work unless I use an unstable driver which I tried and it was bad.

Well I gave up and went back to mapping everything through sst and everything is fine with one command mapped through DCS besides the UI commands which you have to map in DCS.

I just couldn't figure out the mentality of how these 2 software worked with each other.

[MadDog-IC]

 

Well I gave up and went back to mapping everything through sst and everything is fine with one command mapped through DCS besides the UI commands which you have to map in DCS.

 

I just couldn't figure out the mentality of how these 2 software worked with each other.

 

As other user has said, apart from other issues the drivers may have, If you program a joystick button in SST it can't be programmed in DCSW and Modifier joystick buttons in SST will not be recognised in DCSW.

 

In SST:

 

• Program joystick buttons to what every you wish.
  
• Program modifier buttons or modes.
  
• Don't program any thing to joystick buttons or axis you want to use in DCSW. (Leave them as UNPROGRAMMED)
  

In DCSW:

 

• Program joystick buttons to what every you wish that weren't assigned in SST.
  
• Program modifier buttons, You just can't use the same ones as SST has programmed.
  

That is as simple as I can describe it, I appreciate these things can be hard to grasp at times.

 

Regards, Ian.

[ricktoberfest]

Just got home and checked. So for example on a 2 stage trigger:

First stage is unprogrammed in saitek but programmed in DCS. Second stage is programmed in saitek profiler. Shift and modes are programmed in saitek profiler (although I only use mode 1)

 

Looking at your screenshot you are using different drivers than me and/or the x52 pro. I'm using an original x52 from 10 years ago

 

 

-Tapatalk

[fitness88]

As other user has said, apart from other issues the drivers may have, If you program a joystick button in SST it can't be programmed in DCSW and Modifier joystick buttons in SST will not be recognised in DCSW.

 

In SST:

• Program joystick buttons to what every you wish.
  
• Program modifier buttons or modes.
  
• Don't program any thing to joystick buttons or axis you want to use in DCSW. (Leave them as UNPROGRAMMED)
  

In DCSW:

• Program joystick buttons to what every you wish that weren't assigned in SST.
  
• Program modifier buttons, You just can't use the same ones as SST has programmed.
  

That is as simple as I can describe it, I appreciate these things can be hard to grasp at times.

 

Regards, Ian.

 

 

 

 

 

Yes I am starting to see where conflicts will occur when mapping to both DCS and SST. I was successful using the MODE and SHIFTSTATES as modifiers in DCS. Setting up layers worked well using them. It was only when I tried using both DCS and SST that I ran into problems and now I have a better understanding of how they work with each other...thanks.