Switching On and Off joystick clibration and other settings

[roystondh]

I have been using FSUIPC for some while to assist with joystick and button assignment with considerable success.

However I am also using the Wilco Airbus Airbus Vol 1 series which calls for FSUIPC to effectively be turned off.

Does a simple method exist where I can effectively "dual boot" FS9, in one case with FSUIPC enabled and the other with it "turned" off ?

I've tried a quick search, drawn a blank - I am sorry if this has been covered before.

Thanks in advance

RH

[Pete Dowson]

I am also using the Wilco Airbus Airbus Vol 1 series which calls for FSUIPC to effectively be turned off.

If FSUIPC is not configured to do anything, it is "turned off". Who exactly is "calling2 for this, and in what exact terms? I've never heard of anything like that before. For example, if you use FSUIPC for weather options, or to program some buttons, how is that possible impinging on ther aircraft?

Does a simple method exist where I can effectively "dual boot" FS9, in one case with FSUIPC enabled and the other with it "turned" off ?

No, but all of your axis assignments, joystick calibrations and even buttons and switches can be made aircraft-specific. Though I fail to understand what could possibly be required here.

What are they REALLY talking about? No one else has ever mentioned anything. What exact problems have you got? Without specifics there's no way to help you.

Regards

Pete

[roystondh]

Thanks very much Pete for the prompt reply, I’ve always regarded your modules as one of the most useful add-ons for the FS.

I’d rather have FSUIPC engaged 100% of the time, I find the joystick axis calibration invaluable to give effective control of the flying surfaces along with using FSWide to connect to a secondary PC usually running FS Commander to log my flights.

The reason that I understand that FSUIPC should be “turned off” is twofold, firstly this comment in the support sections of the Wilco website

http://www.wilcopub.com/index.cfm?fuseart_airbus1

The aircraft is out of trim when the autopilot is disconnected !

This problem comes from FSUIPC. If you have a registered copy of FSUIPC, go to the miscellanous tab and DEACTIVATE the two items : VS sign and Disco AP elevator trim. Uncheck the boxes as shown here:

And this comment from the AVSIM review

The final thing you need to do is to set up the sensitivity and null point on your yoke or joystick and, if you have it calibrated through FSUIPC, alter FSUIPC so that it no longer controls the throttle for this particular plane. That's because the throttle is the Airbus unique combination of variable-thrust in the lower range of its travel and separate detentes for flight, reduced take-off and full-power take-off in the upper range. The plane uses special programming for this which FSUIPC would otherwise interfere with.

I shall do some further investigation along the lines of the aircraft specific setting you mentioned, however I am finding the Wilco Airbus has some residual bugs that at this rate I shall be switching to the Airliner XP airbus when it comes out.

One thought that I have is to create two config files and then have a batch program switch between them so I have a normal "mode" and a "wilco airbus mode" for my FSUIPC configuration.

Once again thanks and I shall get back to you.

RH

[Pete Dowson]

If you have a registered copy of FSUIPC, go to the miscellanous tab and DEACTIVATE the two items : VS sign and Disco AP elevator trim. Uncheck the boxes as shown here:

Okay, that's understandable. Those two options are defaulted OFF in any case. The first was only provided to deal with some odd FS behaviour which doesn't usually apply to good add-on aircraft, and the latter is only ever needed if you have an elevator trim joystick axis configured which interferes through jittering. Not many folks use analogue trimming.

The final thing you need to do is to set up the sensitivity and null point on your yoke or joystick and, if you have it calibrated through FSUIPC, alter FSUIPC so that it no longer controls the throttle for this particular plane. That's because the throttle is the Airbus unique combination of variable-thrust in the lower range of its travel and separate detentes for flight, reduced take-off and full-power take-off in the upper range. The plane uses special programming for this which FSUIPC would otherwise interfere with.

FSUIPC will only send throttle settings through to FS when they change. The way to deal with this without having to lose the ability to use the lower range would be to always park it someplace with no jitter when it isn't being used. alternatively, if the airbus you are using can accept keyboard or other controls to select the correct speed "gates" you could use the right-hand side of the axis assignments page to actually send those when the axis passes through the correct areas.

There are all sorts of ways of doing all this of course.

One thought that I have is to create two config files and then have a batch program switch between them so I have a normal "mode" and a "wilco airbus mode" for my FSUIPC configuration.

You shouldn't need to do that at all because the aircraft-specific options will swap axis assignments, calibration settings, and so on over for you automatically when you load the Airbus.

Regards

Pete