Jump to content

Litjan

IXEG
  • Posts

    5,657
  • Joined

  • Last visited

  • Days Won

    408

Everything posted by Litjan

  1. This approach is a "RF" (radius to fix) approach that only very advanced FMS versions can fly. The version number we model can not. Cheers, Jan
  2. No, there is no "pipper" for runway or taxiway alignment in the 737. And it would not work in most cases, since usually during an approach there is some crosswind, and also the 737 does not taxi "straight" (it has a slight slack in the wheel castors, so it looks like it is crabbing during taxi) There is a guide on how to set up the correct seating and head position in the real manual - but there is nothing to help you judge alignment in the lateral position (just sit straight and look straight ahead) . Cheers, Jan
  3. Whatever works for you! Happy flying, Jan
  4. I think dr_anthony probably has the answer - the effect is called "cinema verite" and can be accidentially triggered to ON. Check the X-Plane "view" menu... Jan
  5. Oh, the good old days of manual reversion flying in the simulator... skipped the workout in the health club on those days... Jan
  6. Yeah, I watched the video - it is a really complicated situation for the FMC - it still thinks that you are in climb mode and wants to go to CLB speed after recalculating the route after the DIRECT TO. I don´t really know what went wrong at that point, but in that case I would suggest to simply revert to a more simple autopilot mode like MCP SPD and V/S or FL/CHG. We will look at these kind of situations (descents involving several speed and altitude restrictions) more closely in the future, there is still a lot of work to be done... Jan
  7. Unfortunately the video is "private", so I can´t really see what is going on...
  8. I did have a conversation on this subject with Ben Supnik, so maybe he incorporated some improvement in this regard... "Fixed max deflection of low speed nose wheel when not using a hardware tiller." Not sure, have to check if this affects us... Jan
  9. I did have a conversation on this subject with Ben Supnik, so maybe he incorporated some improvement in this regard... "Fixed max deflection of low speed nose wheel when not using a hardware tiller." Not sure, have to check if this affects us... Jan
  10. Thanks for letting us know, Tom - I wonder what fix affected that one... Jan
  11. Nope, should just work like it did before. Jan
  12. This is already fixed for the next update, thanks for reporting! Jan
  13. Excellent - and don´t worry, the "combined modes" of A/T and AP pitch channel are probably the most complex systems in the 737. Still looking forward to clearing up that original bug - keep me posted! Cheers, Jan
  14. mmerelles is correct, the aircraft is behaving as intended. While you are in a VNAV PTH descent, the correct behaviour for the A/T is to go to RETARD first, then to revert to ARM. While in RETARD, you can not grab control of the throttles, only while in ARM. The intention is for the plane to have idle thrust and glide down the pre-calculated path. The autothrottle is "watching" the speed, though - if you are too fast, you will eventually get the "DRAG REQUIRED" message, if you get too slow, the autothrottle will revert to FMC SPD and add thrust until you are back on speed - then the cycle will go RETARD-ARM again. Jan
  15. No, but maybe Tom has - I am adding this to our bug-base... Thanks for the report, Jan
  16. Hi jamarns, I would be very interested to see a short video of this happening - even if you use the AP disengage bar on the MCP, the plane should be totally controllable. The only instance that you would see trimming while the AP is off would be when the speed trimming system kicks in (only during flaps not up and high power). But it should never render the aircraft uncontrollable. Cheers, Jan
  17. Thanks for following up on this, Jon. We are investigating and will fix this. Jan
  18. Hi, no, sorry, it does not work - yet. Cheers, Jan
  19. Thanks for the report! No solution for you yet, but we have seen this "turning away" before and are on track for fixing it! Cheers, Jan
  20. Hi Maestaru and thanks for the kind words! The other guys (absolute IXEG experts!) beat me to the answer, this was something we changed between video capture and release. I do follow these threads and answer whenever I get a chance - I can´t teach how to fly an airplane in here, but if there is an advanced question I am always happy to help! Happy flying, Jan
  21. Beautiful shots, Ricardo! I am just worried about the yellow Master Caution in picture #2, I hope you made it back to terra firma ok!? Thanks for sharing, Jan
  22. As a general rule, after flying two single-engine departures your leg on the live engine side should shake and hurt... Jan
  23. Litjan

    fmc crash

    Thank you for the report! I will add it to the bug-base... Jan
  24. I have done - nothing . I wonder if there is something else coming into effect for you here - some cross-assignment of braking, for example. There are keys that can be set up for braking, namely V and B, and I think you can also adjust if they "toggle" or "push to brake". Some users reported that the "B" key also toggles the Beacon for them - I think it is easy to map a key to braking by accident, and have it set to "always brake" after toggling it. Maybe you push a button to do something else (get a certain view, etc.) and it also "toggles on" the brakes? Another idea: Try the same on a "default" airport (not a custom one) - maybe the designer did something that affects the ground friction? There is also a certain code in place (default X-Plane, not IXEG) that adds "really strong braking" at very slow speeds, this is to avoid computational creep and flutter which used to make airplanes "shimmy" and weathervane in crosswinds - but this should not kick in at 10kts. Jan
  25. Thanks for reporting back on this, helios123! I hope that this update fixed it for you, let us know if you find out anything else, please! Thanks, Jan
×
×
  • Create New...