Jump to content

AngelOfAttack

Members
  • Posts

    60
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by AngelOfAttack

  1. The speed brake not complete down thus trigger the TO config warning is quite common IRL on a 737....
  2. I'm yet on WIN7 because I was disgusted by the Appleization of Microsoft over new version of Win10 and Win11, so I think Linux will sooner or later be my next platform (guess what, XP12 won't run on win7)... Kinda wonder if wine+proton could get the job done? it'll be kinda weird since XP itself was verified running on linux, so the Proton database doesn't bother check...
  3. Today I found this little bug when doing an RNAV approach. I use LNAV/VS and AP was disconnected at around 1500', however I kept FD on. After landing, as the route deleted, I noticed the FMA goes V/S,FD and an amber CWS R. Normally, while CMD is engaged, if LNAV got disengaged, CWS R would show as roll channel have retreated to CWS, but in the case of both CMD and CWS were not engaged, the CWS annunciation should not be made. The autopilot behaivor during approach were not been CWS, only the FMA shows something not quite correct after landing Very little problem, but Hope you can nail it in the next update run you (hopefully) are currently working on.
  4. Is XP12 included in that 5%? And any chance for -400 and -500?
  5. As pre FCTM, rolling takeoff with less than 2 seconds 40% N1 stable time have negligible impact on takeoff performance.
  6. I know this is not well documented, I can't find such detailed description on FCOM or AMM, But I observed it on 737NG and confirmed with some older instructors who had flown on -300 that this behaviour is same with NG. To be fair I also don't have real or simulator on Classic to fully confirm it for now.
  7. Hi, I noticed the overall logic issue with Master Caution(MC) and System Annunciator(SA). Simply put, the MC and SA didn't stay illuminate with a condition in related system still presents but the "trigger" one already putted out. Here is a easy sensorial to recreate this bug: 1. load in ready to take-off condition. 2.Turn OFF any one of the HYD PUMP, let's say, ELEC 2(A) 3.The MC and SA "HYD" illuminate with "LOW PRESSURE" light on ELEC2(A). 4.Reset MC, both MC and SA now extinguished, but LOW PRESSURE on ELEC2(A) still illuminatng 5.Turn OFF another HYD PUMP, let's say ELEC1(B) 6.The MC and SA "HYD" illuminate again, so far as expect. 7. Without Reset MC, turn on HYD PUMP ELEC1(B) again. 8.on IXEG 733, upon ELEC1(B) turn on and LOW PRESSURE light for ELEC1(B) it extinguished, the MC and SA"HYD" would also extinguished. But IRL, since the ELEC2(A)'s LOW PRESSURE light are still illuminating on HYD panel, the MC and SA"HYD" would stay on, until been reset manually, or when all amber light on HYD panel off. PS: this logic apply to all SA. likewise easy to test on ELEC. PS2: This logic not cross different system, if I reset something on ELEC,but fault still these, a new fault on HYD not bring "ELEC" on SA, only "HYD"
  8. OK. I just ended up adding these 2 function: function IX3_ENG1_CUT_OFF() if (IX3_ENG1_N2 >= 46 and IX3_ENG1S == -1) then IX3_ENG1S = 0 end end do_often("IX3_ENG1_CUT_OFF()") function IX3_ENG2_CUT_OFF() if (IX3_ENG2_N2 >= 46 and IX3_ENG2S == -1) then IX3_ENG2S = 0 end end do_often("IX3_ENG2_CUT_OFF()") to "manually" cutoff the switches, so far seems work for me, only problem is now I lack the louder click sound when it happens natually, but still a normal click sound like when manually put it back by mouse
  9. Hi everyone, while fly 737s, on all other add-ons, I have 2 key set on my buttonpanel to make input on both starter switch, to make it easy for set CONT/OFF up on taking off and landing as it's much convenient to do so than use mouse click on high workload condition. For default IXEG inputs, I can only set one switch with one joystick input, so I tried to make a Flywithlua script to make it work. My code for this part is: dataref("IX3_ENG1S", "ixeg/733/engine/eng1_start_act", "writable") dataref("IX3_ENG2S", "ixeg/733/engine/eng2_start_act", "writable") function IX3_ENGS_CONT() IX3_ENG1S = 1 IX3_ENG2S = 1 end create_command("ixeg/733/overhead/ENGS_CONT", "ENGS_CONT", "IX3_ENGS_CONT()", "", "") function IX3_ENGS_OFF() IX3_ENG1S = 0 IX3_ENG2S = 0 end create_command("ixeg/733/overhead/ENGS_OFF", "ENGS_OFF", "IX3_ENGS_OFF()", "", "") I noticed when this lua is running, even without the lower part, just the 2 dataref() part , when I try to start engine, the start switch will not automatically cutoff, AND the engine will go up to 1millon RPM to fly high and crash the airplane at start up(would not happen if just hold the switch by mouse. I also tried: function IX3_ENGS_CONT() command_once("igex/733/overhead/left_engine_startswitch_to_CONT") command_once("igex/733/overhead/right_engine_startswitch_to_CONT") end create_command("ixeg/733/overhead/ENGS_CONT", "ENGS_CONT", "IX3_ENGS_CONT()", "", "") function IX3_ENGS_OFF() command_once("igex/733/overhead/left_engine_startswitch_to_OFF") command_once("igex/733/overhead/right_engine_startswitch_to_OFF") end create_command("ixeg/733/overhead/ENGS_OFF", "ENGS_OFF", "IX3_ENGS_OFF()", "", "") but somehow it doesn't work at all.
×
×
  • Create New...