jonfrederickl Posted August 11, 2016 Report Posted August 11, 2016 Started to configure my FMC until I got a soft crash. I had finished the route and was putting in the Arrival runway and star, I got the crash once I selected the arrival runway 24. LEMG-LECH Route: GDA B28 SOPET STAR: SOPE1R/ 24 Log.txt GizmoLog.txt IXEG_FMS_debug.txt Quote
Litjan Posted August 12, 2016 Report Posted August 12, 2016 We unfortinately get a crash when selecting a runway without an approach... this is on the list. Sorry for the inconvenience and thanks for the report! Jan 1 Quote
Sigmar Posted August 16, 2016 Report Posted August 16, 2016 Jan and Jon, I too experienced a couple of crashes like the one described above and -- erroneously, it would seem -- suspected database inconsistencies to cause those. Yesterday I performed a flight from Linz (LOWL, my home base in real life) to Kefalonia (LGKF). Wary about inconsistencies between the 737 database (still AIRAC 1509 in my 737) and X-Plane (AIRAC 1603 on my system) I proceeded from Brindisi VOR direct to Kefalonia VOR, selected a VOR approach on RWY 32 *without selecting a STAR*, then shortened the "approach" on the LEGS page by making the actual RWY waypoint the next one after KFN VOR, and was able to perform the VOR approach and landing, using HDG select to track the appropriate VOR radials and V/S for descent, and finally hand-flying and landing the 737, without any issues. Happy landings Sigmar Quote
Litjan Posted August 16, 2016 Report Posted August 16, 2016 Hi Sigmar, yes, it is perfectly possible to work around the problem by substituting a regular approach and then modifying it... or just disregard the magenta line in the end - after all you are going for a visual approach - this does not mean keeping visual with your EHSI . Of course we need to fix the core fault. Jan Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.