Litjan

I am fairly convinced that if you delete (not disable, delete!) Better Pushback, FlyWithLua, LiveTraffic and especially Volanta, things will work again.

Thanks for reporting back. This is the common problem, people install shady add-ons in an attempt to "improve" X-Plane to their liking, but really this is like inviting a total stranger to sleep in your house...and then later on you wonder why all of the silver cutlery is missing . There are unfortunately a million dubious hacks/plugins and add-ons out there that will happily change files or art-controls that are not supposed to be messed with - and Laminar (and sometimes add-on devs like us) have to deal with the fallout when suddenly "hey, my X-Plane does not work anymore, I did not do anything, I swear!!"

Have you switched the dim/bright switch to dim? Also, are you running a standard X-Plane installation, or have you installed other third-party software that may change light brightness?

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.