Release Candidate (RC) Version - Download and Feedback

[ruetzi]

I need to admit this is one of the worst scenario you can ask an virtual ATC to operate.

A top program is put through its paces. Almost anyone can go from Amsterdam to Belgium.

The only way to get in LOWI from rw 08, is to pass through that narrow corridor in the mountains, is extremely though to be elaborated by an algorithm. But I have in mind some workarounds for next release, that can ideally mitigate that issue.

Then my complaining has already borne fruit. You can only grow through new demands.

What you can try for now, is to disable approximation fixes creation and see if can helps in someway, but I don't expect big improvements anyway.

Since the approach on the rw 33 in Salzburg I have already switched them off.
But maybe I'll try to insert own points with altitude information into the flight plan without STAR, as it is shown on this approach WI750.

Greeting ruetzi

[SHaneD]

I'm using 124thATC v2.0-a60RC60, had a problem approach today.

Flying between DAAG & DAUK (in Algeria) everything was ok up until approach, I was offered 01 to land on, I declined and went for 19 (as the preferential runway), routing for 19 came up on the ND, I was then surprised to be given clearance for 01 not 19 when I approached the airport (wind was 321 @ 7 at that moment), I followed the routing on the ND and made my way to the airport and landed with no further problems

approach routing highlight.jpg

showing routing for 19 on ND and the clearance for landing 01 in the message window

bugReport.7z

ShaneD

HI ShaneD,
checking your log:

Code: Select all

No airport flows found, wind less than 10 knots (7 knots). Get runway by location...

So basically because the wind was just 7 knots, the plugin ignored it, and picked up the runway by location. The plugin in facts ignores the wind under 10 knots.

Having a reading about it on IVAO, I found the correct approach would be ignore it under the 5 knots, instead 10:

If the wind speed is lower than 5 knots, the wind can be considered not important as a selection criteria.

I'll make some further readings and I'll decide if reduce the threshold to 5 knots.
I'm open to any suggestion regarding the best approach, as I'm not really a real pilot.

A.

Thanks for looking into this so quickly, I was just surprised to get both ends of the runway to land on! will wait the outcome of your decision

Getting 61 now, Thanks

[stewy81]

Trying out RC57 today with x plane 11.40. Had issues with 124th telling me to descend to 3600 feet continuously while displaying the restrictions for each waypoint as I had them on my flight documents......attached is screenshot from in sim and the bug report. My restrictions had min and max altitudes. Airac is 1911

Thanks,

Bug fixed stewy81, thanks for reporting it.
RC61 online, hopefully the last one of this intense version.

Ant,

I had no issues with updating to 61 today. Also had no major issues during my flight. All went very well. Only one errant message to turn to a heading (waypoint) that I did not see or need on my flight plan during approach but it did not affect the approach clearances and flight level changes or vectoring beyond the one errant call. I think we have a stable release candidate here.

[ntnll]

Trying out RC57 today with x plane 11.40. Had issues with 124th telling me to descend to 3600 feet continuously while displaying the restrictions for each waypoint as I had them on my flight documents......attached is screenshot from in sim and the bug report. My restrictions had min and max altitudes. Airac is 1911

Thanks,

Bug fixed stewy81, thanks for reporting it.
RC61 online, hopefully the last one of this intense version.

Ant,

I had no issues with updating to 61 today. Also had no major issues during my flight. All went very well. Only one errant message to turn to a heading (waypoint) that I did not see or need on my flight plan during approach but it did not affect the approach clearances and flight level changes or vectoring beyond the one errant call. I think we have a stable release candidate here.

Many thanks stewy81 for the feedback.

Version 2.0-a60RC63 online, this is a truly "candidate" for the release. In a more correct versioning naming, it would be the "RC1", and all the previous one just "builds".

Speaking about that, starting from build 2.0-a61, I'll get rid of the notation "RC" for the test builds, I'll use it just for the pre-release candidates. For the testing builds, the "build number" will be used instead. This will addresses my previous bad habit, in favor of a better naming definition.

Thanks,
A.

[Andi111882]

I just had some issues with RC62:
I was not able to dial in the frequency 127,120 manually. The correct one (according to the aircraft) was 127,125.

[vittop]

Hi Antonello, great job, I had no issue while updating. I am testing "63" now, and I have only found a small detail to fix:

124thATC v2.0-a60RC63 11:48:23: Communication: PH AED, Altimeter 29.88, contact Princess Juliana Intl approach on 128.950, expect ULUBA1, runway in use 10, bye.
...................
124thATC v2.0-a60RC63 11:48:40: Communication: Altimeter 29.88, contact Princess Juliana Intl approach on 0.00, expect 128.950, runway in use ULUBA1, 10.

i.e. while reading back, variable values seem to be shifted one position to the right, starting with frequency that is replaced by 0.00. Looks like an array indexing issue.

please find the zipped log.txt attached

Log.txt.zip

[ntnll]

Hi Antonello, great job, I had no issue while updating. I am testing "63" now, and I have only found a small detail to fix:

124thATC v2.0-a60RC63 11:48:23: Communication: PH AED, Altimeter 29.88, contact Princess Juliana Intl approach on 128.950, expect ULUBA1, runway in use 10, bye.
...................
124thATC v2.0-a60RC63 11:48:40: Communication: Altimeter 29.88, contact Princess Juliana Intl approach on 0.00, expect 128.950, runway in use ULUBA1, 10.

i.e. while reading back, variable values seem to be shifted one position to the right, starting with frequency that is replaced by 0.00. Looks like an array indexing issue.

please find the zipped log.txt attached

Log.txt.zip

Good spot mate, thanks! Fixed in next build.
a.

[ntnll]

I just had some issues with RC62:
I was not able to dial in the frequency 127,120 manually. The correct one (according to the aircraft) was 127,125.

Hi Andi111882, thanks for the feedback, remember to attacch always a log. I'll try to replicate the issue.
a.

edit: bug found and fixed, thanks for reporting it!!

a.

[ntnll]

2.0-a60RC64 online.
Anybody there using XP10? Can you guys please create a signature with your specs? It will help me understanding hardware and XP version used by the users.

Many thanks,
a.

[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

[vittop]

Hi Antonello, great job, I had no issue while updating. I am testing "63" now, and I have only found a small detail to fix:

124thATC v2.0-a60RC63 11:48:23: Communication: PH AED, Altimeter 29.88, contact Princess Juliana Intl approach on 128.950, expect ULUBA1, runway in use 10, bye.
...................
124thATC v2.0-a60RC63 11:48:40: Communication: Altimeter 29.88, contact Princess Juliana Intl approach on 0.00, expect 128.950, runway in use ULUBA1, 10.

i.e. while reading back, variable values seem to be shifted one position to the right, starting with frequency that is replaced by 0.00. Looks like an array indexing issue.

please find the zipped log.txt attached

Log.txt.zip

Good spot mate, thanks! Fixed in next build.
a.

Retried the flight with RC64, now readback ok. Going on testing..

[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.

[Rafalec]

Hello, i have a problem with automatic update , last version is 59 , after starting xplane , 124th ATC propose to update to version 64 , i click on update , after that popup appear saying that update is applied and backup is done.

If i restart xplane , same process restart , proposing to update to version 64

Backup isn't created in plugin directory.

[ntnll]

Hello, i have a problem with automatic update , last version is 59 , after starting xplane , 124th ATC propose to update to version 64 , i click on update , after that popup appear saying that update is applied and backup is done.

If i restart xplane , same process restart , proposing to update to version 64

Backup isn't created in plugin directory.

Hi Rafalec,
I didn't get the issue. Is the plugin keeping suggesting to update after restarting x-plane, even if you actually updated on previous x-plane launch?

[Rafalec]

Yes exactly.