Litjan

Unfortunately I don´t have a cure for this ready - the sounds are done with the OpenAL and on some systems they don´t seem to work right :-/

Thanks for reporting back...I really don´t know how a livery could affect the nav-radios. There is also the chance that you have the "disable downwind ILS" function enabled and if the wind shifts, the ILS signal will turn off for the downwind runway...

This is strange - does this only happen at one airport or at several? There is always the possibility that other plugins interfere (fly with lua, etc.) if you could attach the log.txt file from a run where the ILS did not work, I could take a look. Also, try to post a screenshot that shows the Mode Control Panel (where you set the ILS course) and the VHF NAV radios (where you set the ILS frequency).

Hi Patrick, just reading this - I am happy that you got it solved - and thanks for reporting back with the solution! Happy flying!

No, it works fine on everyone else´s installation - it must be something you are doing wrong. Also check if you have the default random failures on, there IS a chance for them to fail your nav receiver or even the ILS transmitters randomly.

Awesome, thanks for sharing that!

No, I can not replicate this on my end and I have no idea what could be causing it. The sounds are currently still using the OpenAL, so if that is not installed correctly or something is interfering with playing sounds on your system, this is beyond our control. I wish I could tell you how to fix it or do something on our side to fix this...but for now I can´t. Good luck, Jan

Yes, there are quite a few parameters to be met for an autoland approach to be legal (and safe), I think the crosswind limit was like 10 kts (it goes down with decreasing RVR). The 737´s autopilots have no access to the rudder, so it can not "decrab" or "sideslip" to counter crosswinds. It can also not maintain the centerline after touchdown (rollout), so all it does is fly you to touchdown (in full crab) and then the pilot has to take over and manage the rollout. Also keep in mind that some ILS localizers in X-Plane are not very well centered on the runway, this is due to inaccurate government data on localizer direction and also a certain leeway LR allows airport designers to place their runways (iirc it´s "within 5 meters" of the official runway end coordinate).

I do not see any problem with it.

@Vanadeo I just flew a pattern at TXKF with about 50 tons of weight (just under max landing weight), using flaps 40 and autobrake 3 for landing. The Vref was 131 and the Vtgt was 136 (no wind). On the replay it looks like the autobrake was disarmed at landing, but this was due to it being replay... I don´t feel that the nosewheel is coming down hard at all - if you are using autobrakes, the deceleration (especially at higher settings) sets in almost instantly and the resultant deceleration force will make the plane pitch down (like a car slamming the brakes also pitches down).

I will doublecheck those areas you mention

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