Litjan

Hi, this is correct - the relais holding the connection to the generators are held close by battery bus current. Once the battery drains, you will loose all power to the aircraft. This will usually not happen, because the battery charger is powered through the ground service bus. If you turn off the battery switch, all buses will become unpowered, except for the hot battery bus. If you want to fly without AC generators you can - the battery will power all the buses you mentioned (but while on the ground, you need to move the standby pwer switch to "stby pwer", not to auto). But only if the battery switch is on. Once the battery is drained, you can not connect any power to the aircraft, anymore (not even GPU). Jan

A shrine... hmm. With priestesses? Like the oracle in 300? I will see what can be done :-) Jan

Thanks for the pictures, yes, sure looks like the conditionals are the problem. For now, I would suggest this workaround: Use HDG SEL to stay on the magenta until almost at the conditional waypoint, then fly DIRECT TO (enter LSK 1L) to the next "real" waypoint and engage LNAV again. Sorry for the inconvenience, Jan

Thanks for the detailed report, Juan - I am fairly certain that this is a problem isolated to your hardware configuration, otherwise we would have heard about this before and more than once. Can you give us a detailed report on the hardware you are using and the driver versions so we can track this problem down? Thank you, Jan

I will double-check, but the autopilot engagement status should have nothing to do at all with the operation of the autobrake. We are using X-Plane´s default autobrake, and it has a bug in that it requires to have ALL landing gear on the ground to work, whereas the real one only looks for wheel spinup and strut compression. Thanks for the report, Jan

No, I fly full time. But I have a nice gaming-laptop that fits just inside my flightkit and since I am old and married, I don´t have to entertain the flight-attendants and hit the bars during night-stops anymore, I actually get a lot of stuff done . Jan

I have it set, but don´t see the effect shown above... or do you mean that with HDR it´s fine, but without it´s not? Jan

You think so, eh? Jan

Couldn´t reproduce this - but would be very interested if there is something changing in 10.50 that we need to be aware of. So please check if you can make that go away by going 10.45 and then we will have to let Ben Supnik know... Jan

Once those guys pay me what my Airline pays me, I will consider switching full time! Jan

Hmm, I have never seen this - there has been another report of someone seeing the CDU corrupted when the "ground services menu" is open with XP 10.50b5, but I have not been able to reproduce that, either. Are you upgraded to the latest drivers for your video card? Jan

Hi Max, yes, there are! I could teach you here if I had a few months of time...but since I don´t, I would suggest you do some google searching for keywords like "FCOM" "737-300", and so on. I think there are even some links flying around in this forum...shouldn´t be hard to find for an internet-savvy person, but of course reading "official" documentation isn´t really entertaining. Jan

That could be related to another problem we have with "conditional waypoints" not being in the right spot...we are looking at that.# Jan

Hi, the TAS at those waypoints is way too high to make the turn - we need to work on our "bypass" code to show that on the LEGS page, but for now try to enter 170/ for the speed at the first waypoint and see if the route draws then? Thanks for the report, Jan

Thanks Werner! Jan

Yeah, I was still smiling, then....Now I fly Airbus. Jan

Thanks for the heads-up! I will check in the latest Beta myself... Jan

Hi, the problem is that the speed is too fast for the plane to make the turn - your speed at D165V is planned at 240kts and FL89 - the True Air Speed is too high to make the turn to the next waypoint. You can also tell by the LNAV route making a very "sharp" kink at that waypoint. Try to reduce the speed to 170kts or so (enter 170/ at LSK 1R) and see how it works then? Jan

I think the reason behind this behaviour is the "deselect" function of the pushbutton on the MCP. The take-off mode of the flight-director is basically FL CHG in the pitch channel with a complex algorithm to determine the target speed (V2+15 with both engines) and HDG SEL in the roll mode. This roll mode can not be deselected, though. So when you engage the autopilot, the pitch mode switches to FL CHG with a fixed speed, but the roll mode stays in HDG SEL (but can not be deselected - so no light on the button). Just my guess why... Jan

Hi Tom, yes, this is correct - we had some discussion about this back then and I didn´t quite remember, but one of our beta testers checked it in the real aircraft. The HDG SEL is active, but the button isn´t lit. Jan

Thanks for the report and the files! Jan

Thanks, Tim - we will look at it as soon as possible! Jan

The CWS P is a fallback mode when the GS is lost after it was captured. The plane will tolerate a missing GS signal for a second or so, but then revert to CWS P. This is working ok in your movie - but the GS should never capture in the first place in this scenario... Jan

Errm, no, it is not normal, it is a bug - when you push APP in that situation the GS should get armed in white - and stay that way until a valid GS deviation signal is within 1/5th dot deviation for the capture... Good find (probably only happens if the GS isn´t received yet)! Jan

Sweet, thanks! Jan