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