Litjan

Sorry I can not provide a better solution at this time - I also talked to Tom, and he also said that there is no quick fix for this, it seems to be an artifact of the volumetric lighting effect.

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.