Release Candidate (RC) Version - Download and Feedback

Forum dedicated to the alpha, beta, and RC versions
vittop
Posts: 62
Joined: Tue Dec 11, 2018 7:50 am

Re: RCs public previews

Post by vittop » Tue Mar 26, 2019 12:19 pm

ntnll wrote:
Tue Mar 26, 2019 11:29 am
vittop wrote:
Tue Mar 26, 2019 10:00 am
RC27 tested KCLM->KGRF IFR, C172 FL60, auto SID\STAR selection: no problem. I will repeat same flight but VFR, then I will try IFR and VFR between small strips (no SID\STAR info). Will come back if any issue. Thanx
Thank you vittop for your fast feedback. Happy to hear first tests positive, I'm aiming to release as soon the last bug we'll fixed.

Linux users, please report any instability issue on the last version, many thanks.
a.
I flew back VFR KGRF->KCLM. C172 FL60, auto SID\STAR selection. Only issue was, since flight path crossed Olympic Range (several peaks > 6000ft), I had to manually ask ATC a FL increase (from FL60 to FL70) to avoid a peak I was heading toward. No other problem. I add bugreport file for this flight, in case ATC is in charge to prevent CFIT also while flying VFR (I could not tell).
bugReport.tar.gz
I finally flew VFR between two small airfields, 7WA0 to WA59. I filed FPL to TWR but no answer. Probably the airfield is towerless. After TO I called Center freq, and a popup asking me to request VFR appeared. Center replied asking me to sqawk code on XPDR, I replied then X-Plane crashed, here are last three communications:

124thATC v2.0-a60RC27 14:00:25: Communication: Center, good afternoon, N172SP request VFR clearence to Rakes Glen as filed.
124thATC v2.0-a60RC27 14:00:36: Communication: N172SP, cleared to Rakes Glen, squawk 2321.
124thATC v2.0-a60RC27 14:01:33: Communication: Cleared to WA59, squawk 2321, N172SP.

bugreport included:
bugReport1.tar.gz
Tested also WA59 (this one with TWR) to WA45. Another crash, this time after TO clearance

124thATC v2.0-a60RC27 14:49:46: Communication: Rakes Glen Tower, good afternoon, N172SP on holding point of runway 09, ready for departure.
124thATC v2.0-a60RC27 14:49:59: Communication: N172SP, wind is calm, runway 09, cleared for take off.
124thATC v2.0-a60RC27 14:50:07: Communication: Cleared for take off runway 09, N172SP.
bugReport2.tar.gz
at the end I succeeded with VFR WA59->WA45, no crash. Can't tell where's the difference from above test.
You do not have the required permissions to view the files attached to this post.

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

Re: RCs public previews

Post by vittop » Tue Mar 26, 2019 2:45 pm

bugReport3.tar.gz
This is the BugReport from my last, successful test WA59->WA45, couldn't put it in the previous message (max 3 attachments allowed, I guess), Anyhow, I did minutes ago another test switching back to IFR and got a crash. I went to settings.txt and discovered that, even if the interface was set to IFR, saved data still reported "vfrFlight#1". I guess this mess of mine could be due to a mismatch between value shown in the interface and the one actually in the file don't know if is a s/w bug or whatever else.

Thanks a lot, go on with your good job
You do not have the required permissions to view the files attached to this post.

argonius
Posts: 42
Joined: Wed May 30, 2018 2:14 pm

Re: RCs public previews

Post by argonius » Wed Mar 27, 2019 7:42 pm

Hi Antonello

Tested RC27 on an IFR flight from EGLC to EGGP (route: BPK WELIN T420 TNT) with manual STAR/SID selection.
- First of all - no crash (linux user) :)
- I selected RWY27 and SID BPK1A for departure
- Issue 1: I was directly cleared to cruise alt FL230, although the SID has an alt. restraint of 3000feet
- Issue 2: "My" clearance confirmation contained an alt of 0 feet instead of FL230
- Issue 3: With each heading call after departure I got "descend 0 feet", later there was a climb to FL230
- Cruise went fine, I selected RWY27 and STAR TIPO2G for arrival
- STAR TIPO2G requires FL100 at NANTI, received correct instruction, first descent to FL150 later to FL100, at NANTI I was at FL100 - cool!
- Issue 4: After NANTI I was requested to climb to FL150 again - Don't think that makes a lot of sense
- Issue 5: I have tried to request FL100 - I got "cleared to 100feet (!) and climb to FL150" - Ignored it and stayed at FL100
- Later I was instructed to descend to FL70 and later to 3000 with handover to EGGP approach
- Issue 6: At the end of the STAR at WPT TIPOD I didn't received an vectoring calls towards the ILS of RWY27. It only kept telling me to climb to 3000 even after I was established on ILS and also after touch down. No handover to tower.

Full bugreport attached.

Either it is me doing strange things or it is still pretty buggy. In any case I very much appreciate your work!

Christian
You do not have the required permissions to view the files attached to this post.

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

Re: RCs public previews

Post by ntnll » Thu Mar 28, 2019 3:25 pm

argonius wrote:
Wed Mar 27, 2019 7:42 pm
Hi Antonello

Either it is me doing strange things or it is still pretty buggy. In any case I very much appreciate your work!

Christian
Thanks Chris,
all minor bugs, not much concerned about them. With the massive changes I introduced, I expected tons of news bugs, this honestly looks very well. The most complicate things is to reproduce these bugs in order to isolate and fix them. I'll try to make your flight, thanks for your feedback.
124thATC Developer

Othello
Posts: 2
Joined: Mon Feb 04, 2019 6:50 pm

Re: RCs public previews

Post by Othello » Sat Mar 30, 2019 2:03 pm

Hello Antonello,

the bug (keeping 3000ft, no handover to tower, ist very easy to reproduce.

Fly from EDDM to LOWI, a short fly,
insert only one waypoint, TULSI

Transition Level 1500 (EDDM) and 12000 (LOWI)

That's all.

/Günther

Ansgar86
Posts: 1
Joined: Sat Mar 30, 2019 9:28 am

Re: RCs public previews

Post by Ansgar86 » Sat Mar 30, 2019 6:45 pm

report Ansgar86 30.3.2019.7z
Hallo guys,

Just started today playing with the new atc plugin, my first flight with this plugin was starting in muenich (EDDM) to london Heathrow (EGLL)

On the flight i was using following route: as SID : Inpu2Q to INPUD then via y102 to upala via UL610 to Batty via UL 608 to SUMUM and via L608 to LOGAN

After takoff the ATC was leading me via Heading to my first waypoint INPUD ignoring my sid INPU2Q what in my opinion is very sad but as in read here sid and stars are not implemented yet so ok nevermind. While taking off and climbing to INPUD i dont had an handoff to munich departure only an Handoff direct to munich Centre radar. After reaching Inpud the ATC let me fly on own Navigation till 30miles before T/D i got the massage that i have to expect runway 27R to Land in EGLL. 10 Miles before T/D the ATC sends me down from FL 330 to FL 150 so i Decended with 1800 v/s was an easy going
and the ATC was sending me via Heading on the runway course ignoring the Star i had programmed. when i was 60 Miles away from the runnway the ATC send me down from FL 150 to FL 070 this was a little bit short so i had to use a decending rate of 3000 v/s at this moment i was think "Ok this is some kind of steep" when i reached FL 100 the ATC send me down to FL 030 i was maybe 30 MIles infront of the runway by now so i had to go even steeper never had before 4000 v/s i could barly reach the glideslope on runnway 27R in EGLL luckely i hade early enoug decelerated so i managed to Land my Plane.

The decend from FL 330 o FL150 was very good in with an good V/S but then i wass flying over 5 minutes more or les on FL 150 without decending further so i think thats why i got so big trouble to decend to FL 030. Maybe a soulution is when the plugins reads the route direct out of the FMC and alow us to use SID and STARS.

Another problem i found is as soon as i aktivate ATC handles AI Planes (experimental i know) my Xplane crashes emidatly and i can't start my xplane anymore it crash again a soon as i start a flight so i have to delete the plugin and reinstall it again.

Will continue testing and write some reports here.

p.s.maybe its possible to aktivate some yellow arrows like the defauld atc does, because it was a pain into the ass to find gate 224 in EGLL had to tap out and consult my charts i don't owne a second screen and on the sdandart airport xplane use gate 224 dont has a number visible so was very hard to find. so i gave up and Parked anywhere close by.
p.p.s bug report is upstairs on Flightlevel first line
With best regarts
Ansgar
You do not have the required permissions to view the files attached to this post.

earlcw
Posts: 29
Joined: Fri Feb 22, 2019 2:37 pm

Re: RCs public previews

Post by earlcw » Sun Mar 31, 2019 7:35 pm

So far RC27 persists in the bugs I've reported before the LAT LONG 0,0 bug on flights to CYQB and the decend to 0 bug when using SID out of KDCA. Also since installing 27 I'm having crashes at least once every 2 or 3 flights where before on 26 I was stable.

earlcw
Posts: 29
Joined: Fri Feb 22, 2019 2:37 pm

Re: RCs public previews

Post by earlcw » Sun Mar 31, 2019 9:40 pm

Flying back from CYQB to CYOW via star DEANS9 I see via logs the lat long 0,0 was created then replaced by the DEANS9 star waypoints great. However no transfer to ils/tower at the end. Log attached. Using RC27.
You do not have the required permissions to view the files attached to this post.

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

Re: RCs public previews

Post by stewy81 » Tue Apr 02, 2019 6:58 am

bugReport.7z
KMEM to KAUS .........initial altitude 32000 (also cruze altitude) then we start getting descend 0 feet error. Tower to Center handoff, not sure you have the departure frequency modeled yet?

Flight was fine until x plane crashed during ACC file access from 124th atc. not much else to report, was waiting to see how it handled the approach, it had asked me which STAR I was wanting, and had notified me of runway in use, I was in my descent which it persists on asking me to complete. I feel if it can read that I'm descending and it needs me to increase my descent the wording should change to say something like "FDX 5510 please expedite your descent to FL160" instead it keeps repeating Fedex 5510, descend 16000 feet, altimeter 30.27, transition level 180. I"m already going -1800 FPM how much more do they want?

Thanks
You do not have the required permissions to view the files attached to this post.

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

Re: RCs public previews

Post by ntnll » Tue Apr 02, 2019 4:07 pm

Hi Guys,
the new code correcting part of these bugs is ready, but a huge power surge destroyed a couple of days ago my lab and other fancy expansive staff in my apartment, so I can't build the package for now, I'm aiming to release the next version this weekend, as soon I'll back to the normality
124thATC Developer

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

Re: RCs public previews

Post by ntnll » Wed Apr 03, 2019 7:28 am

I was able to compile the code, build 124thATCv2.0-a60RC28 available, fixing 0 ft altitude error and others minor bugs
124thATC Developer

argonius
Posts: 42
Joined: Wed May 30, 2018 2:14 pm

Re: RCs public previews

Post by argonius » Wed Apr 03, 2019 4:41 pm

Hi Antonello,

I have repeated my earlier flight with RC28: IFR from EGLC to EGGP (route: BPK WELIN T420 TNT) with manual STAR/SID selection.
- First of all - no crash (linux user) :)
- I selected RWY27 and SID BPK1A for departure
- Issue 1: I was directly cleared to cruise alt FL200, although the SID has an alt. restraint of 3000feet (same as in RC27)
- No more descend 0 feet with RC28 :)
- Cruise went fine, I selected RWY27 and STAR TIPO2G for arrival
- Issue 2 (NEW) - STAR TIPO2G requires FL100 at NANTI, the instruction to descend from FL150 to FL100 was received AT NANTI, so too late. In RC27 I got the instruction in due time BEFORE NANTI (but was requested to climb again to FL150 after passing NANTI)
- This time I was not requested to climb to FL150 again.
- Later I was instructed to descend to FL70 and later to 3000' .
- Issue 3: At the end of the STAR at WPT TIPOD I didn't received an vectoring calls towards the ILS of RWY27. No handover to tower. (same as in RC27)

Bug report attached, I hope it helps.

BR
Christian
You do not have the required permissions to view the files attached to this post.

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

Re: RCs public previews

Post by ntnll » Wed Apr 03, 2019 5:49 pm

argonius wrote:
Wed Apr 03, 2019 4:41 pm
Hi Antonello,

I have repeated my earlier flight with RC28: IFR from EGLC to EGGP (route: BPK WELIN T420 TNT) with manual STAR/SID selection.
- First of all - no crash (linux user) :)
- I selected RWY27 and SID BPK1A for departure
- Issue 1: I was directly cleared to cruise alt FL200, although the SID has an alt. restraint of 3000feet (same as in RC27)
- No more descend 0 feet with RC28 :)
- Cruise went fine, I selected RWY27 and STAR TIPO2G for arrival
- Issue 2 (NEW) - STAR TIPO2G requires FL100 at NANTI, the instruction to descend from FL150 to FL100 was received AT NANTI, so too late. In RC27 I got the instruction in due time BEFORE NANTI (but was requested to climb again to FL150 after passing NANTI)
- This time I was not requested to climb to FL150 again.
- Later I was instructed to descend to FL70 and later to 3000' .
- Issue 3: At the end of the STAR at WPT TIPOD I didn't received an vectoring calls towards the ILS of RWY27. No handover to tower. (same as in RC27)

Bug report attached, I hope it helps.

BR
Christian
Hi argonius, many thanks for your fast report.

Issue 1: Know issue, working on that
Issue 2: I'll have a look, thanks for report
Issue 3: I can't reproduce this issue, are you using a custom airport?

a.
124thATC Developer

argonius
Posts: 42
Joined: Wed May 30, 2018 2:14 pm

Re: RCs public previews

Post by argonius » Wed Apr 03, 2019 7:11 pm

ntnll wrote:
Wed Apr 03, 2019 5:49 pm
Issue 3: I can't reproduce this issue, are you using a custom airport?
No, standard XP airport. Navigraph data cycle 1904.
(There are reports from other users further above about the same issue of not being vectored to ILS)

/Christian

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

Re: RCs public previews

Post by ntnll » Wed Apr 03, 2019 8:03 pm

argonius wrote:
Wed Apr 03, 2019 7:11 pm
ntnll wrote:
Wed Apr 03, 2019 5:49 pm
Issue 3: I can't reproduce this issue, are you using a custom airport?
No, standard XP airport. Navigraph data cycle 1904.
(There are reports from other users further above about the same issue of not being vectored to ILS)

/Christian
Thanks Christian, bug identified and fixed ; )
124thATC Developer

Post Reply