Hi. I need some help in setting up my axes. One of my main aircraft is Flight1's King Air B200, however the throttles on this aircraft are difficult to manage and I find that the engine number 1 spikes constantly when on the ground, which means that taxing is tricky. I assign and calibrate all of my axes through FSUIPC. I have heard that the Flight1 King Air doesn't like having the throttles processed through FSUIPC and that it is best of these are set in Prepar3d. I don't understand how to set up the throttle axes in Prepar3d while everything else is handled by FSUIPC. My Joystick Controllers are currently disabled in Prepar3d, so surely I would have to enable them so I can process the throttle? But this would enable all of the other axes which are currently handled by FSUIPC. I thought you had to choose between Prepar3d and FSUIPC and use one or the other. How then can I have a mixed set up so that Prepar3d processes just the throttles? I would appreciate any advice you can give. Thank you.

Adrian

You can assign the throttles in fsuipc to use the default P3D control calibration instead of the fsuipc calibration (this works the same as if you assigned them in the P3D settings menu). You would then use the calibration tool in the P3D settings to assign the range of axes.

I’ve had to do this on some aircraft that don’t work right with fsuipc calibration. Similarly for my speed brake axis as well.

You'll need to set up an aircraft-specific profile for the B200 and set up the axis as "Send to FS as normal axis" and select "Axis Throttle x Set" for each axis.  This should be functionally equivalent to assigning it in P3D's controls menu.

But...that said, I'd first check that you don't have another unintended assignment to the throttle axis somewhere...on a gamepad, or another input device.  Check the P3D controls menu for every listed device to see if there's an unwanted axis assignment to throttle1.  The behavior you describe is common when another "phantom" axis assignment exists...any time the phantom axis changes value, however slightly (e.g. a noisy pot), it'll spike the axis, as the inputs do not average, but rather use the last input seen.  P3D will auto-assign axes when it sees a new controller, and it's common to see funky assignments on rudder pedals, gamepads, etc.

 

2 hours ago, JasonPC said:

You can assign the throttles in fsuipc to use the default P3D control calibration instead of the fsuipc calibration (this works the same as if you assigned them in the P3D settings menu). You would then use the calibration tool in the P3D settings to assign the range of axes.

I am finding that these settings, going through FSUIPC as "Send to FS as normal axis" don't seem to work the same as default P3D.

I set up my Aerosoft A330 and FSL A320 using this type of setting and my PFC throttles move backward.  If I try to go into "Joystick Settings" and click on the reverse box, my throttles won't work at all because these aircraft don't seem to allow any processing by FSUIPC.

I've had to actually shut off all axes settings in P3D and just use the throttle setting.  Then enable joystick settings in P3D when flying that particular aircraft. I don't even have to select reverse in P3D.  My throttles work in the right direction as long as they are not going through FSUIPC.

I hate this because I always like setting my controllers through FSUIPC with Profiles for each aircraft, but it is the only way I can get some of these aircraft that were not considering users that strictly use FSUIPC for their axis.

These developers that say "Our aircraft doesn't need FSUIPC to work..."  ...well that's a bad thing, not a good thing.

 

Bob

Yeah I’ve had some issues with the buses. More so with aerosoft, don’t remember having a problem with the fslabs other than it has its own calibration settings in the menu that you have to set up for it to work properly. Each addon is totally different.

Another reason to get behind a new flight sim that would hopefully make something as simple as controls be streamlined to actually work consistently.

On 12/17/2019 at 12:17 PM, JasonPC said:

Yeah I’ve had some issues with the buses. More so with aerosoft, don’t remember having a problem with the fslabs other than it has its own calibration settings in the menu that you have to set up for it to work properly. Each addon is totally different.

Another reason to get behind a new flight sim that would hopefully make something as simple as controls be streamlined to actually work consistently.

I certainly hope that MSFS will provide profiles for hardware setup on each aircraft right out of the box. One of the things that I like about X-Plane 11 really.

1 hour ago, signmanbob said:

I certainly hope that MSFS will provide profiles for hardware setup on each aircraft right out of the box. One of the things that I like about X-Plane 11 really.

I hope it’s improved but one thing I heard is that the alpha is running a new version of sim connect and that certain programs already have compatibility through an update. So I guess it could only get better from there.

Edited January 2, 20206 yr by JasonPC

The flight 1 king air is one plane that don't work well setting axis in fsuicp setup in p3d or use any other software besides fsuicp for this plane I use spadnext.