Release Candidate (RC) Version - Download and Feedback

Forum dedicated to the alpha, beta, and RC versions
RandomUser
Posts: 67
Joined: Fri Aug 31, 2018 10:15 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by RandomUser » Sat Jun 15, 2019 5:22 pm

Bryzian wrote:
Fri Jun 14, 2019 3:13 am
Hi. I have been getting a crash in X-plane 11 when enabling the AI traffic for a long time that I gave up on long ago. I tried this RC version to see if it was ever fixed. I started getting the crash in 0.59 but If I remember right when I went back to 0.58 it still kept crashing. I did find XPFW ai planes that work with xplane 11 @ https://forums.x-plane.org/index.php?/f ... -for-1110/. The manual states that they aren't supported in XP11. These don't fix the crash though. The AI option will crash with these planes or the Laminar Research planes. I really miss having all the AI planes being controlled by this ATC plugin. All the traffic on frequency was fun to hear! Maybe with this bug report you might be able to tell what is cauing it. It looks like the log isn't giving much info though. I made this crash happen at KORD with 3 AI planes. Looks like it is just crashing to desktop if AI traffic is enabled. Thanks in advance for looking at this!
I'm surprised that AI ever worked at all. Every release I've tried (59 and newer) crashed whenever activating the AI feature.

peroni
Posts: 11
Joined: Wed Nov 07, 2018 5:54 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by peroni » Mon Jun 17, 2019 8:37 am

I would suggest to take out that AI option for the final release of a60
I know it says experimental next to it but we all know it is not working and would prevent new users to get constant crashes if they enable it without knowing how to turn it off.

ntnll
Posts: 410
Joined: Sun May 13, 2018 12:32 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by ntnll » Mon Jun 17, 2019 9:19 am

peroni wrote:
Mon Jun 17, 2019 8:37 am
I would suggest to take out that AI option for the final release of a60
I know it says experimental next to it but we all know it is not working and would prevent new users to get constant crashes if they enable it without knowing how to turn it off.
I'm actually thinking either to bring back the feature to an acceptable stable behavior, or disable it.
124thATC Developer

peroni
Posts: 11
Joined: Wed Nov 07, 2018 5:54 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by peroni » Mon Jun 17, 2019 6:34 pm

If you could get that to work it would be phenomenal

stewy81
Posts: 23
Joined: Fri Jun 22, 2018 8:03 am

Re: Release Candidate (RC) Version - Download and Feedback

Post by stewy81 » Tue Jun 18, 2019 4:31 pm

I flew a route in North Carolina today with no issues at all. KGSO - KILM using a payware DHC-600 on x plane 11.35B2 with RC37 124th atc

Looking very stable for me, I'll try some more flights when able and let you know.

Thanks,

John

haruka
Posts: 2
Joined: Tue Jun 18, 2019 8:48 am

Re: Release Candidate (RC) Version - Download and Feedback

Post by haruka » Thu Jun 20, 2019 1:16 am

aeroflo wrote:
Sat Jun 15, 2019 12:42 pm
I'm not really sure if this is a bug or not but when I tried to file a flight plan with airways, X-Plane crashes. If you look in the X plane log you can see it is trying to use an airway as a waypoint. I think in an older version it worked perfectly. I also used it yesterday with airways and it worked.
If 124th should suddenly be unable to identify an airway it would cool if it just would replay XYZ not found instead of crashing the hole sim.
Again tested on X-Plane 11.34 and macOS 10.14.5
I have a very similar crash, but it's not when searching for an airway, see below for preliminary analysis.

My filed fp was:

(ZBAA) KM61D KM A596 EGANA DCT REPEP REP11A (ZBOW)

When searching for KM, the plugin also crashes after "Found DME" line. It seems that the logic of distance comparing has some issues, as the plugin should be comparing if the DME found is closer than previously found VOR or NDB (in this case both was found before).

Related logs:

Code: Select all

124thATC v2.0-a60RC37 08:40:05: Entering SearchNavType...for KM
124thATC v2.0-a60RC37 08:40:05: Searching close to aircraft position 40.073490 - 116.604942
124thATC v2.0-a60RC37 08:40:05: SearchNavType: Try to find: KM near lat 40.073490 and lon 116.604942
124thATC v2.0-a60RC37 08:40:05: SearchNavType: less of 5 chars waypoint, searching as VOR...
124thATC v2.0-a60RC37 08:40:05: SearchNavType: Found VOR lat/lon 35.199139/128.935608 in a distance of 654 miles (navType: 4)
124thATC v2.0-a60RC37 08:40:05: Looking for a closer NDB...
124thATC v2.0-a60RC37 08:40:05: SearchNavType: Found NDB lat/lon 40.388332/115.496666 in a distance of 54 miles, (navType expected: 2)
124thATC v2.0-a60RC37 08:40:05: SearchNavType: NDB (dist 54 nm, 40.388332/115.496666) is closer than VOR (dist 654.000000 nm, 35.199139 35.199139), using NDB, (navType: 2)
124thATC v2.0-a60RC37 08:40:05: Looking for a closer DME...
124thATC v2.0-a60RC37 08:40:05: SearchNavType: Found DME lat/lon 37.549221/126.797531 in a distance of 500 miles, (navType expected: 1024)
--=={This application has crashed because of the plugin: 124thATC v2.0-a60RC37}==--
...which is pretty similar to the logs in the quoted post above.

EDIT:

After using some ways to tinker with it (please bear with me on that, trying to be helpful), I've found that when a DME was found but does not belong to the actual plan, the logging sprintf has incorrect parameter order or string format, thus leading to this crash.

Actually "NDB is closer than VOR" line also has incorrect parameter...

ntnll
Posts: 410
Joined: Sun May 13, 2018 12:32 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by ntnll » Thu Jun 20, 2019 8:56 am

haruka wrote:
Thu Jun 20, 2019 1:16 am
After using some ways to tinker with it (please bear with me on that, trying to be helpful), I've found that when a DME was found but does not belong to the actual plan, the logging sprintf has incorrect parameter order or string format, thus leading to this crash.

Actually "NDB is closer than VOR" line also has incorrect parameter...
Thanks everybody guys for your valuable feedbacks!
Yes there was an incorrect sprintf print causing the crash, I already corrected this bugs some days ago. Thanks for report it!
Haruka, how did you realized it? :lol:
124thATC Developer

haruka
Posts: 2
Joined: Tue Jun 18, 2019 8:48 am

Re: Release Candidate (RC) Version - Download and Feedback

Post by haruka » Thu Jun 20, 2019 9:35 am

ntnll wrote:
Thu Jun 20, 2019 8:56 am
Thanks everybody guys for your valuable feedbacks!
Yes there was an incorrect sprintf print causing the crash, I already corrected this bugs some days ago. Thanks for report it!
Haruka, how did you realized it? :lol:
I have a bad habit of reversing things that are not working as intended, so I tried to read the surrounding decompiled code...

ntnll
Posts: 410
Joined: Sun May 13, 2018 12:32 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by ntnll » Thu Jun 20, 2019 12:13 pm

haruka wrote:
Thu Jun 20, 2019 9:35 am
ntnll wrote:
Thu Jun 20, 2019 8:56 am
Thanks everybody guys for your valuable feedbacks!
Yes there was an incorrect sprintf print causing the crash, I already corrected this bugs some days ago. Thanks for report it!
Haruka, how did you realized it? :lol:
I have a bad habit of reversing things that are not working as intended, so I tried to read the surrounding decompiled code...
ahah, I noticed ;)
Thanks for your feedback.
a.
124thATC Developer

johnbla
Posts: 22
Joined: Mon May 21, 2018 12:34 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by johnbla » Fri Jun 21, 2019 12:04 pm

Hi, I don't think this is a bug, I just need some clarification. I am using the latest beta. Just flew a VFR flight from YCAS to YTFD which is on a bearing of 253. After take off I was vectored onto a course of 073 (which is in the opposite direction) for a few minutes before being vectored to 253. As I was flying VFR, I would have thought that I would be vectored straight to the destination airport. Is this normal? It just seemed odd to be vectored in the opposite direction for no reason, especially when flying VFR. Log file attached. Thanks, John.
You do not have the required permissions to view the files attached to this post.

ntnll
Posts: 410
Joined: Sun May 13, 2018 12:32 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by ntnll » Fri Jun 21, 2019 12:23 pm

johnbla wrote:
Fri Jun 21, 2019 12:04 pm
Hi, I don't think this is a bug, I just need some clarification. I am using the latest beta. Just flew a VFR flight from YCAS to YTFD which is on a bearing of 253. After take off I was vectored onto a course of 073 (which is in the opposite direction) for a few minutes before being vectored to 253. As I was flying VFR, I would have thought that I would be vectored straight to the destination airport. Is this normal? It just seemed odd to be vectored in the opposite direction for no reason, especially when flying VFR. Log file attached. Thanks, John.
Hi johnbla,
Not sure without the full bug report attached. Have a look to the .kml google earth files, and see if you recognize the flight plan patter.
124thATC Developer

johnbla
Posts: 22
Joined: Mon May 21, 2018 12:34 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by johnbla » Fri Jun 21, 2019 1:09 pm

Just did another VFR flight and all was OK.

ntnll
Posts: 410
Joined: Sun May 13, 2018 12:32 pm

Re: Release Candidate (RC) Version - Download and Feedback

Post by ntnll » Mon Jun 24, 2019 8:53 pm

RC build a60RC38 uploaded:

- Increased flight plan parsing function stability.
- AI overall stability improved
- AI models placement issue partially addressed (still working on the elevation precision, but planes should not float in the air anymore)

The AI function is still FAR from stability, use it if you want to see strange things happen. Don't waste your time providing any feedback about AI issues, there are already many identified bugs, I wouldn't concentrate on that for now.

Please report any stability issue. As usual, please corroborate your comments with bug reports, or at least the XP log.

Thanks,
Antonello
124thATC Developer

peterg
Posts: 8
Joined: Tue Oct 30, 2018 8:43 am

Re: Release Candidate (RC) Version - Download and Feedback

Post by peterg » Wed Jun 26, 2019 11:10 am

First Flight with RC38 from EDDT to EHAM.
Everything works fine.
Thx a lot.

vittop
Posts: 77
Joined: Tue Dec 11, 2018 7:50 am

Re: Release Candidate (RC) Version - Download and Feedback

Post by vittop » Thu Jun 27, 2019 7:49 am

Retried once KASE-KDEN with RC38: it seems that the "Initial FL70" bug (KASE alt is 7800) has been fixed, after T/O I've been cleared to FL100 initially so no more mismatch between atc and my actual altitude.

Retried once LIPQ-LIML with RC38, no crash when filing fpl anymore.

Retried once KPAE-KCLM with some wpts (SEA-ULESS-ARRIE-ELWHA), no crash but as usual after ULESS atc doesnt's tell me to turn northbound toward ARRIE, while FMS correctly terminates SEA-ULESS leg and indicates new leg ULESS-ARRIE as active. Please find attached the debug

Thanks a lot
bugReport.tar.gz
You do not have the required permissions to view the files attached to this post.

Post Reply