Jump to content
The simFlight Network Forums

Strange problem using saitek x52 fs9


Recommended Posts

This just started recently after going from win xp to win 7 pro 64. I have the registered ver fsuipc 3 latest ver. button 2 is set to arm spoilers and button 6 toggles gear when pushed and toggle taxi light when released. Works well. I have button 19 to decrease flaps and 21 to increase flaps. I've used this for quite awhile, but now if on t/o and I have flaps at 5 and I push button 6 to raise the gear the flaps go to ten. The gear and taxi lights do their thing, but the flap do not. And it's the same when landing. If I'm at flaps 2 or 5 and I push button 2 the spoiler arm, but the flaps decrease to the previous setting. Then lowering gear they increase. I've gone into the saitek properties and recalibrate and everything is fine. I've looked in fsuipc and even made sure everything is correct, but still the problem. Any ideas? I hadn't happened before. This is using iFly 737ng. I'll have to take alook at my other addon planes.

Link to comment
Share on other sites

This just started recently after going from win xp to win 7 pro 64. I have the registered ver fsuipc 3 latest ver. button 2 is set to arm spoilers and button 6 toggles gear when pushed and toggle taxi light when released. Works well. I have button 19 to decrease flaps and 21 to increase flaps. I've used this for quite awhile, but now if on t/o and I have flaps at 5 and I push button 6 to raise the gear the flaps go to ten. The gear and taxi lights do their thing, but the flap do not. And it's the same when landing. If I'm at flaps 2 or 5 and I push button 2 the spoiler arm, but the flaps decrease to the previous setting. Then lowering gear they increase. I've gone into the saitek properties and recalibrate and everything is fine. I've looked in fsuipc and even made sure everything is correct, but still the problem. Any ideas? I hadn't happened before. This is using iFly 737ng. I'll have to take alook at my other addon planes.

Sounds like you either have multiple assignments, maybe in FSUIPC and FS, or your device is playing up and sending spurious button presses. Try using FSUIPC button and event logging to see what is going on.

Pete

Link to comment
Share on other sites

fsu.zipI did a log on app with my level d. I haven't really figured out how to read the log, but I did this just on final appro and it says it's 55mb big. but I did attach the ini file. I been flying with these addons for a long time. But in Feb. I moved up to win 7 pro 64 from win xp 32 sp3.
Link to comment
Share on other sites

I haven't really figured out how to read the log, but I did this just on final appro and it says it's 55mb big.

Er, it won't be 55 mb if you only enabled the items I said -- buttons and Events (not Axis events), and just pressed the buttons which are going wrong, then switching the logging options off again! The logging was only supposed to be used to see what your buttons were doing and showing where the assignments were!

Please just paste the contents of INIs and LOGs rather than uploading them.

Just at a cursory glance at your INI:

0=Saitek X52 Flight Controller

0.GUID={06993A70-7DA4-11E2-8004-444553540000}

1=Saitek Pro Flight Rudder Pedals

1.GUID={06993A70-7DA4-11E2-8005-444553540000}

O=<< MISSING JOYSTICK >>

[buttons]

Buttonrepeat=20,10

3=P0,10,C66298,0

5=P0,5,C66066,0

7=P0,12,K85,9

8=P0,2,C65607,0

9=P0,3,C65615,0

11=R0,16,C66526,0

12=R0,18,C66527,0

13=R0,17,C66529,0

14=R0,15,C66528,0

15=P0,14,C65875,0

[buttons.ifly]

0=P0,1,CM4:1,0 //macro

1=P0,13,K68,9

2=P0,6,K222,8

3=P0,9,K87,8

It appears that buttons 19 and 21 (mentioned in your message) are not programmed in FSUIPC at all. Only 1, 2,3,4,6, 9, 10,12,13,14,15,16,17,18. I suspect you have buttons also programmed in FS itself hence the multiple assignments I mentioned.

Additionally you have button 2 assigned to "elev trim dn", not spoiler arm -- that's button 5.

Button 6 appears to be assign to keypress 222 for the iFly -- that's the #~ key. I'm afraid I don't know wehat that does, but it seems unlikely be be 'gear up' as you say.

Also, the X52 seems to have been disconnected at the time you got this INI, judging by the 'MISSING JOYSTICK' message.

Pete

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.