marvix Posted September 27, 2018 Report Share Posted September 27, 2018 I am trying to configure the Airbus Pro with my custom throttle set and it seems to be a pulling teeth event. I have custom throttles and they work with P3Dv4 control set-up, I would like to use FSUIPC to line up the detent for CL mode, the other detents do line up. Is there a specific procedure for getting the throttles to work, I had them working with P3Dv3 and the previous Aerosoft airbus. (FYI, the custom throttle set is set up as logitec wingman USB) I see the axis movement and can calibrate in FSUIPC, nothing happens in the Airbus Pro. Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 28, 2018 Report Share Posted September 28, 2018 8 hours ago, marvix said: . Is there a specific procedure for getting the throttles to work, I had them working with P3Dv3 and the previous Aerosoft airbus. (FYI, the custom throttle set is set up as logitec wingman USB) I see the axis movement and can calibrate in FSUIPC, nothing happens in the Airbus Pro. Some of the more sophisticated add-on aircraft read throttles differently, bypassing the usual FltSim methods. PMDG Boeings are examples -- though they respond to calibrated inputs they also read more directly so bypassing that. The result is that they can get two different inputs and so act jerkily. The advanced versions of the Airbus system do something special with throttles too, I assume emulating the thrust modes rather than using the throttle input directly. I suspect that if you use FSUIPC for assignment you must assign to the standard FS controls - "Axis throttleN set". Try that first WITHOUT calibrating (press the RESET button in the calibration section if you've already set calibration). If that works, only then try Calibrating. You will probably have to set the "NRZ" (no reverse zone) option. If that still doesn't work, there's one other trick: add (or change to Yes) "UseAxisControlsForNRZ=Yes" into the relevant [JoystickCalibration] section of the FSUIPC5.INI file. That's the last hope for normal calibration. If that doesn't work I can only think that it must be done by writing a Lua plug-in to process the axis. Pete Link to comment Share on other sites More sharing options...
marvix Posted September 28, 2018 Author Report Share Posted September 28, 2018 Thanks Pete, I'll let you know and report back. Link to comment Share on other sites More sharing options...
marvix Posted September 29, 2018 Author Report Share Posted September 29, 2018 Thanks Pete, your suggestions did work. The trick of changing the no reverse zone did help. Now FSUIPC in back in charge of Airbus. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now