Jump to content
The simFlight Network Forums

Wico Airbus Volume 2 Saitek TQ problems


Thralni
 Share

Recommended Posts

Hello Pete and others,

I know, again a thread about the Wilco Airbus and getting the Saitek TQ to work with it. But yeah, I have a problem that won't go away: the throttle is responsive, but it doesn't do at all what it is being told. Here are things I did:

- To test if it works at all, I assigned engine 1 and 2 to the Saitek throttle levers within FSX. That worked: the Wilco throttle levers were responsive and worked correctly.

- I went back into FSUIPC and assigned the throttle axes of the Saitek yoke using the "send to FS as normal axis" option.

- In the joystick calibration window, I made sure that "no reverse zone" was ticked.

- In the FSUIPC4.ini file, I made sure that the joystick calibration section of this particular profile (called wilco A330) has the "UseAxisControlsForNRZ=Yes" parameter.

After all this, it still doesn't work. What I get is this: When I move my Saitek throttle levers, the throttle levers in the Wilco do not move. Instead, the thrust ramps up for a bit, accompanied by a thrust reverser sound, but it quickly cuts out and returns to idle. So, there is a response, but it's completely wrong.

This is the relevant part of the FSUIPC4.ini file:

[Profile.Wilco A330]

1=Feelthere A330-200 GE Airbus Air Greenland

[buttons.Wilco A330]

0=R2,21,C65966,0

1=U2,21,C65967,0

2=R2,22,C65971,0

3=U2,22,C65972,0

[Axes.Wilco A330]

0=0X,256,F,65763,0,0,0

1=0Y,256,F,65694,0,0,0

2=1Z,256,F,23,0,0,0

3=2Z,256,D,22,0,0,0

4=2U,256,F,65820,0,0,0

5=2V,256,F,65821,0,0,0

[JoystickCalibration.Wilco A330]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=Yes

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-16384,0,1933,16254

Elevator=-16384,-512,512,16320

Throttle1=-16384,-512,512,16383/32

Throttle2=-16384,-512,512,16383/32

Throttle3=-16258,-512,512,16383/32

Throttle4=-16384,-512,512,16383/32

Spoilers=-16384,16383/16

Flaps=-16384,16383

For your information:

- I use FSX + Acceleration

- This is FSUIPC 4.703

- The product is Wilco Airbus Volume 2, patched to the latest version, but this is NOT the evolution version that was released some time ago.

- All other addon planes I have work great.

- Most of the assignments are from within FSUIPC, because of the various needs of my addon aircraft (Airbus using control sticks, others using yokes etc etc)

I hope somebody can help. For as far as I can see I have done everything that I had to do (use "send to FS as normal axis", tick the "no reverser zone" box and put in the "UseAxisControlsForNRZ=Yes". Maybe I missed something, in which cause any one of you can highlight it for me.

Link to comment
Share on other sites

I know, again a thread about the Wilco Airbus and getting the Saitek TQ to work with it. But yeah, I have a problem that won't go away: the throttle is responsive, but it doesn't do at all what it is being told. Here are things I did:

- To test if it works at all, I assigned engine 1 and 2 to the Saitek throttle levers within FSX. That worked: the Wilco throttle levers were responsive and worked correctly.

So why not use them that way?

- I went back into FSUIPC and assigned the throttle axes of the Saitek yoke using the "send to FS as normal axis" option.

But looking at your assignments you used "THROTTLE1_SET" and "THROTTLE2_SET", not the normal AXIS_THROTTLE1_SET and AXIS_THROTTLE2_SET controls. Why? Those old FS98 controls are the ones FSUIPC normally uses to get reverse thrust on the same axes, and are, by default, excluded in the 4 throttles page as you will see by the checkbox at the bottom.

- In the joystick calibration window, I made sure that "no reverse zone" was ticked.

And did you manage to actually calibrate them? It seems unlikely.

- In the FSUIPC4.ini file, I made sure that the joystick calibration section of this particular profile (called wilco A330) has the "UseAxisControlsForNRZ=Yes" parameter.
[

Yes, that's good but wasted when you assign to wrong controls. Please assign to the AXIS controls in the first place. All the "UseAxisControlsForNRZ=Yes" does is avoid changing them into the THROTTLEn_SET controls which you chose instead.

Also, I see from your calibration values that you've not actually bothered to calibrate any of your axes properly at all. Apart from Aileron and Elevator (which are only partially calibrated in any case), all the others are still completely set with default values. If you aren't going to calibrate in FSUIPC it's a bit of a waste of time using it for your controls, really.

Aileron=-16384,0,1933,16254

Elevator=-16384,-512,512,16320

Throttle1=-16384,-512,512,16383/32

Throttle2=-16384,-512,512,16383/32

Throttle3=-16258,-512,512,16383/32

Throttle4=-16384,-512,512,16383/32

Spoilers=-16384,16383/16

Flaps=-16384,16383

Regards

Pete

Link to comment
Share on other sites

Ah, see? That's why I posted, because I didn't even see that there were multiple options for setting the throttle axis. I thought that Throttle1_set and Throttle2_set were the only ones... Probably overlooked the other ones. As such, I didn't calibrate them, because I couldn't. If I could, I would have certainly bothered to calibrate them, but In the calibration window none of the values changed when moving the throttles. I'll try setting the throttles using the AXIS_Throttle1/2_set assignments and see what happens.

As for why not using the FSX default assignments instead, isn't that obvious? It would defeat the entire purpose of using FSUIPC... The point is that every aircraft is different and using FSUIPC's profiles I do not have to go into the FSX controls window to change it for every other airplane I fly.

UPDATE: Edited the assignments using the Axis_throttle1/2_set, and it work brilliantly now. Thanks!

Link to comment
Share on other sites

As for why not using the FSX default assignments instead, isn't that obvious? It would defeat the entire purpose of using FSUIPC... The point is that every aircraft is different and using FSUIPC's profiles I do not have to go into the FSX controls window to change it for every other airplane I fly.

Hmm. It was really the calibrations I was referring to. You can assign to FS axes without calibrating, just as you can calibrate axes without assigning. You appear to have gone through the calibration pages for your various FSUIPC assignments pressing the left hand "SET" button to tell FSUIPC to calibrate them, but then not actually done so.

If you only want to use the assignments and leave your default windows driver-set calibrations to themselves you might as well go through pressing the left "RESET" buttons on each axis assigned to FS controls and just leave FS to it. This will work with all of the controls named "Axis ...." because those are the ones FS assignments would make. All you'd be using FSUIPC for is the switching for different aircraft.

For axes assigned "direct to FSUIPC calibration" you do actually need to SET calibration, but you don't for the regular FS controls.

Regards

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.