Litjan

Hi Manfred, sorry for the late reply, I was on duty yesterday flying EDDF-KEWR.. Yes, this would have been my first guess - if the hydraulics are off (or failed) we simulate the so called "manual reversion" - the plane can still be flown with raw muscle power using the cables, but the flightcontrols are not powered, so they are very hard to move, like a car with the servo steering failed. We simulate this by making the controls move SLOW - the real controls are just HARD to move, but we can not simulate that...it may be possible with a force-feedback joystick like you have one, but those are still the exception for simulator users. I have flown that failure in the simulator a few times, and it is acceptable to have one pilot work the yoke with both hands (and the other one controlling the throttle on his command), because it is pretty much impossible to control the plane that way with only one hand on the yoke. Glad to hear that you are enjoying the plane, all the best, Jan

Sorry to hear that it is still not working - in your log it looks like you are running out of memory: 0:08:20.650 I/TEX: Target scale moved to 4.000000. Texture usage is 417.00 mb out of 691.98 mb available. Memory headroom is 292.72 mb 0:08:20.728 I/TEX: Target scale moved to 2.000000. Texture usage is 529.99 mb out of 516.74 mb available. Memory headroom is 0.00 b 0:08:30.761 I/TEX: Target scale moved to 4.000000. Texture usage is 417.07 mb out of 787.36 mb available. Memory headroom is 390.48 mb 0:08:30.836 I/TEX: Target scale moved to 2.000000. Texture usage is 529.99 mb out of 516.74 mb available. Memory headroom is 0.00 b 0:08:40.870 I/TEX: Target scale moved to 4.000000. Texture usage is 417.07 mb out of 784.12 mb available. Memory headroom is 387.16 mb 0:08:40.953 I/TEX: Target scale moved to 2.000000. Texture usage is 529.99 mb out of 516.74 mb available. Memory headroom is 0.00 b 0:08:50.969 I/TEX: Target scale moved to 4.000000. Texture usage is 416.74 mb out of 737.70 mb available. Memory headroom is 339.88 mb 0:08:51.073 I/TEX: Target scale moved to 2.000000. Texture usage is 529.99 mb out of 516.74 mb available. Memory headroom is 0.00 b , you have a very weak hardware (laptop with 3050 card with only 4GB) and while this may fulfill the minimum system requirement for X-Plane 12, it may not be enough to run 3rd party add-ons like the IXEG 737. A recommended hardware configuration for X-Plane 12 is a system with at least 32GB of RAM and 8GB of VRAM. One thing you could try is to reduce the slider for "Texture Resolution" and "MSAA" to minimum and you also need to remove all third-party scenery because it will also use Video Ram (for example the Ortho4XP) but also other scenery and libraries like OpenSAM and custom airports. They all have special "textures" that will try to load into your RAM and VRAM and eventually you run out.

Good morning, it looks like you are running several - potentially outdated, incompatible or unstable - plugins like Volanta, a Weather Radar, XPRealistic, XPilot, a touchdown recorder, and so on. There is also a long list of errors pertaining to the CSL aircraft used by the XPilot plugin... I also see that you are running this on a laptop with medium to low capabilities and have a lot of add-on scenery (like Ortho4XP, OrbX Innsbruck...), there are several messages about running out of memory . This is what I would suggest: Remove all third-party content to revert the X-Plane simulator to a "vanilla" state - i.e. the way it was when you first install it. Now install the 737 and see if it runs. If this works, you can install your other third-party plugins and content ONE BY ONE to see which ones causes the crash. Let me know if this helps!

Hello Joachim, It seems that you do not know how the Autopilot and Flight-Director system of the 737 (and all Boeing aircraft) works, and I can not explain it fully here in forum posts. I see you are still in TO/GA mode (you did not activate an appropriate vertical mode after taking off) and of course while using the Flight Director the same flight-mode-announcements are shown as if flying with the autopilot, the only difference is that the pilot is moving the controls, not the autopilot. The vertical line "jumping" is normal take-off behavior, it is the way that the FlightDirector is coded...the pilot is not supposed to follow the flight-director until he has safely taken off. I suggest reading and studying about how these systems and the flight mode annunciation works, there are also some good tutorial videos on what these do and how they are supposed to be operated. If you fly without knowing how the systems work, you will have lots of questions about "unexplainable behavior".

Exactly - the pilot does not care how many people sit behind the cockpit door, he only cares about the weight and the center of gravity.

Here, I found the thread I was remembering:

Hi and thanks for the feedback - sorry to hear that you are having this problem! We have heard of a report like this once before - it seems to be a problem with the OpenAL sound library system that is happening very rarely on some systems, for reasons unknown to us. I will try to find the post about this problem and see if there was a solution to it - eventually we plan to move the sounds to the FMOD sound system, which should solve this problem. Can you try setting your volume lower or putting your sound out on a different device (i.e. going from monitor speaker to headset or so)? Maybe that will help as it sounds like the sound volume is exceeding a certain sound level on your system, possibly. Sorry I can not provide any more clear guidance, Jan

It varies from airline to airline and even then between different configurations. If you put in many small seats -> more passengers, and vice versa.

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.