Litjan

As much as I can understand the wish for some update to this feature or that - if someone wants "a flight model update" it makes me think he just wants an update because updates are cool (and perceived as additional value). Something that is fine does not need an update.

Hmm, that is strange, I have not heard that before - do you have time acceleration on, maybe?

Hmm, thanks for pointing that out - I have just tried myself, and I can see those, too. It depends on the intensity of the "Background lighting" rheostat (behind the Captain´s control column), and I tried, but none of the rendering settings seem to affect it. I will see if I can investigate where those "shadows" come from, for now the only solution seems to be to either increase or decrease the background lighting a bit more, they disappear once that light reaches a certain level. Sorry for that inconvenience! Jan

I am glad to hear that you got it working! And thanks for reporting back.

In flight it should work! Let me know if it does not for you, we will troubleshoot together then.

That is correct - we have removed the GPU cart object because it would clash with the "dynamic" GPU cart that X-Plane provides now (at many airports). In addition, a lot of airports have ground power that comes either "out of the ground" or "from the jetway", so seeing a GPU cart is not always appropriate. Laminar has further tweaked their GPU functionality in recent months - but we feel that it is not always perfect (i.e. they won´t allow GPU while the plane is on the runway because that is "not realistic" - which is nonsense, of course, because in theory nothing would preclude the GPU to enter the runway and plug in). So for now we will simply "turn on the GPU" when you use that option, if you want to role-play it, you can also call up the "ground services" window (shift-g is the default key) and call up a GPU cart to make it look nicer.

Try to assign a button to "extend speedbrake one notch" and then try again - even in the real 737 the positioning of the lever is "finicky" and it is easy to misplace it and either not arm the speedbrake or actually start extending it. And of course you are not trying to arm the speedbrake while on the ground, are you?

Because they are fed from different static sources, and the standby altimeter is not corrected by the air data computer, but essentially works like the one in a Cessna would. A discrepancy of even 150 feet is perfectly normal, especially at higher speeds.

No, the FMS "knows" the correct holding entry and flies it automatically, too. I am no expert on holdings, though, I can not remember the last time I had to fly one. If you have to fly a holding with the IXEG, I would enter the holding fix on the fix page and then also enter the inbound radial - that way you have a pretty good depiction on the map. You could also do some quick math and calculate how far the plane flies at holding speed in one minute (usually about 4 nautical miles) and then draw a circle around the fix - that way you have a rough idea of when to turn inbound again (if you forget to start the timer on the outbound leg). When flying a holding pattern, the important aspect is to fly in the area that ATC keeps "clear" for the holding aircraft, the holding area. That is why there are certain speed limits for holding patterns, they keep the planes within the holding area.

https://skybrary.aero/articles/holding-pattern

Nice work! Normally ATC will clear you for "published holds" - or they give you holding instructions consisting of a fix, an inbound course and a timing (how long in flighttime the inbound leg should be).

I hope that you will continue to find enjoyment in it! Even if further development is unclear, I will be hear for the foreseeable future to help with questions and offer support. You will hopefully find that while not every nuance (and some arguably bigger ones like holds and a reliable VNAV PTH descent) are not incorporated, it flies well from A to B and if it was a real aircraft, I would not hesitate to fill it up with pax and fly it from A to B in the real world. Cheers, Jan

I totally understand that concern. We can not promise anything with regard to the future, so if your purchase today depends on a legally binding guarantee towards support or updates that lie in the future, I would hold back on purchasing it. It works today as advertised and outlined in the https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/ post. Beyond that Tom and I and X-Aviation can not make any promises. We can state intentions, but as we have seen in the past, best intentions sometimes fall prey to realities. All the best, Jan

Hi Charlie, The previous issue (from 2023) has been resolved and the plane flares fine (in my opinion, but I flew the real one only for 10 years ). To find the correct approach speed, enter the weight correctly into the FMS and then check on the approach page - it tells you the Vref, add 5kts to that to find the approach speed...technically you are expected to bleed off these 5kts between the threshold and touchdown, but in reality this is rarely done. If you feel that you lack authority to "pull the nose up", make sure that your center of gravity is within limits, if it is too far forward, the ability to increase pitch will be limited. To see smoke from the tires is perfectly normal, this is not due to hard touchdown but due to the wheels getting spun up super rapidly when they touch the ground.

Hmm, your rudder shows a 7% deflection to the right after take-off, this should be enough to start this kind of roll. Make sure your hardware is calibrated correctly - your values should be around 0.00 for aileron and rudder if you do not touch the controls. You can check your "rudder trim" to be at 0 - or even use it a bit to the left to make the rudder point straight. No real aircraft is ever perfectly "rigged" and in reality it is enough to have a bunch of US citizens sit on one side and a bunch of Japanese on the other to make you grab that trim knob. If all else fails, set up a bigger "nullzone" in X-Plane by increasing the response profile to include a "bucket" around the neutral position, so that small deflections of your hardware get interpreted as 0 input.

That is absolutely your prerogative. Some say minimal activity and updates indicate a lack of care by the developers, others say minimal activity and updates indicate a mature product that is not in need of them. As a developer I am partial, of course - but I personally still love playing games that have not had updates in decades, like the car I am driving, and both work fine. Ultimately I think the conclusion constant updates = high value is false, in fact some of my games that get constant updates leave me with the feeling that I "rather hold off playing them until they are done". Just my 2cts .

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!