I flew back VFR KGRF->KCLM. C172 FL60, auto SID\STAR selection. Only issue was, since flight path crossed Olympic Range (several peaks > 6000ft), I had to manually ask ATC a FL increase (from FL60 to FL70) to avoid a peak I was heading toward. No other problem. I add bugreport file for this flight, in case ATC is in charge to prevent CFIT also while flying VFR (I could not tell).ntnll wrote: ↑Tue Mar 26, 2019 11:29 amThank you vittop for your fast feedback. Happy to hear first tests positive, I'm aiming to release as soon the last bug we'll fixed.
Linux users, please report any instability issue on the last version, many thanks.
I finally flew VFR between two small airfields, 7WA0 to WA59. I filed FPL to TWR but no answer. Probably the airfield is towerless. After TO I called Center freq, and a popup asking me to request VFR appeared. Center replied asking me to sqawk code on XPDR, I replied then X-Plane crashed, here are last three communications:
124thATC v2.0-a60RC27 14:00:25: Communication: Center, good afternoon, N172SP request VFR clearence to Rakes Glen as filed.
124thATC v2.0-a60RC27 14:00:36: Communication: N172SP, cleared to Rakes Glen, squawk 2321.
124thATC v2.0-a60RC27 14:01:33: Communication: Cleared to WA59, squawk 2321, N172SP.
Tested also WA59 (this one with TWR) to WA45. Another crash, this time after TO clearance
124thATC v2.0-a60RC27 14:49:46: Communication: Rakes Glen Tower, good afternoon, N172SP on holding point of runway 09, ready for departure.
124thATC v2.0-a60RC27 14:49:59: Communication: N172SP, wind is calm, runway 09, cleared for take off.
124thATC v2.0-a60RC27 14:50:07: Communication: Cleared for take off runway 09, N172SP.
at the end I succeeded with VFR WA59->WA45, no crash. Can't tell where's the difference from above test.