Saitek Joystick Modes

[Tregarth]

I have started to use a Saitek X52 joystick and see I have 3 separate Modes.

a) Can I program each of the modes in FSUIPC?

B) If so how can I do it,please?

Also I would like to assign the FSX F2 Thrust Reverser command to a joystick button. I have looked in Buttons & Switches, pressed a button, selected "Select for FS control" and looked in the "Control sent" window but cannot see a Thrust Reverse command. I have tried looking in Key Presses tab and drawn a blank there, too.

I have used the default FSX B737 but cannot make the reverser work.

What command should I be looking for, please?

I am using FSX with Win 7.

Thank you.

[Pete Dowson]

I have started to use a Saitek X52 joystick and see I have 3 separate Modes.

a) Can I program each of the modes in FSUIPC?

Do all the buttons and switches show as different buttons in FS or FSUIPC for each mode? If so: yes, just by simple assignment as you would in FS.

If the answer is no, then it depends on whether the mode switch itself is seen, because then there are ways of setting flags or conditions for each mode. If it is, you can program by INI file editing, using the conditional actions as documented in the Advanced Users document.

Also I would like to assign the FSX F2 Thrust Reverser command to a joystick button. I have looked in Buttons & Switches, pressed a button, selected "Select for FS control" and looked in the "Control sent" window but cannot see a Thrust Reverse command.

There's no such thing, that's why. FS's "F2" button is assigned to "Throttle Decr". So the FS command to use is "Throttle Decr" (or, for different engines, ThrottleN Decr where N is the engine number).

I'm pretty sure you can assign these in FS as well. And if you look at the FS assignment for the F2 key you would have found the correct command.

I have used the default FSX B737 but cannot make the reverser work.

Sorry, I don't know what you mean by this. Using F2, or using the mouse on the throttle quadrant reversing levers, you can't engage reverse?

Pete

[Tregarth]

Do all the buttons and switches show as different buttons in FS or FSUIPC for each mode? If so: yes, just by simple assignment as you would in FS.

If the answer is no, then it depends on whether the mode switch itself is seen

The buttons etc do not show as different buttons in FSUIPC. If they did I would not be asking the question.

How can I tell if the mode switch is seen? What test can I carry out to find out if this is so?

For info the F2 button is assigned to "Throttle Decrease" in FS, but holding it down it becomes the "Reverse Thrust" command which is what I want, hence the question.

By saying I was using the default FSX 737 I was trying to point out I was using a plane with thrust reversers so if the command worked it would be apparent on the aircraft.

Do all the buttons and switches show as different buttons in FS or FSUIPC for each mode? If so: yes, just by simple assignment as you would in FS.

If the answer is no, then it depends on whether the mode switch itself is seen, because then there are ways of setting flags or conditions for each mode. If it is, you can program by INI file editing, using the conditional actions as documented in the Advanced Users document.

There's no such thing, that's why. FS's "F2" button is assigned to "Throttle Decr". So the FS command to use is "Throttle Decr" (or, for different engines, ThrottleN Decr where N is the engine number).

I'm pretty sure you can assign these in FS as well. And if you look at the FS assignment for the F2 key you would have found the correct command.

Sorry, I don't know what you mean by this. Using F2, or using the mouse on the throttle quadrant reversing levers, you can't engage reverse?

Pete

[Gypsy Baron]

-SNIP-

How can I tell if the mode switch is seen? What test can I carry out to find out if this is so?

If the X52 is similar to the X45, the Mode switch is seen as a seperate 3-position switch.

In the WinXp control panel Game Controllers page if you select the X52\Properties you should

see it listed under the "Switches" heading.

In FSUIPC, under the Buttons + Switches tab, if you activate the mode switch you

should see the data in the Joynumber and button windows change. These would be the codes

you would use to create compound control functions.

That is, you would use the state of that switch as seen in FSUIPC to qualify/modify the functions

of the other buttons, axis, rotaries etc.

Paul

[Tregarth]

Dear Paul,

Good to hear from you again!

I am using Win 7 so the page names are, of course, different.

In Win 7 "Game Controller" = "Devices & Printers". This will eventualy take me to X52 Controller Properties. By rotating the knurled knob the 3 Mode positions show and the Mode no on the controller changes from 1 to 2 to 3.

Starting FSX and then FSUIPC when I go to "Buttons & Switches" if I press joystck button A in Mode 1 the Button Window shows Joy# 0 and Btn# 2. Changing to Mode 2 I see Joy# 0 and Btn# 28, then pressing button A the values revert to Joy# 0 and Btn# 2. Changing to Mode 3 the result is Joy# 0 Btn# 29. Again, presing A shows Joy# 0 Btn# 2.

Thus it seems that changing the Mode knob simply adds 2 more buttons to the controller rather than multiplying the number of controls by 3. Why anybody should want so many buttons I cannot guess, they must have a fantastic memory to remember them all.

It may be that FSUIPC cannot support X52 in Win 7, it would be good to have it confirmed one way or another.

I appreciate your help.

Best wishes for a Happy New Year.

If the X52 is similar to the X45, the Mode switch is seen as a seperate 3-position switch.

In the WinXp control panel Game Controllers page if you select the X52\Properties you should

see it listed under the "Switches" heading.

In FSUIPC, under the Buttons + Switches tab, if you activate the mode switch you

should see the data in the Joynumber and button windows change. These would be the codes

you would use to create compound control functions.

That is, you would use the state of that switch as seen in FSUIPC to qualify/modify the functions

of the other buttons, axis, rotaries etc.

Paul

[Gypsy Baron]

-SNIP-

Starting FSX and then FSUIPC when I go to "Buttons & Switches" if I press joystck button A in Mode 1 the Button Window shows Joy# 0 and Btn# 2. Changing to Mode 2 I see Joy# 0 and Btn# 28, then pressing button A the values revert to Joy# 0 and Btn# 2. Changing to Mode 3 the result is Joy# 0 Btn# 29. Again, presing A shows Joy# 0 Btn# 2.

This is exactly correct. The "Mode" knob looks just like 3 switches in FSUIPC or Win7 for that matter.

I suspect "Mode 1" will return "Joy#0 Btn# 27". So, you have Btn# 27,28,29 that represent the three different states

of the "Mode" knob.

It is up to you to use those states to modify how the other buttons/switches act in FSUIPC. You will not see those

other buttons/switches do anything different unless you program them to do so.

You need to spend some time studying the document "FSUIPC4 for Advanced Users.pdf" that is provided with the download

of FSUIPC4. Page 12 starts the section on Button Programming. Page 16 starts the discussions on the more advanced

methods of switch programming, which is what you will need for implementing the "Modes". The Saitek software

does this for you but is limited in it's usefulness. Tha FSUIPC facilities go far beyond what can be done with

the Saitek software. Essentially, you can have 5,6,10 or more "Modes" using the advanced programming methods

defined in the FSUIPC documentation. Add the Lua capabilities and the possibilities are endless!

I have over 70 functions defined for 10 switches on my Saitek dual quadrants using a form of the compound

button programming. That's essentially 7 "modes". I use the various capabilities of FSUIPC and Lua for

all my complex aircraft control assignments such that I rarely need to resort to keyboard or mouse inputs

when flying them. The time you spend investigating the advanced techniques will be well spent.

And keep that document "handy", along with "List of FSX controls.pdf" and "FSUIPC Lua Library.pdf".

I refer to those documents on a regular basis when setting up my Saitek X-45, Pro yoke and dual

throttle quadrant functions.

Thus it seems that changing the Mode knob simply adds 2 more buttons to the controller rather than multiplying the number of controls by 3. Why anybody should want so many buttons I cannot guess, they must have a fantastic memory to remember them all.

The "Mode" knob actually "adds" three additional switches/buttons to multiply the overall setup by "3". Recall also that

sticks like the X-45, and I assume the X-52, also have the "pinkie switch" that is essentially a "mode" switch.

As to remembering the various settings, on my A2A B-17G setup, I have 7 "modes" as mentioned above. To jog my memory I

created a 2D pop-up window with a BMP showing the fuctions assigned to each switch in each "mode".....I call those

"control sets". I also implement a little Lua plugin script that displays the "current control set" assignments

on the screen in a small Lua Display window for 10 seconds each time I change the control set switches (mode switches).

Here are the JPG representationsd of two of my BMP pop-up "reminder panels".

It may be that FSUIPC cannot support X52 in Win 7, it would be good to have it confirmed one way or another.

I appreciate your help.

Best wishes for a Happy New Year.

FSUIPC can support the X-52 with no problems. It is up to you to "extend" the capabilities:)

Paul

[Tregarth]

Dear Paul,

Thank you for your help. I have printed off all your words of wisdom and will now sit quietly in a corner to digest them together with the files. For info the page nos you referred to are now 19-25 in the updated FSUIPC 4 manual. I have been searching the internet and your advice pops up very frequently - Thank you.

I hope you had a good re-union with your shipmates from the USS Dewey and can remember it.

I will be back in contact with you soon to tell you of my progress (or lack of it!)

Cheers.

This is exactly correct. The "Mode" knob looks just like 3 switches in FSUIPC or Win7 for that matter.

I suspect "Mode 1" will return "Joy#0 Btn# 27". So, you have Btn# 27,28,29 that represent the three different states

of the "Mode" knob.

It is up to you to use those states to modify how the other buttons/switches act in FSUIPC. You will not see those

other buttons/switches do anything different unless you program them to do so.

You need to spend some time studying the document "FSUIPC4 for Advanced Users.pdf" that is provided with the download

of FSUIPC4. Page 12 starts the section on Button Programming. Page 16 starts the discussions on the more advanced

methods of switch programming, which is what you will need for implementing the "Modes". The Saitek software

does this for you but is limited in it's usefulness. Tha FSUIPC facilities go far beyond what can be done with

the Saitek software. Essentially, you can have 5,6,10 or more "Modes" using the advanced programming methods

defined in the FSUIPC documentation. Add the Lua capabilities and the possibilities are endless!

I have over 70 functions defined for 10 switches on my Saitek dual quadrants using a form of the compound

button programming. That's essentially 7 "modes". I use the various capabilities of FSUIPC and Lua for

all my complex aircraft control assignments such that I rarely need to resort to keyboard or mouse inputs

when flying them. The time you spend investigating the advanced techniques will be well spent.

And keep that document "handy", along with "List of FSX controls.pdf" and "FSUIPC Lua Library.pdf".

I refer to those documents on a regular basis when setting up my Saitek X-45, Pro yoke and dual

throttle quadrant functions.

The "Mode" knob actually "adds" three additional switches/buttons to multiply the overall setup by "3". Recall also that

sticks like the X-45, and I assume the X-52, also have the "pinkie switch" that is essentially a "mode" switch.

As to remembering the various settings, on my A2A B-17G setup, I have 7 "modes" as mentioned above. To jog my memory I

created a 2D pop-up window with a BMP showing the fuctions assigned to each switch in each "mode".....I call those

"control sets". I also implement a little Lua plugin script that displays the "current control set" assignments

on the screen in a small Lua Display window for 10 seconds each time I change the control set switches (mode switches).

Here are the JPG representationsd of two of my BMP pop-up "reminder panels".

FSUIPC can support the X-52 with no problems. It is up to you to "extend" the capabilities:)

Paul

[Gypsy Baron]

Dear Paul,

Thank you for your help. I have printed off all your words of wisdom and will now sit quietly in a corner to digest them together with the files. For info the page nos you referred to are now 19-25 in the updated FSUIPC 4 manual. I have been searching the internet and your advice pops up very frequently - Thank you.

I hope you had a good re-union with your shipmates from the USS Dewey and can remember it.

I will be back in contact with you soon to tell you of my progress (or lack of it!)

Cheers.

Thanks. Yes, I did have a great reunion with my Dewey shipmates old and new.

If you have any further questions/problems setting up your X-52 "modes" with FSUIC

just drop me a PM and I'll try to help you out as time permits.

Have a Happy New Year!

Paul

[Tregarth]

Dear Pete,

You replied to my earlier question about Modes "If the answer is no, then it depends on whether the mode switch itself is seen, because then there are ways of setting flags or conditions for each mode"

Following a lot of help from Gypsy Baron over the Christmas period the answer seems to be "No". I am using the default FSX Cessna and have programmed a set of instructions in the X52 stick's Mode 1 which works perfectly. What I had expected to happen was when I go to Mode 2 and press, say stick Button 2, nothing would happen. Instead the flaps still retract (a Mode 1 setting), using Mode 3 produces the same result. Thus only Mode 1 seems to be effective.

Rotating the Mode switch whilst in the Buttons & Switches tab shows no effect in the But# box or the Joy# box so it looks as if FSUIPC (version 4.60a dated 4/3/10) does not see the switch. 4.60a seems to be the most recent version which I registered earlier this year; does the fact I am using Win 7 32 bit have any relevance?

I have read your Advanced User manual and, with Gypsy Baron's help, have tried to use it. At one time I saw the values 27 and 28 in the Btn# window when I changed the Mode switch but these seem to have disappeared. Using your "Compound Buttons Instructions" I have used your template to add a line of code including button 27 but this does not work

Is there an update for Win 7 that I have missed?

For safety I have uninstalled and re-installed the Saitek drivers also, looking in the Saitek X52 Pro properties box rotating the Mode switch changes the Mode bars in the "Properties Window" and also the Mode number changes in the throttle MFD display so I know the stick is functioning properly.

I have tried ticking and un-ticking the Enable Controllers box in the Controller window but that does not make any difference.

I would appreciate your answer,

Thank you.

Do all the buttons and switches show as different buttons in FS or FSUIPC for each mode? If so: yes, just by simple assignment as you would in FS.

If the answer is no, then it depends on whether the mode switch itself is seen

The buttons etc do not show as different buttons in FSUIPC. If they did I would not be asking the question.

How can I tell if the mode switch is seen? What test can I carry out to find out if this is so?

For info the F2 button is assigned to "Throttle Decrease" in FS, but holding it down it becomes the "Reverse Thrust" command which is what I want, hence the question.

By saying I was using the default FSX 737 I was trying to point out I was using a plane with thrust reversers so if the command worked it would be apparent on the aircraft.

[Pete Dowson]

Rotating the Mode switch whilst in the Buttons & Switches tab shows no effect in the But# box or the Joy# box so it looks as if FSUIPC (version 4.60a dated 4/3/10) does not see the switch. 4.60a seems to be the most recent version which I registered earlier this year

There is a later version (4.645) in the Download Links subforum, but I doubt it would make any difference.

does the fact I am using Win 7 32 bit have any relevance?

No. FSUIPC4 uses DirectInput for its buttons and switch inputs and that supports 32 buttons of which FSUIPC sees all. That's DirectX8. Maybe DirectX9 or 10 or 11 supports more, but I doubt whether Saitek requires anything so recent as it would have limited their market. It sounds instead as if that switch is either interpreted internally, or only by their driver.

FSX itself wouldn't see it either. FSUIPC only sees what FSX can see.

There is a program called SPAD (see the Download Links subforum for a reference) which might be able to read it. It operates the USB protocol.

Is there an update for Win 7 that I have missed?

Win7 makes no difference whatsoever.

Regards

Pete

[jordanal]

Dear Pete,

You replied to my earlier question about Modes "If the answer is no, then it depends on whether the mode switch itself is seen, because then there are ways of setting flags or conditions for each mode"

Following a lot of help from Gypsy Baron over the Christmas period the answer seems to be "No". I am using the default FSX Cessna and have programmed a set of instructions in the X52 stick's Mode 1 which works perfectly. What I had expected to happen was when I go to Mode 2 and press, say stick Button 2, nothing would happen. Instead the flaps still retract (a Mode 1 setting), using Mode 3 produces the same result. Thus only Mode 1 seems to be effective.

Rotating the Mode switch whilst in the Buttons & Switches tab shows no effect in the But# box or the Joy# box so it looks as if FSUIPC (version 4.60a dated 4/3/10) does not see the switch. 4.60a seems to be the most recent version which I registered earlier this year; does the fact I am using Win 7 32 bit have any relevance?

I have read your Advanced User manual and, with Gypsy Baron's help, have tried to use it. At one time I saw the values 27 and 28 in the Btn# window when I changed the Mode switch but these seem to have disappeared. Using your "Compound Buttons Instructions" I have used your template to add a line of code including button 27 but this does not work

Is there an update for Win 7 that I have missed?

For safety I have uninstalled and re-installed the Saitek drivers also, looking in the Saitek X52 Pro properties box rotating the Mode switch changes the Mode bars in the "Properties Window" and also the Mode number changes in the throttle MFD display so I know the stick is functioning properly.

I have tried ticking and un-ticking the Enable Controllers box in the Controller window but that does not make any difference.

I would appreciate your answer,

Thank you.

Hi, the modal button does work and it changes the joystick # as seen by FSUIPC accordingly. The trick is, you must install the appropriate Saitek driver for your particular device and operating system. You do not necessarily need to install the Saitek SST software, just the driver. You'll know it's ready to work with FSIUPC if you can see the three-light modal button in the Game device calibration panel. I used to use it and have all sorts of button configurations with my Saitek Yoke and Throttle, but it got to be too much to remember and maintain, so I reverted to the KISS method a few years back.

[Tregarth]

Dear Jordanal,

Please see

Interesting discovery vis-a-vis Saitek "Mode" switch which is in this Forum.

Gypsy Baron was helping me; as a result of his help and support we found that the X52 properties window needs to be open to make Modes 2 and 3 work in the X52. The Mode button in the X52 Props window changes but nothing happens in FSU if the Props window is not showing. In addition a few buttons on the throttle now display which previously had shown in the Properties Window but not in FSUIPC.

If I close the X52 Properties window I lose Modes 2 and 3. Strange but true.

Thanks for your reply.

[scott967]

My suggestion would be if you are going to use fsuipc to program your Saitek, dump the Saitek drivers and just use the default win 7 ones. AFAIK all you get with the Saitek drivers is the "auto-calibrate" feature of Saitek which never worked well for me anyway.

scott s.

.

[nrcapes]

Dear Jordanal,

Please see

Interesting discovery vis-a-vis Saitek "Mode" switch which is in this Forum.

Gypsy Baron was helping me; as a result of his help and support we found that the X52 properties window needs to be open to make Modes 2 and 3 work in the X52. The Mode button in the X52 Props window changes but nothing happens in FSU if the Props window is not showing. In addition a few buttons on the throttle now display which previously had shown in the Properties Window but not in FSUIPC.

If I close the X52 Properties window I lose Modes 2 and 3. Strange but true.

Thanks for your reply.

I just got the X52 last week and read your post after trying to get FSUIPC 3.99 (registered)to work with FS9. It really is a strange situation. I found that the Saitek "clutch" button on the joystick that lets you switch profiles on the fly with the Saitek SST software shows 3 different button values with the X52 Properties window open and I change the Mode switch, but not when closed. Guess I will have to read Pete's buttin programming and use some other button to get different modes.

[Tregarth]

Good luck.

Despite Gypsy Baron's good work helping me sort out this mess i eventually went back to using the Saitek software. The Sitek instructions are not that helpful but once you have puzzled them out the stick works. Alternatively just use the FS set up instead, but don't try to use a combination of FS and SST. Only one or the other.

If you read Pete Dowson's reply to Gypsy Baron's post you will see that there does not seem to be a "workaround" to overcome the problem, which I why I went back to SST.

Tregarth

I just got the X52 last week and read your post after trying to get FSUIPC 3.99 (registered)to work with FS9. It really is a strange situation. I found that the Saitek "clutch" button on the joystick that lets you switch profiles on the fly with the Saitek SST software shows 3 different button values with the X52 Properties window open and I change the Mode switch, but not when closed. Guess I will have to read Pete's buttin programming and use some other button to get different modes.

[jetblst]

Actually, you can use the F2 button for reverse via the X52 and FSUIPC. I have done this many times with great success. However you have to check the "enable joystick" in MSFS using a mix of FSUIPC and your controller. Caviat here is that you might have your axes reset into MSFS rather than staying put via FSU. I find that rarely happens.

X52...

Select Buttons/Switches

GO TO THE SELECT FOR KEYPRESS SIDE.

Push "Set" Button.

Push your "F2" Button on your keyboard. (Selects Reduce throttles in MSFS).

Select Keypress to be repeated while held. (Self Explanitory).

Push the (Second) "Set" Button.

Push your F1 Button on your keyboard. (Sets your throttles to idle when you release whatever button you assign this to).

Enjoy!

(NOTE) After figuring out axis range and multiple commands on one axis I now have my reverses and spoilers on my x52 slider via FSUIPC. Seemed logical as in jets you'd use them in that combo on landings. Of course I set this into my jet profiles as well. Gotta love profiles.

[Tregarth]

Thanks for the info.

For my needs I find that I can get by with only the Saitek profiles. I would like to use the FSU profiles but it seems senseless to have a multimode stick which needs to have work arounds to make it function "as advertised".

But I will print your comments in case I ned to use them sometime.

Tregarth

Actually, you can use the F2 button for reverse via the X52 and FSUIPC. I have done this many times with great success. However you have to check the "enable joystick" in MSFS using a mix of FSUIPC and your controller. Caviat here is that you might have your axes reset into MSFS rather than staying put via FSU. I find that rarely happens.

X52...

Select Buttons/Switches

GO TO THE SELECT FOR KEYPRESS SIDE.

Push "Set" Button.

Push your "F2" Button on your keyboard. (Selects Reduce throttles in MSFS).

Select Keypress to be repeated while held. (Self Explanitory).

Push the (Second) "Set" Button.

Push your F1 Button on your keyboard. (Sets your throttles to idle when you release whatever button you assign this to).

Enjoy!

(NOTE) After figuring out axis range and multiple commands on one axis I now have my reverses and spoilers on my x52 slider via FSUIPC. Seemed logical as in jets you'd use them in that combo on landings. Of course I set this into my jet profiles as well. Gotta love profiles.

[mtjoeng]

.. For my needs I find that I can get by with only the Saitek profiles. I would like to use the FSU profiles but it seems senseless to have a multimode stick which needs to have work arounds to make it function "as advertised". ..

Use either the Saitek 'Mode' with software, or redefine everythiong in FSUIPC ('disable' joystick control)

for FSUIPC, to get the 3 'mode' positions back (they're reserved/hidden for Saitek software only):

Windows Saitek YOKE driver MODE 123

C:\Windows\System32\SaiD0BAC.pr0 <= mode123 <= (rename)/delete/(restart windows)

[von]

Use either the Saitek 'Mode' with software, or redefine everythiong in FSUIPC ('disable' joystick control)

for FSUIPC, to get the 3 'mode' positions back (they're reserved/hidden for Saitek software only):

Windows Saitek YOKE driver MODE 123

C:\Windows\System32\SaiD0BAC.pr0 <= mode123 <= (rename)/delete/(restart windows)

****

I am new to Saitek.

If using just Saitek software and flying single and twin engine ... do the MSFS "axes" all have to be reselected in MSFS each time you change aircraft?

I know in FSUIPC you can program "aircraft specific" profiles.

Also, Why is this (SaiD0BAC.pr0) deleted in your example here?

[oldJ3pilot]

Greetings von;

MSFS settings are unchanged from plane to plane. If you want to change anything for a particular plane you must go to "Settings" and do it. The advantage of FSUIPC is that you can have specific profiles BUT be sure to delete MSFS settings that you want FSUIPC to manage.

If you use the SAITEK software for programming you can develop profiles for different planes, conditions, etc. The software also makes the three modes function.

Regards

Neal H

[von]

Neal,

Thanks for the reply.

I am about to start fresh on setups on my new PC.

I will only be using one single engine prop, one twin prop, and two twin engine jets.

Thus the questions here for Saitec or FSUIPC (throttle/yoke) profiles.

My first thought would be to use FSUIPC only.

"MSFS settings are unchanged from plane to plane."

OK.

"If you want to change anything for a particular plane you must go to "Settings" and do it."

OK.

What assignment have you had to change for your aircraft?

And would this assignment have to be change again in MSFS before flying another aircraft?

"The advantage of FSUIPC is that you can have specific profiles BUT be sure to delete MSFS settings that you want FSUIPC to manage."

Could I have a couple of examples?

Here I assume you want to delete a MSFS key assignment you never use (like cowl flaps) and use that same key in your new aircraft to like turn on a fuel pump.

"If you use the Saitek software for programming you can develop profiles for different planes, conditions, etc."

OK.

Example:

If I use Saitek software and assign Z axes for throttle on Siatek TQ.

I must also now assign the throttle axes in MSFS to the Siatek TQ lever e.g. flying a single engine Cessna.

Correct?

And each time I use SiateK software profile with more engines I have to set up MSFS"s axes assignments before each flight.

Correct?

In other words, Saitec profiles will not automatically reconfigure MSFS axes when changing planes?

"The software also makes the three modes function."

OK. that is an advantage for using a lot of buttons.

[Tregarth]

Use either the Saitek 'Mode' with software, or redefine everythiong in FSUIPC ('disable' joystick control)

for FSUIPC, to get the 3 'mode' positions back (they're reserved/hidden for Saitek software only):

Windows Saitek YOKE driver MODE 123

C:\Windows\System32\SaiD0BAC.pr0 <= mode123 <= (rename)/delete/(restart windows)

Mtjoeng,

Thanks for your reply; unfortunately it is a bit too cryptic for me to understand.

Do you mean that you can make all 3 modes on a Saitek X52 Pro run in FSUIPC by using the file C:\.....<= ?

I have looked in my System 32 folder but cannot find the file you mention (SaiD0BAC.pr0), I recognise this as a Saitek file from the .pr0 extension. The nearest I can find to yours in my folder is SaiD0762.pr0

Can you please explain bit a bit more about what you have done to make the 3 modes work?

I appreciate your comments, it seems that others have found the same problems that I have, so we can all benfit from your knowledge.

Thanks,

Tregarth

[mtjoeng]

Mtjoeng,

Thanks for your reply; unfortunately it is a bit too cryptic for me to understand.

Do you mean that you can make all 3 modes on a Saitek X52 Pro run in FSUIPC by using the file C:\.....<= ?

I have looked in my System 32 folder but cannot find the file you mention (SaiD0BAC.pr0), I recognise this as a Saitek file from the .pr0 extension. The nearest I can find to yours in my folder is SaiD0762.pr0

Can you please explain bit a bit more about what you have done to make the 3 modes work?

I appreciate your comments, it seems that others have found the same problems that I have, so we can all benfit from your knowledge.

Thanks,

Tregarth

sorry i have misread the post

read Flight YOKE, iso Flight Joystick

anyway, should be the same Saitek method though

saitek let windows "hide" the 3mode button for their software

so the Saitek software has unique access to use for their '3modes' software

if - like me - you think their software isnt clever enough for FSX

.. you seem to be stuck with 3 hidden buttons @ driver level, so FSUIPC cannot see the 3mode switch

so with the YOKE its the SaiD0BAC.pr0 file that does that trick

found with google:

"Go into C/windows/System32 and look for a file called SaiD0762.pro

(it's with the rest of the saitek driver files) and remove it.

You can then programme buttons 16,19,32 and 39.

I've done this from my first X52 and my X52pro without any ill effect."

and it seems you can get 4 xtra buttons back for fsuipc

[Masterius]

For anyone using the Saitek/Logitech Pro Flight Yoke, the X52 HOTAS, or the X52 Pro HOTAS, you've most likely encountered difficulties with the Mode Switch when using anything other than the Saitek Smart Technology profile editor. Windows' Game Controller setting (joy.cpl) will show the Mode Switch as functioning, yet your game or third-party programming software (like LINDA or FSUIPC) will not recognize any input--programmed or native--from the Mode Switch. Everything else will work, just not the Mode Switch*.

There is a reason for that, and a solution as well.

The Mode Switch was intended to triple the amount of keybindings/controls that you could program. As an example, for the trigger switch, using the SST profile editor you might program Mode 1 for firing guns, Mode 2 for firing rockets, and Mode 3 for firing missiles.

Outside of the SST profile editor, however, the Mode Switch does not work, and this is because Saitek designed their programming driver so that Windows would hide the Mode Switch function in order that their software would have exclusive access. The programming driver is not the same as the Saitek Smart Technology profile editor program. When the yoke or joystick is first installed you do not have to install the SST profile editor, only the drivers. The Saitek Smart Technology profile editor is optional, and unnecessary. However, whether you choose to install SST or not, along with the necessary driver(s) is the programming driver as well.

One solution is to select the applicable Saitek/Logitech peripheral (Yoke or HOTAS) in the Game Controllers window. The easier way to do this is to enter in the search bar "Game Controller" then select "Set up USB Game Controllers". Scroll down and highlight the applicable controller--yoke or joystick--then click "Properties". As long as the Properties window is open and active the Mode Switch will now correctly function. Unfortunately, this requires remembering to do this each and every time you use your flight sim. However, there exists a more elegant--and permanent--solution.

For each of the three controllers, Saitek has an associated programming driver. They should be located in C:\Windows\System32, and are as follows:

• Pro Flight Yoke: SaiD0BAC.pr0

• X52 HOTAS: SaiD0255.pr0

• X52 Pro HOTAS: SaiD0762.pr0

Make a backup copy for safety and then rename the applicable file. For instance, I've renamed SaiD0BAC.pr0 as SaiD0BAC.pr0.bak.

That's it! Simply reboot your system and now you'll be able to use the Mode Switch outside of the SST profile editor software.

*For the X52/X52 Pro, the mouse controller and scroll wheel is also effected and should work using this fix.

[John Dowson]

We always recommend not using/installing the Saitek drivers (or any additional software) if using FSUIPC, as these invariable cause issues. Just let windows install the default drivers. I have the X55 (not the X52, but should be similar), and the mode switch on the throttle is recognised by FSUIPC as buttons 31, 132 and 133.

John