Litjan

That looks very well flown!

If you hear nothing from us, assume that the project is not abandoned but no work has been done on it that would warrant us sharing any progress info. If we abandon the project, we will announce this here - so if we don´t - you know it´s not abandoned.

The arrival fuel on the PROGRESS page is still buggy and does not show the correct fuel. You can use a rule-of-thumb though and calculate your fuel use by assuming that you will need 2400kg of fuel for 400 nautical miles - or 6kg (14lbs) per NM. This is valid for "when at cruising altitude", so you can calculate how much fuel you will use until you arrive at the destination.

We thought about it, but there is a reason why we did not include this. On aircraft without automatic alerting of incorrect barometric setting below/above the transition level/altitude, it is procedure to change the settings separately. For example if you fly at FL 210 and ATC says "descend to 4000 feet, altimeter 1032", the PILOT FLYING will change his altimeter immediately to the QNH setting (so he does not forget and the plane levels of at the correct altitude), but the PNF will only change his altimeter as he passes the transition level (so that if ATC changes their mind and tells you "stop descent at FL190" you have one altimeter set to the correct STD value, still. If we had made the altimeters sync, too - it would be impossible to follow this correct procedure with the sync enabled.

I would just like to add that the use of the adjective "broken" in connection with the current state of the 737 makes me question the validity of the other arguments that were brought forward as it made me assume that there is a fundamental misunderstanding about how this airplane works and a fruitful discussion about it´s shortcomings (that are openly and for everyone to read in this thread https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/ would be very difficult to have.

Nope. I meant all the - vaguely concealed - attempts to lure out information that have been posted by various users every few weeks. Which have all been replied to with the same: There is currently nothing to report. I am here to provide support for users with problems/questions and so is the customer support of X-Aviation. So the support for the plane is alive and well.

You can read the recent posts regarding your question.

The gross weight can be entered on the approach page to check "in advance" what kind of approach speeds you would expect (like when you do the approach in one hour or so) - accounting for burnt fuel until you actually will fly the approach. This is rarely used, but the way it works in reality. Normally you are not supposed to EVER enter the gross weight or zero-fuel-weight after the initial setup. The fuel totalizer will add the current weight of the fuel to the zero-fuel weight (as entered by the pilot) and thus your gross weight will always show the correct, current value.

It sounds like you are doing everything right - there is really not much to it. There are several tutorial videos here: https://youtube.com/playlist?list=PLGRsg_6rB1D6f7lKjdw5r9P99swJtryhQ&si=t3vEGmLMysqJ3zHE If you "lose" your tracking, it could be that your joystick is noisy or spiky, deflecting the joystick carries the risk of disengaging the autopilot. It should come with aural and visual warnings, though. If that happens, you can increase your Joystick Deadzone in the preferences, so that a slight "jitter" will not disconnect the AP.

Is the autopilot you are using on the same side as the ILS receiver you have set up? The 737 distinguishes between "masters" for the autopilot and flight-director system, you will see a small MA light up on the side that is "master". The "master" side has to be the one that has the ILS tuned - for example if autopilot A is on, but the ILS is set up on the first officers side, it won´t "capture" (but it also won´t capture the LOC, so this is probably not your problem).

No you don´t.

Not a bad idea - maybe it should not even depend on the livery (as for example Lufthansa had both options for autopilot engagement), but a user could set up a combination of preferences including the livery and then save them under a unique name...

Yes, Cameron is correct - when the plane calculates that it won´t be able to reach it´s cruise altitude and then descend again in time for the landing, this message will appear. It can also happen that a different STAR or SID has an altitude restriction on it, that makes it impossible to reach the cruising altitude. When you change a SID or STAR while you are already flying another one, VNAV can get confused about the phase of flight it is on (climb, cruise, approach)

Hi Stephan, I can confirm that behavior! Thanks for finding this bug - I will alert @tkyler to this, it is probably just an oversight - you are the first to mention it! Thanks for the profound and well researched report, Jan

That is correct - if you purchased after the 6th of 2022 (the X-Plane 11 version) then the upgrade to the X-Plane 12 version should be free. Pils is correct, though - you will have to go through the support of X-Aviation to clarify your situation, provide a proof of purchase probably and then wait until support answers. Note that each new question you add to your support request will reset your position in the queue to the very end again. So impatient users that ask "hey, did you read my message?" every second day will never get an answer. Occasionally the person handling support requests also goes on vacation and does not work support during that time, so especially during vacation times it can take quite a while to get an answer.