nantelp Posted November 30, 2019 Author Report Posted November 30, 2019 Ok the value for: T1 in -14320 to 15867 T2 in -16384 to 16125 Yes the aerosoft Airbus is the only plane where I have this problem. All the other Add-ons plane are working fine and have both throttle at 0 THR. Pierre
Pete Dowson Posted November 30, 2019 Report Posted November 30, 2019 3 hours ago, nantelp said: T1 in -14320 to 15867 Hmm, close but not close enough.perhaps, but then: 3 hours ago, nantelp said: Yes the aerosoft Airbus is the only plane where I have this problem. All the other Add-ons plane are working fine and have both throttle at 0 THR So how come the others don't also stay off Idle, being fed exactly the same values? Incidentally, didn't you say yo'd setup a user-defined quadrant setting? I don't see that in your INI. The only aircraft assignment you made is: [AircraftQuadrants] Aerosoft_A318_professional_AIR_FRANCE_F-GUGA=J2 so: J2-0=5,30,1,20,35,35,108,108 J2-2=5,5,4,20,56,72,108,126 J2-3=5,6,0,20,56,72,108,126 J2-5=5,32,20,20,56,72,108,123 Now, what I find very strange is that ALL of the Minimums are set to 20 and all the maximums at 108. Now pots are NEVER precisely identical, so i think these are default uncalibrated values. I think you need to calibrate them all properly in PFC. Then FSUIPC will get better values too. Looking back at your pictures, the ones for PFC show Throttle 2, set to its minimum position, gives an input of 8 whilst you have 20 as being the "idle" setting. So anything below 20 will be idle. Good and safe. BUT throttle 1, also at its lowest, shows an input of 0 and a minimum for idle set as 0. Now allowance at all for any variation -- 12 whole units allowed of leeway for Thr2, none at all for Thr1. Please, you MUST calibrate. Always allow those null zones I said, at both minimum and maximum settings. Pete
Pete Dowson Posted December 1, 2019 Report Posted December 1, 2019 I've neen checking exactly what the PFCcom64 driver does, and unfortunately no amount of calibration in the PFC driver will affect the values seen in FSUIPC's axis assignments. The reason is that the values fed to FSUIPC are deliberately designed to allow the more powerful FSUIPC calibrations to be used.so they aren't pre-calibrated. There's only one way I can think of, short of writing a Lua plug-in to do the calibration or having me develop new facilities in PFCcom64, and that is as follows. Use the simple arithmetic adjustments available in FSUIPC assignments to adjust the range you get slightly. This is by INI file editing only. In this line in your FSUIPC5.INI file: 0=17Z,512,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }- Now you say your current range is -14320 to 15867 and we ideally want -16383 to +16383. So a range of 32766 compared to 30187. 32766/30187 = 1.0854. So we multiple the value by that, which gives a range of -15543 to 17222. So we need to sutract 840, giving us a final range of -16383 to 16382, which will do nicely. In the INI this looks like 0=17Z,512,F,66420,0,0,0,*1.0854,-840 This scaling facility is described in your FSUIPC5 for Advanced Users, on page 42:Additional parameters to scale input axis values Hope this helps at last! Pete
nantelp Posted December 1, 2019 Author Report Posted December 1, 2019 Hi Pete, I re- did the test with the default airplane and I realized that the throttles have the same problem see picture The In value are T1 -14320 to 15351 T2 -16384 to 15867 (I see that the T2 sits at 0 THR because of the -16384, correct?) Quote So how come the others don't also stay off Idle, being fed exactly the same values? So yes they all have the same uneven Throttles, but if I use the Joystick calibration and I calibrate them with no reverse zone then the problem goes away, and the throttles are even at 0 THR. I did the test with the Electra and the PMDG 777. But for the Airbus I cannot use the Joystick Calibration, if I do the Throttles stop working in the SIM. Quote Incidentally, didn't you say yo'd setup a user-defined quadrant setting? I don't see that in your INI. The only aircraft assignment you made is: Like I said I did the test with a fresh install of FSUIPC and PFCcom64 so I use the Jet 2 quadrant and I didn't use any profiles. I only had the Aerosoft_A318_professional_AIR_FRANCE_F-GUGA=J2 defined. Quote Please, you MUST calibrate. Always allow those null zones I said, at both minimum and maximum settings. So just to make sure, I don't have to do that. In PFCc0m64 I just need to assign the quadrant to the aircraft. Quote In the INI this looks like 0=17Z,512,F,66420,0,0,0,*1.0854,-840 see picture, that fixed it they are now equal and at 0 THR So you did solve my problem, I do not know how to thank you. On more question: When I create profile in FSUIPC, when I am ask "do you want to apply the general assignment to this Aircraft? yes or no. What should I answer? Is the explained somewhere in the documents? Again many thanks Pierre
Pete Dowson Posted December 1, 2019 Report Posted December 1, 2019 40 minutes ago, nantelp said: When I create profile in FSUIPC, when I am ask "do you want to apply the general assignment to this Aircraft? yes or no. What should I answer? It means exactly what it says. You may not have any, but normally most folks have some assignments which are common to ALL the aircraft, or perhaps MOSt of the aircraft they fly. So, you replay "Yes" if you want all those non-Profile assignments to apply in this new profile, only being replaced by any specific ones you make for it. Replay "No" if you are starting afresh, completely differently, for this profile. Pete
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