Jump to content

C2615

Members
  • Content Count

    261
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

51 Good

About C2615

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    I belong to both VATSIM & IVAO
  • Virtual Airlines
    No

Recent Profile Visitors

680 profile views
  1. I just get a stool set aside for my stick. nice and level
  2. Now things are going wild, After 2 peaceful flight yesterday, Today I have almost identical occurrence on Carenado PC12! It happend while cruising, but AP and RXP750 have the airplane well in control I didn't even noticed it. only when I start to decent, I notice the throttle couldn't be bring down, end then I look my VC Yoke, it's full aft and right. After I disconnect PC12's AP, the airplane goes to same trajectory as E170 above, but different heading, about 330 this time, and level off at FL170 (I cruized at FL160 as planed) After a few try, I can only regain control by reloading(select and OK the same aircraft) PC12. luckly PC12 is much simper aircraft than E170. This really terrified me, as if it could happen in ANY aircraft. A few guys posted simular issue with ASP3D+PMDG aircraft and WXR on, but in my case, I had ASP3Db3 installed, then it doesn't work well with my 4.5HF3 so I leave it and uninstalled it's P4 interface (the one under mydocument\Prepar3D v4 Add-ons) but leave the main program of ASP3D untouched. then use back the ASforP3Dv4 I tried to close ASforV4 when it strike, but it doesn't help me to regain control. However it's the only major change of my sim before these 2 occurence I could recall, it's definitely worth to look into, I'll remove both AS and reinstall AS for P3Dv4 to see if it would happen again, but as I don't even know what would trigger it, it's hard to tell...
  3. The XP one works without problem, I can download it here: https://forums.x-plane.org/index.php?/files/file/39522-e-jets-speed-calculator/ BTW here is my database for FLEX temperature calculation for QSimplanner, just for better takeoff performance caculation😉 https://forum.simflight.com/topic/88983-e190170-performance-data-for-qsimplanner/?tab=comments#comment-539579
  4. What, they still sell the V2 version? Well, V2 is somewhat flyable with AP and MCDU, I can only speake for 170/190 then, but the aerodynamic is just not match the manual. The landing light/ Taxi light will make VC too bright to fly at night, but it's fixable via a FSLSpotlight profile.
  5. iFly offer 2D panel for 737 and 747, but currently for v4 only.
  6. Ok guys, this is my fresh "post crash" flight story in P3D(v4.5HF3), while there are some technique issue I would love if someone could explain, that's not the main point for me to post this topic. Like all story, it starts as a routine flight, I plan a small hop from RJFF to RJKA with feelthere E170, after my previous 2 uneventful legs from RJCH-RJBE-RJFF in FSL319 and P3D restarted. My DP from RJFF is MORIO3, 2 rectangle right turn after taking off from RW34 to heading south. All preflight and take-off are normal, after takeoff, I manually fly though flaps retracted above 4000' (NADP1) and the first turn, then AP engaged in NAV and VNAV mode. The 2nd turn done by AP, while slightly over shoot, it's correcting, after the aircraft turning back to route it stating to capture back by a slight left turn, then, it seems the left turn can't be stoped, and the airplane is starting to deviate from route to the left. "OK, fine, some buggy NAV path from feelthere, fair enough, I have seen something like this even from PMDG", so I just switched to HDG mode and turn it back on course. Then seems the HDG didn't work, so natually, I disconnect the autopilot and roll my joystick to right. That when I realised the "*thigh* has hit the fan". it doesn't work. the autopilot was connected as FMA annoced, but my airplane refused to respond my right roll input. Now my airplane has leved off itself at bearing 056, still climbing with full throttle, and no responds to any of my stick and rudder input. Even the yoke in VC dosen't move with my joystick. "Emmmm, I have seen this." I have recalled my distant memory in FS9 with GA727 and a freeware KingairB300, "it must be the 'default AP' jamd on at TO/GA mode" Since the AP disconnect button on my joystick is mapped by Feelthere's loadmanager, I reach to the "Z" key, and "Shift+R" for autothrottle, after that, still nothing. TCS button? no help. Now I start worrying, I reach to FSUIPC and set my button to "AUTOPILOT_OFF",and "AP_master" , still, no control. I tried reengage and disengage E170's AP by mouse push few times, doen't work out. BTW I have checked my joystick input, they are all good. Now the airplane is rockting over FL250, on the puls side, it's flying level and stright with a little climb, at least not at risk for a while. While not think it's that well simulated, I reach the checklist, turn off the FCM button and pull disconnect handle, MFD shows my control surface is in direct mode or disonnected, but I can feel the AP is still actively controlling the airplane. The throttle is also jamed in full, I can bring them back by moving my throttle device, but as soon as there is no new input, it will shoot back to full. But for stick and rudder, not even a glitch. Now what, I just want my aircraft back, I disconned all electric, still, the AP is active with blank PFD/MFD! Still thinking it's the AP TOGA problem, I reach to the LINDA dev mode and try to send both AP_off control and directly change offset of 0x07VC and 0x080C, without any luck. also tried to send offeset command by FSUIPC button mapping, nothing. I tried to close some program like AIFlow/AIgroudn , Lorby flashlight and FSX2ACIM etc, see if it's them interfering some offset. but nothing. Now the aircraft steady at FL310 somehow, it has power to accelerate, the CRZ alt I set was 280, and the setting in AP panel is all over the place by now, the FL310 seems been choosen by itself. To avoide overspeed, I have to bring back throttle constantly, while trying anyway I could think to disconnect the AP. While all three trim is under my command, The AP can easily override all my trim input. even with the stabilizer full up or full down. Now I admit there would be no way I can disconnect the AP. I tried to figure out how could I land this thing before I ran out of fuel, which I didn't bring too much. Trim and differentia throttle would easily been canceled by flight control input, I can't even hold the throttle back to lower my alt, even if I tried hard and steadily stall my airplane, as soon as I give up, the AP will bring it back to FL310 I can lower the landing gear, that will give my in a steady near stall at FL310, but hardly loss any altitude. Speed brake won't work as engine is not in idle, and flaps won't go out anyway. While sort of cheating, I went to Failure menu and failed the control surface, that turns out to be a disaster, it also disabled all my trim input, so I have to turn them back. Fail the Hyd sys and Elec sys doesn't have any effect at all. BTW, when AP try to save the airplane from free fall, the control indication on MFD shows normal deflaction of control surface, without any aerodynamic effecet as they failed...seems feelthere only got it to show where the yoke is... Then I start to manipulation the AP panel, while I had ATT FAIL, miraculously, I can control AP pitch and throttle somehow. Roll, HDG and NAV still don't work, but I can now command a steady VS though E170's AP, and hold an inputted AT speed, while doing so, the yoke in VC and elevator indicator gose full up, but viewing from outside, the tailplane looks normal. seeme the default AP is still trying to command TOGA, but E170's AP can beat it somehow. If I disconnect E170's AP, the airplane will pitch up violently, then adjust to steady climb. Now I had some of my control back, actually, almost all the pitch control, I need to find somewhere to land. That's hard, After few more try, I can't figure out how to control my heading anyway.... I kind of regret I have full elec thus IRSs off, but concidering the heading isn't controlled at the very begining, that might not ge better. While ditch near the shore of Japan is a good choice in reallife or in XP, it's not an option in P3D then.... With low fuel and sun setting, I just went any flat(ish) land I can see. Flaps still not working with low sped and alt somehow, but I can slow to 150kts, I planned to grab the fire handle as soon as touch down, as the STRAT/STOP switch won't work in air in case of bancing , And sure, that's just a crash, only if I turned the "detect crash" on...... welcome to the Ryotsu island.... Yet, after Evec, the AP still hoding my yoke and throttle HARD ================== To find out why, I switched to default Braon58, it seems working fine without AP engeged what soever. Then I switch back to E170, in cold and dark mode, the Yoke now not firmly jamed, but jumping (flashing) back and froth from center to my Joystick position. that looks weried, but after I powered up, that glitch gone. Then I test fly with AP (but no time for MCDU route), and even deliberately inject the default TO/GA command via FSUIPC and LINDA, I can't reproduce the same phenomenon. For safety, I set the "autothrottle_takeoff_ga =" to 0 in aircraft.cfg, Feelthere's Ejet TOGA logic works fine without the default one. This is my personal experience with a "black swan" type emergency, No procedure could cover it, I tried to deal it with all my knowledge both inside and outside of aviation (actually, feels it's more about software stuff...). the outcome? not so good IMO.... I still think it's about Autopilot jamed at on, and with feelthere's Ejet, when AP is normally on, the joystick has no input effect, just as what happend in this scenario. But I just don't have the skill and time to go though all the debug procedure. And seems I might not be able to repreduce it (and actually, I hope not).
  7. I don't have FA50, but from my experience with PC12, Carenado has it's own Lvar for most it's functions, and it's even more complex than that. For example, There are different Lvar for animate the button been pushed, the function been select, and the conflict function been deselect (like select VS would cancal ALT HOLD)... so it's very painful to make things work even with detected or list of lvar....
  8. My main concern is if mid/heavy airliners are landing at short runways, that's the risk of overshot. Like in Japan, there are a few 767 and 787 fly to airport with less than 2400m / 8000' of runway, or in US, 737 land on runway less than 2000m/6000' . While when landing at large airport, you may select low brake setting for less wear and better comfort, when opreating at those condition, you mush unleash all your stoping force you have.
  9. I start flight sim from 2002, but only when 2010 I start to log my time by FSP in FS9 only, at that time, I also occasionally fly FSX and XP (and some combat sim then). After all 4 pilot entry in FSP goes over 1000h, in 2018, I went to P3Dv4, and after half year, I finally got FSC for my FSP replacement, now it logs more than 1000h then. That send my "logged hour" over 5000, I think I'm in the 5000~10000 region then. My Logged Level-D Full flight Simulator hour is 28h, but I have about 10 more hours unlogged on those machines😜
  10. Could it be target distance like 2/3 of the runway length?
  11. Recently I use LNM for save flightplan for RXPGTN, beside that, it's handy for visualize and record flightplan path. For path finding, I now mainly use Qsimplanner as it has PACOTS and AUSOTS, QSim's fuel plan is also good, but no match to the real word data from Boeing PET I use.
  12. Thanks Bert, I'll take a look later, for now the scale is close enough as flight test result. I think it should have some nonlinear scale in the real plane, but I can't find any data for that, any real PC12 pilot could help on how this thing behavoir when turning on ground?
  13. I found this description in pilatus's manual (7-34-8): So I dig in the xml and RPN Scripting (and mostly by coping code from other place), to make it work like this. in GAUGEPC12\Gauge_Anum_DOWN_PC12V4.xml: under: <Image id="Gauge_Anum_PC12_BG" Name="Gauge_Anum_PC12_BGNOP"> <Transparent>True</Transparent> </Image> Add: (shold NOT included in <image>, I think it should start like line15 or so) <Update> <Script> (A:AUTOPILOT MASTER,BOOL) 0 != if{ 0 (>L:AUTOPILOT_MASTER_TIMER,number) } els{ (L:AUTOPILOT_MASTER_TIMER,number) ++ (>L:AUTOPILOT_MASTER_TIMER,number) } </Script> </Update> And then, find <Element id="Gauge_Anum_PC12_AP_DISENG"> ,edit the whole <Element> entry into <Element id="Gauge_Anum_PC12_AP_DISENG"> <FloatPosition>0.000,0.000</FloatPosition> <Visibility>(A:AUTOPILOT MASTER,BOOL) 0 == and (L:AUTOPILOT_MASTER_TIMER,number) 0 &gt; (L:AUTOPILOT_MASTER_TIMER,number) 18 6 * &gt; (L:AUTOPILOT_MASTER_TIMER,number) 18 66 * &lt; and</Visibility> <Image id="Image" Name="Gauge_Anum_PC12_AP_DISENG.bmp"> <Transparent>True</Transparent> </Image> </Element> Also, to synchronize the Master Caution Light. go to GAUGEPC12\Gauge_Anum_MASTER_CAUTIONV4.xml ,find <!-- TEST8_MASTER_CAUTION --> Edit them into (A:AUTOPILOT MASTER,BOOL) 0 == (L:AUTOPILOT_MASTER_TIMER,number) 0 &gt; (L:AUTOPILOT_MASTER_TIMER,number) 18 6 * &gt; (L:AUTOPILOT_MASTER_TIMER,number) 18 66 * &lt; and and (L:PUSH_TEST8_MASTER_CAUTION,number) 0 == and if{ 1 (>L:TEST8_MASTER_CAUTION,number) } els{ 0 (>L:TEST8_MASTER_CAUTION,number) } (A:AUTOPILOT MASTER,BOOL) 0 == (L:AUTOPILOT_MASTER_TIMER,number) 0 &gt; (L:AUTOPILOT_MASTER_TIMER,number) 18 6 * &gt; (L:AUTOPILOT_MASTER_TIMER,number) 18 66 * &lt; and and ! if{ 0 (>L:PUSH_TEST8_MASTER_CAUTION,number) } Now, when you (or something else*) disengage autopilot, the A/P DISENG light on CAWS along with Master Caution should only illuminate after 3 seconds of delay, and goes off 30 seconds later (with out this mod, the MC will go off 30s later in Bert's mod, that's where I got the code) (*Note, the AP should be disengaged when using pitch trim switch, it's not in the gaugue's logic, but I get it covered by assign both trim switch to autopilot_off control in FSUIPC.) And don't ask why and how it works, I don't know, the RPN scripting drives me crazy....
  14. I noticed with Bert's panel mod, the little write rectangle at the button of EADI move perfectly align with the ball indicator under it, Look up the manual, it says it's rate of turn pointer, rather than incliometer. So I dig up the xml's (for the first time) and made some modification to get it right. I changed these line in GAUGEPC12EADI\Gauge_EFIS50_EADIV6.xml and GAUGEPC12EADI\Gauge_EFIS50_EADIVCV6.xml <Element id="Slip Indicator"> <FloatPosition>255.000,370.000</FloatPosition> <Image id="pfd_slip_indicator.bmp" Name="pfd_slip_indicator.bmp"> <Transparent>True</Transparent> <Axis>12.500,0</Axis> <Bright>True</Bright> </Image> <Shift id="Shift"> <Scale>60.500,0.000</Scale> <Expression id="Expression"> <Minimum>-1.000</Minimum> <Maximum>1.000</Maximum> <Script>(A:Turn coordinator ball,position)</Script> </Expression> </Shift> </Element> INTO <Element id="Slip Indicator"> <FloatPosition>255.000,370.000</FloatPosition> <Image id="pfd_slip_indicator.bmp" Name="pfd_slip_indicator.bmp"> <Transparent>True</Transparent> <Axis>12.500,0</Axis> <Bright>True</Bright> </Image> <Shift id="Shift"> <Scale>1000.000,0.000</Scale> <Expression id="Expression"> <Minimum>-1.000</Minimum> <Maximum>1.000</Maximum> <Script>(A:TURN INDICATOR RATE,position)</Script> </Expression> </Shift> </Element> While there is no scale described in the manual, as common sense, I made it aligen to the scaler above when in 3deg/sec standard turn...by manual fly test... so it might be off a little, if anyone could give me exact value, appreciate. Also a side effect is when turning on the ground (and if you dare to kick rudder in flight) the pointer will go way off the edge of display, I don't know if it's what real aircraft would show, and I don't know how could I stop it... If anyone could help to improve the very first xml gau modification I did, appreciate. EDIT: with more test flight, changed the scale valur a little bit
  15. C2615

    EPS armed

    I just got the Bert's mod with autogyro, it's amazing on the system depth. However I noticed a small but that persists from the Carenado's original one, the EPS system As the Pilatus's manual's Supplement No.22 the EPS, when armed should only be ON (with the amber "ON" light) when BAT BUS fail or total power loss, to power COM1/NAV1 and some backup gaugues. But in this sim , it's the opposite, when you have power and set it to ARMED(as for almost all normal flight), the EPS ON light wil always illuminate, and when BAT power cutted, it will extinguished... Anyone knows how to deal with this bug? this seems to be the few remining bug that keeps me using the manual's procedure, (well, the EPS is optinal, so maybe leave it in OFF is OK then...but there is the switches....)
×
×
  • Create New...