Jump to content
The simFlight Network Forums

FSX FSUIPC Saitek Rudder Pedals Breaks


Recommended Posts

Hello,

I am new in this forum, perhaps somebody can help me-

I am using FSX on an Vista 32 PC. I bought the SAITEK Yoke, a separat throttle quadrant and the SAITEK rudder-pedal. As advised in diffrent postings I disabled all the joystick commands in FSX, dont use the SAITEK software and programmed everything through FSUIPC (latest version, registered user).

No everything works fine, except the breaks. As I understood the the rudder pedals are programmed as axis. One axis for the ailerons (works fine) and a second acis for the breaks, tipping the left an right pedals.

What happend now is: the plane won´t move because the breaks are on. When I tip both pedals all teh way down, the breaks are released and the plane moves. The breaks, of course should operate vice-verse. I have no idea how to fix it.

Has anyone got an idea?

Greetings

Wolfgang

Link to comment
Share on other sites

No everything works fine, except the breaks. As I understood the the rudder pedals are programmed as axis. One axis for the ailerons (works fine) and a second acis for the breaks, tipping the left an right pedals.

What happend now is: the plane won´t move because the breaks are on. When I tip both pedals all teh way down, the breaks are released and the plane moves. The breaks, of course should operate vice-verse. I have no idea how to fix it.

You need to select the REV checkbox for the Brake axis in FSUIPC.

Link to comment
Share on other sites

Thomas,

I see, that not diffrential breaks, but breaks are indicatedin nthe lower left of the screen, when I start on the runway, but I have now idea what you are speaking of - deltazone etc.

What I am now working on, is to activate the mode switch on the Saitek Yoke, to get a triple amount of commands. There are several postings in this forum teaching you what to do, that FSUIPC recognizes the mode switch as a switch and there is an fsuioc.ini file as an example as well. I tried it out, but what I found was, that changing the mode switch itself generated obscure result, it changed the etc. Have you got an idea what the reasin can. be?

As I saw, you have nearly the same hardware as I have, sou couldn´t you post your FSUIPC.ini file?

As you seem to live in Dormund we could use German, but may be ist better for the rest of the guys around to continue with english.

Greetings,

Wolfgang

Link to comment
Share on other sites

deltazone

mode switch

Hi, I am the one metioning Delta Zone, read the manual, and its on 'Axis Assignement' in the middle "Delta" button, the box underneath is the value, and its default is 256, but press 1once, move your diff.brake LITTLE bit (like 'byond accidental') and press again. My value is 5500+ to make sure its not braking at 0.

mode switch is a Whole Different Story

making More Possibilities Like Original Mode Button (for in FSUIPC you Disable the driver) is called Compound

for instance my buttons will do W shiftW in PanelMode BUT PanLeft and PanRight in VC and SpotMode

=P0,8,C66654,0 ;mode1 VC VIEW_VIRTUAL_COCKPIT_FORWARD 66654

=P0,9,C66653,0 ;mode2 VIEW_COCKPIT_FORWARD 66653

=P0,10,K122,8 ;mode3 122=F11 < K="keyboard" and value in "FSUIPC4 for Advanced Users.pdf"

above:

"0," is my Saitek, being Joystick 0

8,9,10 are mode 1 2 3 buttons and defined here as VC Panel SpotView

x=CP(+0,9)0,7,K87,9 ;if panel SHFT-W

x=CP(+0,9)0,6,K87,8 ;if panel W

x=CR(+0,8)0,7,C65672,0 ;if VC PanRight

x=CR(+0,8)0,6,C65671,0 ;if VC PanLeft

x=CR(+0,10)0,7,C65672,0 ; if F11 PanRight

x=CR(+0,10)0,6,C65671,0 ;if F11 PanLeft

I have per plane 65+ definitions like the above

like the toggles on the Throttle Quad, will show/hide Panels in PanelView But are Different Per Plane

Its easy when you know and Very Confusing when you start, so I wont show you my .ini, because I know you have to comprehend Above Examples first by reading the manual, or you'll only get more confused.

ADVANCED: I just started FLAG conditions, see if you can figure out this one:

x=H0,0,C1003,3855 ;3855=15,15 - Button Flag Set (C1003), Button Flag Clear (C1004),

x=U0,0,C1004,3855

above button 0,0 is Saitek button 1

when Pressed (H) it sets a flag "3855" (Virtual Button 15,15)

when Released (U) it releases the flag

THEN

in my Cheyenne plane with Multiple Main Panels (minpanel, landing view, regular, copilot)

I defined this:

;Approach Panel = panel +W

101=CP(F-15,15)(+0,9)0,6,C65906,0

102=CP(F-15,15)(+0,9)0,6,K87,8

;MINI panel Panel_1 + shftWx2

115=CP(F+15,15)(+0,9)0,6,C65906,0 ;panel1

116=CP(F+15,15)(+0,9)0,6,K87,9

117=CP(F+15,15)(+0,9)0,6,K87,9

;NORMAL 65906 PANEL_1

110=CP(F-15,15)(+0,9)0,7,C65906,0

:COPILOT panel + 3x shftW

120=CP(F+15,15)(+0,9)0,7,C65906,0

121=CP(F+15,15)(+0,9)0,7,K87,9

122=CP(F+15,15)(+0,9)0,7,K87,9

123=CP(F+15,15)(+0,9)0,7,K87,9

cheers mt

Link to comment
Share on other sites

by the way a tip:

you can change FSuipc within FSX and then 'reload buttons' or 'reload axis'

in this way, you edit definition in an editor, Reload within FSX, test, Not Working?, find error, change, reload, test ..

etc.

FSuipc.ini is periodically saved by fsuipc iteself

that is not what you want when editing, for it will save 'itself'

so when you editor says 'file changed externally want to reload?' you must say 'no'

Link to comment
Share on other sites

Hi mtjoeng,

After your last posting I had two busy evenings, but then I succeeded in programming some buttons in compound mode. Here is the result:

[buttons]

; PAN - ALL Modes

1=R0,32,C65734,0 ; PAN_UP

2=R0,33,C65856,0 ; PAN_RIGHT_UP

3=R0,34,C65672,0 ; PAN_RIGHT

4=R0,35,C65857,0 ; PAN_RIGHT_DOWN

5=R0,36,C65735,0 ; PAN_DOWN

6=R0,37,C65855,0 ; PAN_LEFT_DOWN

7=R0,38,C65671,0 ; PAN_LEFT

8=R0,39,C65854,0 ; PAN_LEFT_UP

; SWITCH MODE 1- VIEW Mode

9=CR(+0,8)0,2,C65655,0 ; zoom in

10=CR(+0,8)0,3,C65656,0 ; zoom out

11=CR(+0,8)0,0,K8,8 ; view reset

12=CU(+0,8)0,0,K32,10 ; zoom reset

13=CP(+0,8)0,1,K83,8 ; View next categorie

14=CP(+0,8)0,7,K121,8 ; 2-D panel

15=CP(+0,8)0,6,K120,8 ; 3-D panel

16=CP(+0,8)0,4,K65,8 ; Next View in Categorie

17=CP(+0,8)0,5,K87,8 ; 2-D Cockpit (cycly panels)

18=CR(+0,8)0,14,C66528,0 ; Eyepoint forward

19=CR(+0,8)0,15,C66529,0 ; Eyepoint back

20=CR(+0,8)0,16,C66524,0 ; Eyepoints UP

21=CR(+0,8)0,17,C66525,0 ; Eyepoint down

22=CR(+0,8)0,18,C66527,0 ; Eyepoint left

23=CR(+0,8)0,19,C66526,0 ; Eyepoint right

24=CP(+0,8)1,5,K80,8 ; Pause

25=CP(+0,8)1,2,K121,9 ; Sound on/off

26=CP(+0,8)1,3,K90,9 ; Framerate Cycle

27=CP(+0,8)1,4,K81,8 ; Kneeboard

28=CP(+0,8)1,1,K44,8 ; PrintScreen - snapper

; SWITCH MODE 2- CONTROL Mode

29=CP(+0,9)0,0,C65564,0 ;ATC

30=CP(+0,9)0,1,C65580,0 ; Autopilot Master

31=CP(+0,9)0,2,C66079,0 ; Gear UP

32=CP(+0,9)0,3,C66080,0 ; Gear Down

33=CP(+0,9)0,4,K117,8 ; Flaps increase

34=CP(+0,9)0,5,K118,8 ; Flaps decrease

[Axes]

0=0X,256,D,1,0,0,0

1=0Y,256,D,2,0,0,0

2=0Z,256,D,9,0,0,0

3=0U,256,D,10,0,0,0

4=0V,256,D,17,0,0,0

5=1X,256,D,18,0,0,0

6=1Y,256,D,13,0,0,0

7=1Z,256,D,14,0,0,0

8=2X,256,D,7,0,0,0

9=2Y,256,D,8,0,0,0

10=2R,256,D,3,0,0,0

But now everything seems to have been in vain, because FSUIPC doens´t recognize the mode switch of the SAITEK yoke any more. I have no idea what the reason could be. In the windows joystick control panel the mode switch is recognized but not in FSUIPC. When I open "buttons and switches" in FSUIPC and I move the mode switch, nothing happens any more. What could be the reason.? All I changed is, that I installed VISTA Service Pack 1. Can it be due to this operation?

Regards,

Wolfgang

Link to comment
Share on other sites

Hello everybody,

I wa stoo early with my question and found the solution. Indeed it was the VISTA service-pack!

To make the mode switch working in FSUIPC it is necessaray to rename the file SaiDOBAC.pro as I learned from a psotin in this forum:

"With the driver installed for the clock (without the software), all you have to do is rename the file C:\Windows\System32\SaiD0BAC.pr0 and unplug/plug in the yoke. I've been using this method since I bought my yoke and it works great."( (jordanal on dec 27th)

Now what happened ist that the VISTA Service Pack somhow wrote again a SaiDOBAC.pro in the System 32 directory. Just renamed it again and verything worked.

Greeetings,

Wolfgang

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.