Jump to content
The simFlight Network Forums

nantelp

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nantelp

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Canada
  1. Ok so I should be find now, Many Thanks and Merry Christmas Pierre
  2. Thank you both for the info, I still found it strange that, even if I delete these lines: [Axes] PollInterval=10 RangeRepeatRate=10 in the FSUIPC5.INI and that I copy them in the CRJ pro profile file. When I restart P3D they are re-insert in the FSUIPC5.ini again. Also is it possible that the CRJ is the only plane that requires the PollInterval=10 & RudderBlendLowest=1 , I never saw those parameters added for the other planes I have. I am trying to keep my INI clean, by having a generic FSUIPC5.ini and a separate profile per airplanes. So for all my planes have the Joystick, axis and Buttons defined in the profile files and not in the FSUIPC5.ini. Pierre
  3. Good day, With a fresh installed of FSUIPC5, I was able to solve my issue, but I do have some questions. When I configure the CRJ aircraft , FSUIPC5 is adding the following line in the INI file. [Profile.CRJ pro] 1=CRJ1000 Pro Garuda Indonesia PK-GRO [JoystickCalibration] RudderBlendLowest=1 [Axes] PollInterval=10 RangeRepeatRate=10 I understand the profile one, and I do use a profile for the CRJ. But I do not understand why it's adding the RudderBlendLowest=1 and the two axis parameters in the FSUIPC5.INI and not in the profile file? It only does that for that plane. Also I already have the RangeRepeatRate=10 in all of my profile, so why is it repeating in the FSUIPC5.INI file. Being in the FSUIPC5.INI the parameter will now apply to all, and not only to the CRJ. Some clarification would help me understand. Pierre
  4. Hi Me again, I just conduct another test, I did a fresh installed of FSUIPC and PFCcom64 so I only had the CRJ plane configured. with both: 5=17Z,512,D,9,0,0,0 -{ DIRECT: Throttle1 }- 6=17R,512,D,10,0,0,0 -{ DIRECT: Throttle2 }- or 0=17Z,512,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }- 1=17R,512,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }- The Throttles works but they do not come back to the Idle position, But now If I load the aircraft in the Cold & Dark or Turnaround or Ready for Startup (all state that do not have the motor running) the aircraft load with his throttles in shut off mode. I am using the "FSUIPC with reverser Range" in the EFB , it is the only one working. so if I could get the THRs arm to go down to the Idle position and find out why the quadrant works when I only have the CRJ define in FSUIPC.CFG and not when I have other plane configured. Pierre
  5. Ok I am back and I do need some help. Like I said I had time to do some testing, and now I know that the plane is suppose to load with the throttle in the shut off position when It's load in the cold & dark state. What I did is: 1. disable FSUIPC be renaming the DDL to DDL_old, so it would not load 2. I also have a T .16000M joystick connected to my PC, so I configured the Throttle axis in the CRJ to be assign to the slider. If I load the aircraft in the Cold & Dark or Turnaround or Ready for Startup (all state that do not have the motor running) the aircraft load with his throttles in shut off mode. But neither my slider on the T .16000m Joystick or the mouse move the throttles in the sim. To move the Throttles you have to unlock them the two red-Knobbs. When I load the "Ready for taxi state" which as the motor running, the throttles loads in the idle position. So all this is according to the documentation. Next thing I did is to ask on the Aerosoft support forum if someone was using the CRJ Pro with the same PFC setup, one developer answered and also said: So I did check if I add a overlap for the Throttle axis, I don't if if I did I would have this issue with all my airplane. In the EFB you have two options: FSUIPC without Reverser Range FSUIPC with reverser Range (this is what I am using) My question is know which is used by FSUIPC? I am using the following profile : [Profile] Created=16/12/2019 10:33:56 [Axes] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=0R,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }- 3=17X,512,D,22,0,0,0 -{ DIRECT: Spoilers }- 4=17V,512,D,25,0,0,0 -{ DIRECT: Reverser }- 5=17Z,512,D,9,0,0,0 -{ DIRECT: Throttle1 }- 6=17R,512,D,10,0,0,0 -{ DIRECT: Throttle2 }- [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No 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 RudderBlendLowest=1 Aileron=-16312,0,0,16325 Elevator=-16384,0,0,16253 Spoilers=-16380,16380/16 [Buttons] 0=R20,11,K46,8 -{Key press: Del} I just installed the Airbus 330 from Aerosft and everything works fine. I only have the problem with this add-ons So with this configuration when the Aircraft load in "ready to Taxi" state the Throttles are to far up, and in the up position THR1 doesn't fully go up and THR 2 seem to be ok. In FSUIPC, in the axis assignment, I am getting the in values of: T1 -14578 14835 T2 -16384 16125 Hope all this helps Thanks Pierre
  6. Hi Pete, I had time to do some testing, and now I know that the plane is suppose to load with the throttle in the shut off position when It's load in the cold & dark state. What I did is: 1. disable FSUIPC be renaming the DDL to DDL_old, so it would not load 2. I also have a T .16000M joystick connected to my PC, so I configured the Throttle axis in the CRJ to be assign to the slider. 3. Then I reloaded the CRJ:
  7. I Thomas, I just tried what you said and it doesn't solve my problem. The throttles are not coming back to the Shut off position . Also I notice that they don't always work inside the sim (P3D). Sometime they move and sometime they don't. I do have the option FSUIPC without reverser check in the EFB. Everything else works elevator, alerion, spoiler and steering tiller. I just realized something, after the aircraft is loaded if I move my reverser arm first then the throttles are working, but still stuck at the idle state. they start at shout off and then jump to idle. Pierre
  8. Hi Pete, me again. I am trying to calibrate the last plane I own, the CRJ Professional from Aerosoft, not easy. When the airplane load both Throttles are in Shoot off position, but when the load is over both Throttles jump to idle position, but my throttle arms are fully down. So I cannot move the sim throttle to the lowest level (shut Off). I am guessing that it is related to the value FSUIPC sends to the sim. as you know, I am using PFC equipment (Cirrus II with the 2 jet Quadrant), I have followed the guide supplied by Aerosoft FSUIPC Throttle calibration (1).pdf The quadrant is define in PFCcom64 and properly assign to the aircraft. J2-0=5,30,0,20,35,35,108,255 J2-2=5,5,0,7,7,72,125,128 J2-3=5,6,0,0,56,72,126,128 J2-5=5,32,0,3,56,72,125,128 [AircraftQuadrants] CRJ700_Pro_Air_Canada_Express_C-GOJA=J2 In FSUIPC, in the axis assignment, I am getting the in values of: T1 -14320 16125 T2 -16384 16125 [Axes] RangeRepeatRate=10 0=17X,512,D,22,0,0,0 -{ DIRECT: Spoilers }- 1=17Z,512,D,9,0,0,0 -{ DIRECT: Throttle1 }- 2=17R,512,D,10,0,0,0 -{ DIRECT: Throttle2 }- 3=17V,512,D,25,0,0,0 -{ DIRECT: Reverser }- [JoystickCalibration] Throttle1=-14320,-14320,-14320,16125 Throttle2=-16384,-16384,-16384,16125 This time both Throttle are acting the same. I have tried "Send direct to FSUIPC Calibration" and use the calibration screen, like they suggest in the guide and also send to FS. Both option result in the same problem. I have include the FSUIPC log FSUIPC5.log Pierre Nantel
  9. 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?) 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. 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. So just to make sure, I don't have to do that. In PFCc0m64 I just need to assign the quadrant to the aircraft. 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
  10. 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
  11. Hi Pete, For the other aircraft test it was done using the two piston engine Lockheed Electra 10A-Blank, I only assign the 2 jet quadrant to the aircraft in PFCcom64, nothing was configured in FSUIPC. During the test I move both throttle up and down twice. Here is the log file FSUIPC5 - PFC setup only.log In that file you can see that FSUIPC only recorded the movement event of the Throttles. .In order to start clean I re-installed FSUIPC and PFCcom64 and I am not using profiles. The first test I did was in PFCcom, I assigned the 2 jet quadrant to the airbus aircraft- as you can see on the picture the enable was not check. In the SIM the throttles didn't work. In FSUIPC in the axis assignment I can see movement for both throttles Then if I configure both axis to Send direct to FSUIPC Calibration and I do not calibrate them .. Then the Throttle works in the SIM. . If I Calibrate them Both the throttles are no longer working in the sim. If I enable the quadrant in PFCCom64 and I keep the axis to send direct without using the calibration option, the throttles are working in the sim. If I calibrate them they stop working in the sim Then I conducted the test "assigning in FSUIPC to the FS controls "Axis throttle1 set" and "Axis throttle2 set" without calibration." with a fresh install of FSUIPC and PFCcom64. First I assigned the quadrant to the aircraft in PFCcom64 Then I configured FSUIPC axis no calibration .And to my surprise the throttles work in the SIM, I have attached both the PFCcom64.ini and the FSUIPC.ini for your reference FSUIPC5.ini PFCcom64.ini Of course if I calibrate the Throttles they stop working in the SIM Again ,thanks for the time you are spending helping me. Pierre P.S: with both configurations "send to direct to FSUIPC for calibration" "and "send to FS" the issue with Throttle 1 is still there.
  12. Hi Pete, I am so glad you are helping me, sorry for the misunderstanding. I do have the first part of the log, see attach. Sorry for the NEW LOG, it was the first time I was using this part of FSUIPC.FSUIPC5.1.log One question about ''could you do similar logging 9without prssing the NEW LOG button, with a different, maybe default, aircraft", P3D doesn't have a default aircraft that use my 2 jet quadrant, can I use the PMDG 777 to do this test? this way I will keep using the same quadrant. For this test "try unchecking the throttles in the PFC calibration and instead assigning them in FSUIPC "direct to calibration" and calibrating there (ensuring in the calibration you set for "No Reverse Zone"). " , the throttle arms doesn't move in the sim. . When I did "try assigning in FSUIPC to the FS controls "Axis throttle1 set" and "Axis throttle2 set" without calibration", same thing when I move the arms nothing happened in the sim, but on initialization T1 did move up and was offset with T2. It seems that I need to enable the throttles in PFCcom64, it the only configuration that works. in PFCcom64- Throttle enable and in FSUIPC = "direct to calibration" and no calibration I will do the log test when I know which aircraft I should use. Also can I delete the 2 log files I have FSUIPC5.1 and 5.2, so I can start clean? My understanding now is even if I send to console window, it is still creating a log file, correct? Thanks Again Pierre
  13. I was hopping to be able to get my Throttle1 to act like the throttle 2. Meaning to get both throttles to be at idle state (0 THR) before I start my engines. see picture As you can see, T1 sits higher to the 0 THR mark but T2 is ok. This is the way they are when I load the plane in Cold and Dark state and they stay that way until I take off or land. I would like the throttle1 and 2 to be equally set at 0 THR. when I am un the ground, like this : So I am looking for a way to bring T1 to sit lower, equal to T2. Hope this help you understand my problem. I am trying to understand why is T1 not going as far down as T2? Pierre
  14. Hi Pete, It seem that I am running out of runways. It is not a big deal, except that the left engine can never be put at 0 idle when on the ground. Just for my curiosity, if the add-on plane was setup to be able to leverage FSUIPC calibration" and the "Joystick Calibration”, would I be able to solve my problem? I am asking because yesterday I downloaded the CRJ professional (as an update) and I notice that in the EFB option they have include the possibility to use FSUIPC to calibrate the throttles (see picture). So maybe I can ask Aerosoft to offer the same option for the Airbus series?
×
×
  • 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.