ra.jones

That might not be a limitation of the Wilco pile though. Every time the AIRAC changes then the nav db airport ID's change, so the flight plan departure and destination id's don't point to the correct entries in the nav db. I wrote a script to look up the correct entries in the updated AIRAC and change them in the .rte file accordingly, but it's probably just as easy to load the nav db into MS Access (assuming you have it of course - Open Office doesn't seem to work for some reason) and update them manually. Then the flight plan works just as well. You might have noticed all the waypoints are OK (most of the time anyway), it's just the departure & destinations airports that don't show.

From Eric Marciano's web-site: So you won't see wipers, RAT, etc, and the anti-gravity free-fall descent rates won't have changed :)Weather radar not working is a bit of a let-down though. Was it because you were flying in CAVOK conditions?I'm not sure what the problem with ILS frequenices is, but the Wilco page does say it's going to install the December 2010 AIRAC version. What AIRAC version were you using before? Might that be the reason for apparently missing frequencies (ie they've changed since your version)? What's this? How does it work?

Not necessarily, if parallel runways in place (EGLL, EDDM, etc)

OK, I can probably answer my own question - from Eric Marciano's web-site: I am the developer of the Evolution version. The main differences between my upgrade and the Evolution are the weather radar (provided by Reality XP) and the Head-Up Display for low-visibility approach. The Evolution version doesn't bring any modification to the 3D model nor the flight dynamics. So presumably all the bugs that plagued its navigation systems are still present. Not sure what the claim on the Wilco page referring to the target altitude is all about:* Target Altitude The target climb or descent altitude is shown on the route with a blue arrow and its position is updated in real time. These arrows are sometimes called “hockey sticks”.I take this to mean that when I change vertical speed then the target altitude marker shifts position on the ND - pretty much like the Level-D 767 blue line. I don't see this behaviour on my EM-patched Airbus Series 1 & 2 - can anyone confirm whether this actually happens with the Wilco upgrade?

I don't think you need worry about that - apparently feelThere were not involved in this upgrade and officially know nothing about it. They're not going to support it.Do you know if the flight dynamics and nav display are anything more than the Eric Marciano upgrade? That patch drew some nice curved lines on the nav display for a 'direct to' amendment, and addressed a couple of other issues, but didn't fix the lamentably poor holding pattern functionality. Also didn't fix the bizarre behaviour after a route or STAR amendment when airbourne eg moving the top-of-descent point several hundred/thousand miles away, and pushing the predicted arrival time into the distant future and fuel well into negative figures!! There are many more anomalies also in the nav department. Does the Wilco patch address any of this?

It's not a problem online - just advise them 'TCAS climb' or 'TCAS decent', and they should be OK with it. Unless there's no other traffic around ;) Last time I did it on the VATSIM cross-the-pond event when someone ahead of me pressed their pause button.

Yeah, been there done that :)Suggestions: fly something with a functional TCAS (or install the superb freeware one by Lee Hetherington). Fly on VATSIM/IVAO - ATC would nomally prevent such occurences.

I don't have 64-bit Windows, just 32-bit Win7 and I used to get the CTD's with .gau errors regularly. I fixed it by turning off all the Microsoft 'security' dross (UAC and such) and never had a problem since (except perhaps the memory leak as I get 'out of memory' crashes after long sessions). I now find Windows gets in my way (slightly) less, and while it's arguably less secure (compensated by an effective firewall, antivirus & spyware suite, and common sense), if I was that concerned about security I'd use a proper OS in the first place. No guarentee it will fix the 64-bit CTD issue, but might be worth a try? I'd not hold out too much hope for the Wilco Evolution upgrade - as far as I can make out it's just Eric Marciano's patch plus a weather radar & HUD. I already have EM's fix and it didn't affect the CTD issues.