mga010 Posted August 29, 2017 Report Posted August 29, 2017 I just had a bug when planning the following flight: EDDM TURB6E TURBU Y107 ALESE L12 VIC LAREN1D.VIC1X LIPZ Whenever I enter the arrival the plan opens a console window with several red lines, and I have to reboot the plane. To be more precise: I enter the route completely, and select the departure with no problems. When entering the arrival, I select 04R ILSZ, LAREN1D. If I select the VIC1X transition the console window opens and shows me problems. I have no idea what log files you need. I attach the IXEG_FMS_debug for you and the console window. IXEG_FMS_debug.txt Quote
Litjan Posted August 29, 2017 Report Posted August 29, 2017 Thanks for the report, I think we can track it down with your data provided... Cheers, Jan Quote
Litjan Posted August 31, 2017 Report Posted August 31, 2017 Just to follow up - I entered the same routing you did and did not get a crash... there may be some additional info we need. The best way for us to recreate the problem is to get a video where you tape entering the routing (everything from the moment the simulator stops loading until you get the error-log window)... Cheers, Jan Quote
mga010 Posted August 31, 2017 Author Report Posted August 31, 2017 Hope that helps. Yours, Paul Quote
Litjan Posted September 1, 2017 Report Posted September 1, 2017 This is perfect, thank you very much for doing the video! Cheers, Jan Quote
tkyler Posted September 10, 2017 Report Posted September 10, 2017 (edited) Hey Paul. What nav data set are you using? Aerosoft or Navigraph? -tkyler Edited September 10, 2017 by tkyler Quote
mga010 Posted September 10, 2017 Author Report Posted September 10, 2017 Navigraph. The version can be seen in the video. It is the most recent one. Quote
tkyler Posted September 10, 2017 Report Posted September 10, 2017 (edited) I noticed that just before I revised my post The version that is. I'll try to reproduce with the Navigraph set. Thx. Hope I can recreate, this is a very elusive bug when it rears its head. -tkyler Edited September 10, 2017 by tkyler Quote
tkyler Posted September 10, 2017 Report Posted September 10, 2017 Got this one fixed Paul. Thx for reporting. A discrepancy in the navigraph vs original aerosoft entries brought this one to light, but it was clearly an omission of a much needed line of code in a very specific "IF path". -tkyler 2 Quote
mga010 Posted November 2, 2017 Author Report Posted November 2, 2017 Will there be an update containing this fix? I completely forgot about the bug, and tried to make a tutorial video today with this flight. Of course, it crashed again. I get older and seem to forget things. Paul Quote
Litjan Posted November 2, 2017 Report Posted November 2, 2017 17 minutes ago, mga010 said: Will there be an update containing this fix? I completely forgot about the bug, and tried to make a tutorial video today with this flight. Of course, it crashed again. I get older and seem to forget things. Paul Yes, it will be fixed with the next update. As for getting older and forgetting things - welcome to the club! 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.