RETIRED_FR8TDOG

Hey Doug, Just wanted to say hello to you. You and I talked to each other (FedEx) many times over the radio, only I didn't know you back then. Just wanted to say thank you for putting out a good product which definitely improved the FSX experience now that I'm retired. Best wishes to you all.

Here is a video that might be the solution to your problem: http://youtu.be/s7ti6qdF53g

No they are not. You do, however, have an install options menu which allows you to deselect various kinds of airport and aircraft lighting modifications.

Take a look at the station identifiers at the bottom. They are different and should be the same. Definite bug. From what little I can determine, when you click apply after making a simple edit to the metar (ie: changing the vis to 1 mi) the wrong airport ends up getting the actual weather while the change is reflected in the metar report itself. (I'll explain why I think so below.)For example:Airport KABC visibility is 10 mi before changeEdit KABC to change visibility to 1 mile.Click Parse, then ApplyThe report indicates 1 mi visibility. Actual visibility does not change and in addition, the TAF report for KABC is substituted for another (close by) airport. When I edited the metar (wx config) on the "close by" airport, then I ended up getting the correct visuals for airport KABC. Strange, huh?(I can tell you the file being written to by ASE is: current_synthesized_wx.txt)I'm using build 651 (beta), but it also happens to the builds listed in this forum's title, too. The last couple of builds do not cause the "Parse crash" for me, but the configurator is definitely buggy. The two identifiers on the report screen (metar and taf) should be identical and you are not getting the visual changes after the edit.P.S. I'm a retired airline pilot and also a programmer.