Release Candidate (RC) Version - Download and Feedback

[ntnll]

Yes exactly.

Oh, I never saw this issue before. Can you please send me the log of the update run? The one attached is the after-update one.

[peterg]

Hi Antonello
RC64 crashed at LMML.
After inserting the flightplan I got a box for the SID, I selected. "AGAR2B" and crash.
I'm back to RC 63, everything worked fine.
I could not generate a bug report on my Mac. Permissions problem

Hi peterg,
thanks for the feedback. I can't reproduce the issue, if you have the chance, can you please send me the log.txt after the crash?

Thanks,
a.

Hi Antonello
same with RC 65
Log.txt attached

[ntnll]

Hi Antonello
RC64 crashed at LMML.
After inserting the flightplan I got a box for the SID, I selected. "AGAR2B" and crash.
I'm back to RC 63, everything worked fine.
I could not generate a bug report on my Mac. Permissions problem

Hi peterg,
thanks for the feedback. I can't reproduce the issue, if you have the chance, can you please send me the log.txt after the crash?

Thanks,
a.

Hi Antonello
same with RC 65
Log.txt attached

The log says you don't need update:

124thATC v2.0-a60RC65 08:05:22: This RC version doesn't need an update: 2060 65 > 2060 65

It should not suggests any update
a.

[peterg]

The problem is that Xplane chrash at LMML. Today I flow from LGAV to LMML without any problems. When I insert the flightplan from LMML and select a SID Xplane chrashes.

[ntnll]

The problem is that Xplane chrash at LMML. Today I flow from LGAV to LMML without any problems. When I insert the flightplan from LMML and select a SID Xplane chrashes.

Can you test please if it happens on the last 66 version too?
Thanks,
a.

[peterg]

Hi Antonello,
same with RC66. XPlane crashed at LMML when I select a SID. Sorry!!
Log.txt attached

[vittop]

Hi Antonello, I am testing RC66. Generally speaking runs good, but I discovered a small bug, since I experienced a crash when filing flightplans from seaplane wateways. It happened at NYC Seaplane Skyport (6N7) and also at Seattle Seaplanes (0W0). For this latter, I collected the debug files, please find them attached. Thanks

bugReport.tar.gz

Note: I asked XP11 to start from 0W0 (N47°37.66' / W122°19.91') but Log.txt contains W55 since the plugin offered automatically this into flightplan form. I remember this behaviour sometimes happens at Olympia,WA airport as well, since a helipad is very close to airport runway. Actually W55 is another nearby seaplane base (N47°37.74' / W122°20.32'): both seaplane bases are located 1 miles N of Seattle,WA. In any case I don't think this is the problem with the crash. In fact, I repeated the test and forced 0W0 as departure airport in my flightplan, but still I had a crash. I have a bugreport for this as well:

bugReport2.tar.gz

[ntnll]

Thanks guys, testing ASAP.

a.

[peterg]

Hi Antonello,
this Morning fromLIRP to LSGG without any problems.
At LSGG Plane crashed when selecting the SID
Log.txt attached, I hope it helps.

[ntnll]

I checked, the crash apparently occurs only on linux. I've been testing the previous RC, all of them crash. When did you linux users, started to face those crashes?

[vittop]

I checked, the crash apparently occurs only on linux. I've been testing the previous RC, all of them crash. When did you linux users, started to face those crashes?

I browsed back my posts, and found one I sent on Dec 29, 2018 7:57 pm, when crashed occurred as I tried to file a flightplan probably due to a STAR problem.

[ntnll]

I suppose is due a bug of the taxi parser.
The taxi parser function, is one of the really few still-untouched portions of the original source code by helicharly, and is extremely bugged. I need to rewrite it from scratch, and I really would like to push it back to next release, as it can requires weeks of work and tests.

I'm pushing now a patched version that should address the issue, but in some way, reduce the efficiency of the parser. Unfortunately this portion of the code is unstable, and not reliable, so I'll keep it pushed back as I did for AI, for the sake of stability.
BTW, apparently, for some reason, the bug affects just linux users.

a.

[peterg]

Hi Antonello,
I´m on a Mac

[ntnll]

Hi Antonello,
I´m on a Mac

Hi Peterg,
Sorry my bad, I meant Unix like, not Windows computer.
Can anybody confirm if the issue has been addressed with the work around?

[vittop]

I suppose is due a bug of the taxi parser.
The taxi parser function, is one of the really few still-untouched portions of the original source code by helicharly, and is extremely bugged. I need to rewrite it from scratch, and I really would like to push it back to next release, as it can requires weeks of work and tests.

I'm pushing now a patched version that should address the issue, but in some way, reduce the efficiency of the parser. Unfortunately this portion of the code is unstable, and not reliable, so I'll keep it pushed back as I did for AI, for the sake of stability.
BTW, apparently, for some reason, the bug affects just linux users.

a.

Hi, I tried to takeoff from Malta, Luqa LMML to LSGG, just to see if I had the same issue i.e. a crash when choosing a SID, but I did not: t/o was regular and I reached my assigned cruise altitude at 12.000ft. (I am flying a single engined GA plane). The crash happened instead as I, once seen I had no problem with initial phases, decided to land earlier than declared in the flightplan, by declaring emergency to land at Palermo. Please find the debug as usual attached.