Saitek new X55

[Bryan Fisher]

Hi Peter

 

I am a long-term user of FSUIPC to assign controls with my CH Quadrant and Fighterstick, but am on the brink of buying the new Saitek X55 kit.

 

I asked "Mad Catz" if I would be able to assign controls with the X55, using FSUIPC. The answer was true to form - they didn't know, and suggested that I contact you.

 

This kit is getting good reviews and sounds very useful................but I wouldn't like to lose my FSUIPC control.

 

Can you help?

 

Regards

 

Bryan Fisher (Pontius)

[Pete Dowson]

I asked "Mad Catz" if I would be able to assign controls with the X55, using FSUIPC. The answer was true to form - they didn't know, and suggested that I contact you.

Can you help?

 

Sorry, I've no idea what it is.  If it is a joystick type device recognised by Windows as such, and assignable in FS, then it is also assignable in FSUIPC. FSUIPC doesn't distinguish between makes or types of  joystick, it simple handles up to 8 standard axes, up to 2 POVs and up to 32 buttons. After that you are dependent on drivers or programming Lua plug-ins.

 

Pete

[Ian P]

The X-55 is MadCatz/Saitek's new HOTAS system, Pete. Joystick, twin throttles, lots of buttons and switches.

 

I don't have one (it would be useless to me and my stupidly small hands) but going from previous experience with Saitek, it should be assignable as normal.

 

Ian P.

[Pete Dowson]

The X-55 is MadCatz/Saitek's new HOTAS system, Pete. Joystick, twin throttles, lots of buttons and switches.

 

I don't have one (it would be useless to me and my stupidly small hands) but going from previous experience with Saitek, it should be assignable as normal.

 

Thanks Ian.

 

Pete

[Doc104]

Hi Peter,

 

I just connected my new X55 HOTAS, and have found that the X55 driver causes a conflict with my registered FSUIPC (both 4.8 and 4.9).  Specifically, it causes the joystick to send out a continuous and uninterruptible stream of "space" characters for as long as FSX is running, or until the joystick is disconnected. 

 

Interestingly, when I use an unregistered FSUIPC, this does not happen, But then I'm forced to use the MadCatz programming software, which causes ghost commands in FSX.

 

MadCatz recommends I stop using FSUIPC and use SimConnect instead.  That's not a great answer, as I rather like my registered FSUIPC.

 

I'd appreciate any advice you have on this.

 

Thanks,

Doc104

[Gypsy Baron]

I don't have the X55 however I do have the old X-45 as well as the Saitek Pro yoke and dual throttles.

 

I use the Saitek software for setting up much of the X-45 hats, buttons, switches and use the

stick for my flight controls.

 

For the Pro yoke/throttle stuff I do NOT load the Saitek software but instead program

everything via FSUIPC4.

 

You might try disabling/removing the X55 software and then try setting up everything

via FSUIPC4.

 

You might want to investigate the source  of the continous space characters if they

still exist after disabling the X55 software.

 

With my X-45, even though I use the software and load a profile, the buttons/switches

that I do not create assignments for in the profile get passed directly through and

FSUIPC4 'sees them' and I can make assignments there.

 

  Paul

[Doc104]

Paul,

 

I agree with what you said.  Only the kicker is that it's the X55 driver, not the programming software, that causes the "space" characters malfunction and conflict with FSUIPC.  I had only the driver loaded when I first encountered the problem.  Loading the programming software, testing the system, and then deleting the software, and testing again, all showed the same symptom of continuous "space" characters.

 

I was attempting to set up everything on the X55 with FSUIPC just as you describe, but the conflict prevents FSX from operating normally.

 

I didn't have this issue with either the X45, the X52 pro, or the yoke.  This is something new with the X55 driver.

 

So the irony is, it works fine with unregistered FSUIPC - which means I can't program the keys that way.  With registered FSUIPC, I can program the keys, but I get the malfunction.

 

Thanks,

Doc104

[Pete Dowson]

So the irony is, it works fine with unregistered FSUIPC - which means I can't program the keys that way.  With registered FSUIPC, I can program the keys, but I get the malfunction.

 

An unregistered FSUIPC is not reading the joystick buttons nor axes, but a registered one, whilst reading them IF assigned, will not do anything with buttons if not pressed, and will not produce keyboard characters unless programmed to.

 

So it sounds like you have something assigned badly in your FSUIPC INI file!

 

Pete

[Doc104]

Pete,

 

I cleared all the button assignments in the .INI file, and that took care of the problem.  Thanks for the insight!

 

Doc104