mfor

Members
  • Content count

    109
  • Joined

  • Last visited

Community Reputation

40 Excellent

About mfor

  • Rank
    Advanced Member

Recent Profile Visitors

414 profile views
  1. FMC-Freezing Bug

    It's not about defender: any anti virus program would have to check the executable code the FMC is generating rapidly - so pretty much any virus program should trigger this. For some reason the forums here are moderated in a way to make it look like it's a problem specific to defender, when it really is about how the FMC calculates the routes on the fly, as all virus programs have to check those newly created files for viruses (how else would they know it's safe). So you need to make an exception for this in pretty much any AV program to prevent those freezes from happening, until IXEG can fix things on their end.
  2. The pressurization system has 2 (semi) automatic modes of operation: 1) Automatic - you set the FL and the destination altitude and the system will capture the take-off altitude and return to that level on a aborted climb and target the destination altitude for a normal descend. 2) Standby - you set the desired cabin altitude and can also make manual adjustments - this is useful for non standard flights, e.g. touch and go training. There are also two manual modes (AC and DC powered) where you control the opening of the outflow valve manually - this is for emergencies only (e.g. when ditching you'd close the valve manually to prevent flooding and turn off the bleeds to still allow de-pressurization) The flight/ground switch will activate/deactivate the system, however it will also automatically engage when there's no load on the wheels. For normal flights you would use automatic entering FL and destination altitude. I think it's also part of the procedure (may depend on operator) to set the cabin altitude to 200 below field elevation, so in case you quickly need to switch to Standby the plane will be fully de-pressurized when landed (the auto system handles that automatically afaik). As for the bank angle I think I remember someone (Litjan?) saying it should be lower at high speeds, however IIRC LNAV will disregard any limitations to follow the route.
  3. Take-Off Flaps setting

    On Sunday evening it landed at the small Taney County airport, seven miles (11km) away from Branson, Missouri. Passengers on board the Boeing 737-700 reported an abrupt landing as the large plane touched down on the 3,738ft (1,140m) runway. http://www.bbc.com/news/world-us-canada-25717016 Well, they probably needed flaps 15 for takeoff - and a new pair of pants
  4. Well they kind of have - not on a 737-300 though, I suppose. SCNR
  5. Anti Ice

    What you can do though is put the switch in the ground test mode for some time. This will operate the wing anti-ice on the ground. If you do that right before takeoff you can free your wings of ice just long enough for a takeoff and let the normal operation take over once airborne - in heavy icing conditions you might have to go twice through the maximum operating time or even press it while accelerating down the runway. As for running it on the ground - ours is apparently an early model: "Note that on early systems, i.e. those with a GND TEST position, with the WAI switch ON on the ground, the WAI is inhibited until lift-off i.e. 'armed', This is opposite to the present system." http://www.b737.org.uk/iceandrain.htm
  6. AFAIK it was accidentally not included in 1.2 and will hopefully be back with 1.2.1.
  7. Speed/LVL CHG Problem

    Have you tried disabling the axis and using key binds instead? That would at least confirm that it is a problem with the axis jittering above 0. My guess is that the other planes use different way of handling the axis, e.g. only consider the flaps set if the axis values is greater than say 5% of its value, while IXEG might be using >0. That's just a wild guess though, since I don't know how either product handles this. If that is indeed the problem then maybe you can cheat a bit when calibrating that axis, so that 0 is not fully pulled up - or try one of the tools mentioned in this thread
  8. Speed/LVL CHG Problem

    Couldn't you base the trigger for "flaps set" on a different value (if it is currently based on ">0".) for 1.21?
  9. 1.21

    Well VNAV is part of the package even though it may get confused at times, which apparently is time consuming to fix (i.e. rewrite) It works well enough for me and I definitely wouldn't want to give up the failure system, immersive sounds, EWGPS/TCAS or the refined flight model for a more feature complete FMC - YMMV of course. Do I wish the update(s) wouldn't take so long? Sure, but as far as I understand it the IXEG team all have "proper" jobs and cannot commit full time to the development. I still feel I got my money's worth out of it, after all it is the aircraft I fly most in XP.
  10. Disappeared as in replaced by by "steam gauges"? There is an option for those in the preferences menu. Edit: Realized just now, you are probably talking about the missing digits No idea why they won't be showing, maybe check for failure settings or some other plugin is causing problems.
  11. 1.21

    I can't really say how close to the real thing the engines are since I'm not a 737 pilot, however those who are seem to like the flight model. In any case I'd trust the explanations of the developers quite a bit more than some random guy's rants, whose only merit seems to be the ability to look up numbers in planemaker, without knowledge how they are used.
  12. Steep Descent with LVL CHG

    Don't know if they are semi accurate - just a two rules of thumb I picked up If you set V/S in feet/min to be about 5 times your ground speed in knots (half the number and add a zero) you'll get an fairly nice 3 (2.8) degree descend and you more or less keep your speed when clean and idle. (e.g. if you're doing 240 knots GS select ~1200ft/m ) for each 1000 feet you want to descend you need about 3.3 miles of space with that 3 degree descend mentioned above, i.e if you need to cross a fix at 10000 and are at 30000, you need to start your descend about 66 miles out - allow some extra miles for slowing down if you need to meet speed restrictions. (feet in 1000s multiply by 3 and add 10%) I use these as guidelines to check what VNAV wants to do and plan longer descends, and for shorter legs I use 1) as starting point for my v/s and adjust according to the "green banana".
  13. Steep Descent with LVL CHG

    Well I think level change will always have idle thrust when descending (N1 when climbing) and the AP can just the adjust pitch to meet the desired speed, so the descend rate is determined by the amount of drag you currently have. An Airbus would probably yell at you but the ole 737 just does it The MDH is barometric in that case if I'm not mistaken, so all you do is set the little orange bug at the altimeter - no computer involved there.
  14. No cockpit Buttons Have animation

    Try excluding the x-plane folder from live anti virus scans. Apparently what happens is that when you make changes in flight, the route is constantly recalculated and compiled from LUA into executable code which causes the AV to rescan it, slowing things to a crawl - at least that's my understanding as of now.
  15. ILS not working

    Have you actually tried any of the suggestions in this thread? (test default aircraft, disable plugins, repair/reinstall) People here are usually willing to help, but they can't just wave a magic wand and make your problem go away. It does not seem to be a general problem, because it works for (almost) all people, so we need to find/fix what is different/wrong on your system. And since we cannot access your system, you'll have to do the work I'm afraid.