Litjan

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

No, but maybe Tom has - I am adding this to our bug-base... Thanks for the report, Jan

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

Thanks for following up on this, Jon. We are investigating and will fix this. Jan

Hi, no, sorry, it does not work - yet. Cheers, Jan

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

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

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

As a general rule, after flying two single-engine departures your leg on the live engine side should shake and hurt... Jan

Thank you for the report! I will add it to the bug-base... Jan

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

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

Ok, I checked and I think the update was for the ground handling plugin, not the towmaster. So there seem to be no solution so far. Sorry, Jan

I think there is an updated version for the jar design tow plugin available, at least that is what I remembered. Maybe it was in another thread, have to search a bit for it... Jan

Wow, that is cool! I have to try that! Thanks for letting us know, Gerald! Cheers, Jan

Yes. Jan

Did you guys check if your parking brake was still set, maybe? I ran some test and have the brakes at 0.1 (approximately) - my deceleration is much slower and steady all the way to 0 kts (no sudden increase in decel below 10 kts). Jan

Hi Sigmar, yes, it is perfectly possible to work around the problem by substituting a regular approach and then modifying it... or just disregard the magenta line in the end - after all you are going for a visual approach - this does not mean keeping visual with your EHSI . Of course we need to fix the core fault. Jan

We unfortinately get a crash when selecting a runway without an approach... this is on the list. Sorry for the inconvenience and thanks for the report! Jan

Thank you for the nice words! Happy flying, Jan

Yeah, there are still a few cases were the vnav calc gets screwed up. We are worling on those. Jan

There will ne one out very shortly, we have been working with the dev on that... should only be a few days. Jan

I habe never heard of that, so I assume its only valid for some (older) configurations. In our model the BAT position shows voltage of the battery bus. Jan

Interesting, I am following this to see if you find out the exact problem... you are not depressurizing the A-Hydraulics for the push, are you? (Some old procedures ask for this, when you don´t have a steering bypass pin). In this case make sure that you switch them on again after pushback... Jan

You can´t. This is a flightplanning format that can not be read by an FMS. You can enter coordinates if they are published as five-character waypoints, like N3050 or such. You would have to specify cruise speeds and level changes on the legs page, but changing level with the Step climb function is not yet supported. Jan