Release Candidate (RC) Version - Download and Feedback

Forum dedicated to the alpha, beta, and RC versions
oncleseb
Posts: 9
Joined: Sat Apr 27, 2019 4:04 pm

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

Post by oncleseb » Sun Jul 21, 2019 7:04 am

Hi
Issue when leaving KTPA : 124th has located me on FL45 (helipad !)
Here is bur report file.
RC39 / XP 11.34 / TBM Hotstart
Thx
Sebastien
You do not have the required permissions to view the files attached to this post.

RandomUser
Posts: 63
Joined: Fri Aug 31, 2018 10:15 pm

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

Post by RandomUser » Mon Jul 22, 2019 12:31 am

Roundtrip flight EDDV - LGKR with the Zibo modded 737-800X v. 3.35.12 on XP11.35b6.

No major bugs except descent clearance to 8000ft on the STAR and approach (ELNA5P and ILS27LZ with SAS transition) coming a bit late. I had to ignore ATC and start down on my own.
Since ATC seems to have general difficulties with exotic approaches (RNAV, ILS with transitions, NDB, etc.), I again suggest a "do not vector me" function to be selected during handover to approach. ATC would then simply clear you for the final approach altitude (with a few stages in between, if need be) and hand you over to the tower near the final approach fix.

Bug report attached for completeness.

By the way: Why do I always get transponder codes starting with "2"? Is this a bug or some real world thing?

Other than that, the plugin really seems to be in a releasable state. Good work, Antonello.
You do not have the required permissions to view the files attached to this post.

ruetzi
Posts: 9
Joined: Wed Jul 17, 2019 9:44 am

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

Post by ruetzi » Mon Jul 22, 2019 9:38 pm

124thATC v2.0-a60RC38 20:32:17: FMS fix 6/12: DUPUL
124thATC v2.0-a60RC38 20:32:17: FMS fix 7/12: -0 -0
124thATC v2.0-a60RC38 20:32:17: FMS fix 8/12: -0 -0
124thATC v2.0-a60RC38 20:32:17: FMS fix 9/12: -0 -0
124thATC v2.0-a60RC38 20:32:17: FMS fix 10/12: -0 +0
124thATC v2.0-a60RC38 20:32:17: FMS fix 11/12: +0 +0
Hi earlcw,
are there possibly two waypoints with the name DUPUL with different coordinates entered in your "airnac cycle 1907"? In my "airnac cycle 1708" there is only one waypoint DUPUL with a coordinate further northwest of your flight plan.
However, the waypoint DUPUL is available twice with different coordinates when searching in "https://skyvector.com/".

Greeting
ruetzi

ruetzi
Posts: 9
Joined: Wed Jul 17, 2019 9:44 am

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

Post by ruetzi » Wed Jul 24, 2019 4:05 pm

Hi,
many complain about mountainous regions with 124thATC.
So I think about something difficult.
Twin Otter from VNKT via KIMTI to VNLK FL150 (Kathmandu - Lukla). The real weather is currently blind flying weather. Flight plan abandoned, SID IGRI1A for RW20 selected and harmoniously in the FMS registered. Initial Altitude 7000, later FL150.
On the way on request reduced to FL130. RW 06 is expected for Lukla.
From the log.txt I have the impression that the runway was selected only after the distance to the plane and not because it is to be used exclusively for landing.
Then follows the instruction FL 128. Guidance on HDG 51 direction VNLK. On the last section I changed the blind weather to visual flight conditions. There is no other way in Lukla. Landing clearance for visual flight.

Except for one note on the type of runway selection for this particular airfield - even in these weather conditions - a safely guided flight.
For this the bugreport.

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

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

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

Post by earlcw » Thu Jul 25, 2019 2:35 pm

ruetzi wrote:
Mon Jul 22, 2019 9:38 pm
124thATC v2.0-a60RC38 20:32:17: FMS fix 6/12: DUPUL
124thATC v2.0-a60RC38 20:32:17: FMS fix 7/12: -0 -0
124thATC v2.0-a60RC38 20:32:17: FMS fix 8/12: -0 -0
124thATC v2.0-a60RC38 20:32:17: FMS fix 9/12: -0 -0
124thATC v2.0-a60RC38 20:32:17: FMS fix 10/12: -0 +0
124thATC v2.0-a60RC38 20:32:17: FMS fix 11/12: +0 +0
Hi earlcw,
are there possibly two waypoints with the name DUPUL with different coordinates entered in your "airnac cycle 1907"? In my "airnac cycle 1708" there is only one waypoint DUPUL with a coordinate further northwest of your flight plan.
However, the waypoint DUPUL is available twice with different coordinates when searching in "https://skyvector.com/".

Greeting
ruetzi
I've wondered if there was something about the waypoints that triggered the problem but the problem doesn't always happen. The problem tends to happen at certain airports and never other airports. The constant however has always been the 0/0 happens after choosing the star. However so far 39 has worked flawlessly in regards to this bug.

macgarvin
Posts: 3
Joined: Fri Oct 19, 2018 12:03 am

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

Post by macgarvin » Sun Jul 28, 2019 12:40 pm

Hi

With RC build a60RC39, x-plane 11.24rc1, and MacOS Mojave 10.14.5

I invariably get a 124thATC notification of a STAR and runway, but ATC then follows through with generic 'approximation' points to land, rather than via the notified STAR.

This happens with all of the following permutations leaving from EGPE (Inverness, no SIDs) to EGPF (Glasgow) or EGPH (Edinburgh), both which have a few simple STARS. I have tried 1) adding the STAR and APPROACH to the the FMS flightplan (but not in the 124thATC flightplan) before takeoff, or in flight, 2) letting 124thATC add the arrival points to the FMS flightplan, when declared by 124thATC, without my adding a STAR and APPROACH, 3) including the fix for the STAR as the last fix I add to the flight plan, and 4) making my last point before the airport some distance short of any STAR. For both permutations 3) and 4) this was without allowing 124thATC add points to the FMS flight plan.


Is this because I have 1) incorrectly set up the navigation folder contents in the 124thATC plugin folder (its a simple copy of all contents from x-planes Custom Data folder, excluding the GNS430 sub-folder), 2) its a bug in 124thATC, or 3) it is an expected feature for these airports?

I've attached the compressed files requested, plus the expected route for STAR and APPROACH for the current Navigraph cycle, plus a screenshot of the expanded directory structure for the 124thATC plugin folder (I've provided these as a zip file as I'm getting a 'you do not have sufficient permissions', within Terminal when I attempt to use 'generateBugReport_MAC.command' - which is strange because I have successfully done this in the past - however, one problem at a time!

Happy to provide more information, do more experimentation if helpful.

Cheers, Malcolm

ps - I can't upload the file, getting a 'Sorry, the board attachment quota has been reached' error message. Here is what looks like a relevant part of the x-plane Log.txt files

124thATC v2.0-a60RC39 21:44:08: apt parser: found: 'EGPF'
124thATC v2.0-a60RC39 21:44:08: apt parser: Runway found: '5' '05' lat'55.863480' lon'-4.449060' heading 46.36
124thATC v2.0-a60RC39 21:44:08: apt parser: Runway found: '23' '23' lat'55.879974' lon'-4.418236' heading 226.36
124thATC v2.0-a60RC39 21:44:08: apt parser: Runway length: 1.4341 magnetic variation: 2.45
124thATC v2.0-a60RC39 21:44:08: apt parser: atisFrequency found: '12957', parsed in 12957.000000
124thATC v2.0-a60RC39 21:44:08: apt parser: groundFrequency found: '12170', parsed in 12170.000000
124thATC v2.0-a60RC39 21:44:08: apt parser: towerFrequency found: '11880', parsed in 11880.000000
124thATC v2.0-a60RC39 21:44:08: apt parser: approachFrequency found: '11910', parsed in 11910.000000
124thATC v2.0-a60RC39 21:44:08: apt parser: tower frequency on leaving: '11880.000000'
124thATC v2.0-a60RC39 21:44:08: apt parser: total parkings found: 30
124thATC v2.0-a60RC39 21:44:08: -------------------------- Parser ended!!! --------------------------
124thATC v2.0-a60RC39 21:44:08: Set matching arrival runway... (CheckNavigation::generateILS==1)
124thATC v2.0-a60RC39 21:44:08: Set matching runway...
124thATC v2.0-a60RC39 21:44:08: Take targetAirport object
124thATC v2.0-a60RC39 21:44:08: Runway lookup arrival: )
124thATC v2.0-a60RC39 21:44:08: Runway found 0/2: 05 (isDeparture: 0)
124thATC v2.0-a60RC39 21:44:08: Runway found 1/2: 23 (isDeparture: 0)
124thATC v2.0-a60RC39 21:44:08: Get wind data...
124thATC v2.0-a60RC39 21:44:08: An existing waypoint is active...
124thATC v2.0-a60RC39 21:44:08: Take actual waypoint INBAS as reference
124thATC v2.0-a60RC39 21:44:08: Reference point: Lat 56.700001 Lon: -4.249722
124thATC v2.0-a60RC39 21:44:08: No airport flows found, wind less than 10 knots (7 knots). Get runway by location...
124thATC v2.0-a60RC39 21:44:08: Check runway distance...
124thATC v2.0-a60RC39 21:44:08: Runway 05 distance = 50.63
124thATC v2.0-a60RC39 21:44:08: Runway has NO ILS
124thATC v2.0-a60RC39 21:44:08: Check runway distance...
124thATC v2.0-a60RC39 21:44:08: Runway 23 distance = 49.52
124thATC v2.0-a60RC39 21:44:08: Runway has NO ILS
124thATC v2.0-a60RC39 21:44:08: Nearest runway is 23 distance = 49.52
124thATC v2.0-a60RC39 21:44:08: Take runway 23.
124thATC v2.0-a60RC39 21:44:08: Set runway information...
124thATC v2.0-a60RC39 21:44:08: Airport found to set runway height: EGPF (pilot Cirrus @MOD@, Glasgow).
124thATC v2.0-a60RC39 21:44:08: Height of Runway: 21.000690.
124thATC v2.0-a60RC39 21:44:08: Runway information set!
124thATC v2.0-a60RC39 21:44:09: Flight plan status for Cirrus @MOD@ (size 3): 40VOR.100 (0) (2) DAVOT.100 (0) (2) INBAS.100 (0) (2)
124thATC v2.0-a60RC39 21:44:09: star GOW1A randomly chosen for runway 23, 4 of 13 available
124thATC v2.0-a60RC39 21:44:09: Entering FMS Programming (processing 3 fixes)
124thATC v2.0-a60RC39 21:44:09: FMS cleared, entries now: 0
124thATC v2.0-a60RC39 21:44:09: FMS Content start
124thATC v2.0-a60RC39 21:44:09: FMS fix 1/5: EGPE
124thATC v2.0-a60RC39 21:44:09: FMS fix 2/5: 40VOR
124thATC v2.0-a60RC39 21:44:09: FMS fix 3/5: DAVOT
124thATC v2.0-a60RC39 21:44:09: FMS fix 4/5: INBAS
124thATC v2.0-a60RC39 21:44:09: FMS fix 5/5: EGPF
124thATC v2.0-a60RC39 21:44:09: FMS Content stop
124thATC v2.0-a60RC39 21:44:09: Call SetILSPath.
124thATC v2.0-a60RC39 21:44:09: SetILSPath Enter
124thATC v2.0-a60RC39 21:44:09: DEBUG: SetILSPath - using last fix point as entry point
124thATC v2.0-a60RC39 21:44:09: SetILSPath - Set path from an entry of: Lat 56.700001 Lon -4.249722
124thATC v2.0-a60RC39 21:44:09: Flight plan status for Cirrus @MOD@ (size 3): 40VOR.100 (0) (2) DAVOT.100 (0) (2) INBAS.100 (0) (2)
124thATC v2.0-a60RC39 21:44:09: SetILSPath - SetILSPath GetDistance to: 23.
124thATC v2.0-a60RC39 21:44:09: SetILSPath Downwind 46
124thATC v2.0-a60RC39 21:44:09: Rwy Lat 55.879974 Lon -4.418236
124thATC v2.0-a60RC39 21:44:09: SetILSPath ILS entered: Lat 56.017993 Lon -4.159803
124thATC v2.0-a60RC39 21:44:09: Flight plan status for Cirrus @MOD@ (size 3): 40VOR.100 (0) (2) DAVOT.100 (0) (2) INBAS.100 (0) (2)
124thATC v2.0-a60RC39 21:44:09: Adding Approximation phase to FP...
124thATC v2.0-a60RC39 21:44:09: AddToFlightPlan - Adding Approximation 1 - 56.360714 -4.171751
124thATC v2.0-a60RC39 21:44:09: AddToFlightPlan - Adding Approximation 2 - 56.247643 -4.007538
124thATC v2.0-a60RC39 21:44:09: AddToFlightPlan - Adding ILS - 56.017994 -4.159803
124thATC v2.0-a60RC39 21:44:09: Flight plan status for Cirrus @MOD@ (size 6): 40VOR.100 (0) (2) DAVOT.100 (0) (2) INBAS.100 (0) (2) Approximation 1.0 (0) (4) Approximation 2.0 (0) (4) ILS.0 (0) (5)
124thATC v2.0-a60RC39 21:44:09: AddToFlightPlan - Adding Runway 23 - 55.879974 -4.418236
124thATC v2.0-a60RC39 21:44:09: Flight plan status for Cirrus @MOD@ (size 7): 40VOR.100 (0) (2) DAVOT.100 (0) (2) INBAS.100 (0) (2) Approximation 1.0 (0) (4) Approximation 2.0 (0) (4) ILS.0 (0) (5) Runway 23.0 (0) (6)
124thATC v2.0-a60RC39 21:44:09: Entering FMS Programming (processing 7 fixes)
124thATC v2.0-a60RC39 21:44:09: FMS cleared, entries now: 0
124thATC v2.0-a60RC39 21:44:09: FMS Content start
124thATC v2.0-a60RC39 21:44:09: FMS fix 1/5: EGPE
124thATC v2.0-a60RC39 21:44:09: FMS fix 2/5: 40VOR
124thATC v2.0-a60RC39 21:44:09: FMS fix 3/5: DAVOT
124thATC v2.0-a60RC39 21:44:09: FMS fix 4/5: INBAS
124thATC v2.0-a60RC39 21:44:09: FMS fix 5/5: EGPF
124thATC v2.0-a60RC39 21:44:09: FMS Content stop
124thATC v2.0-a60RC39 21:44:09: Flight plan status for Cirrus @MOD@ (size 7): 40VOR.100 (0) (2) DAVOT.100 (0) (2) INBAS.100 (0) (2) Approximation 1.100 (0) (4) Approximation 2.100 (0) (4) ILS.100 (0) (5) Runway 23.30 (0) (6)
124thATC v2.0-a60RC39 21:44:09: ILS Path set to RWY 23.
124thATC v2.0-a60RC39 21:44:30: DEBUG: Checking obstacles...
124thATC v2.0-a60RC39 21:44:50: ACC lookup: reading acc.dat file /Volumes/Pegasus/X-Plane/Resources/plugins/124thATC64/acc.dat, plane Cirrus @MOD@, airport EGPE

h0use
Posts: 6
Joined: Fri Jul 05, 2019 9:46 am

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

Post by h0use » Mon Jul 29, 2019 5:31 am

Have the flight with latest alpha from YMML to YSSY, if departure and cruise was fine, but approach was not good, plugin decided to land me on runaway 7 (which is mostly for GA and regional planes), but when I chose option to manually select (correct should be 16L/16R) menu showed me only one "Auto" button without any other options. I used default YSSY airport, seems ATC can't read properly all available runaways.

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

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

Post by ntnll » Wed Jul 31, 2019 9:48 pm

Thanks so much all for your feedback. I can't reply to everybody, but I read all your messages.

2.0-a60RC40 uploaded:

- fixed a bug introduced in 2.0-a60RC39 preventing the correct arrival runway parsing on change runway request dialog.
- introduced a new option for disable the approximation fixes generation "Do not create approximation fixes"
124thATC Developer

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

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

Post by ntnll » Wed Jul 31, 2019 9:48 pm

Thanks so much all for your feedback. I can't reply to everybody, but I read all your messages.

2.0-a60RC40 uploaded:

- fixed a bug introduced in 2.0-a60RC39 preventing the correct arrival runway parsing on change runway request dialog.
- introduced a new option for disable the approximation fixes generation "Do not create approximation fixes"
124thATC Developer

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

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

Post by vittop » Thu Aug 01, 2019 4:04 pm

ntnll wrote:
Wed Jul 31, 2019 9:48 pm
Thanks so much all for your feedback. I can't reply to everybody, but I read all your messages.

2.0-a60RC40 uploaded:

- fixed a bug introduced in 2.0-a60RC39 preventing the correct arrival runway parsing on change runway request dialog.
- introduced a new option for disable the approximation fixes generation "Do not create approximation fixes"
Hi, I tested this new RC40.

First of all, this version .sh script to generate the bugReport.tar.gz only picks up Commands.txt and DataRefs.txt, so I added the missing .txt and .kml files manually, I hope are all inside. Now, the flight, a VOR to VOR route suggested by SkyVector from KHAE to KMKE via UIN PIA BDF RFD BAE. As often happens to me, after being correctly told by plugin to turn after UIN, once passed PIA I had no turning instruction anymore from plugin. All other instructions (i.e handoffs to app and then twr and then gnd, altitude changes, QNH) are ok but no turning instruction at all, I had to set a/p to NAV for horizontal control (to follow next VOR up to BAE) and then to HDG again, adjusting it to approximately intercept ILS. bugReport included
bugReport.tar.gz
You do not have the required permissions to view the files attached to this post.

ruetzi
Posts: 9
Joined: Wed Jul 17, 2019 9:44 am

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

Post by ruetzi » Thu Aug 01, 2019 6:56 pm

It's my fault. This surely happened when the wrong mail address in the bat file was changed that I pointed out to Antonello.

Greeting
ruetzi

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

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

Post by ntnll » Thu Aug 01, 2019 10:18 pm

124thATCv2.0-a60RC40 repacked with the correct bug report scripts, thanks for report it!

Please note that the bugReport folder has been moved from:

\Resources\plugins\124thATC64\64\bugReport < ------------ delete this folder if still exists in the plugin structure

to:

\Resources\plugins\124thATC64\bugReport


a.
Last edited by ntnll on Fri Aug 02, 2019 10:26 am, edited 4 times in total.
124thATC Developer

macgarvin
Posts: 3
Joined: Fri Oct 19, 2018 12:03 am

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

Post by macgarvin » Thu Aug 01, 2019 11:59 pm

Thanks ntnil, I've downloaded RC40 and will see if that fixes my problem

h0use
Posts: 6
Joined: Fri Jul 05, 2019 9:46 am

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

Post by h0use » Fri Aug 02, 2019 7:44 am

ntnil,are you going to collaborate with WT3 guys? You both doing great things and as result of your collaboration could be breathtaken :roll:

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

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

Post by vittop » Fri Aug 02, 2019 10:55 am

ntnll wrote:
Thu Aug 01, 2019 10:18 pm
124thATCv2.0-a60RC40 repacked with the correct bug report scripts, thanks for report it!

Please note that the bugReport folder has been moved from:

\Resources\plugins\124thATC64\64\bugReport < ------------ delete this folder if still exists in the plugin structure

to:

\Resources\plugins\124thATC64\bugReport


a.
bugReport creation seems ok now, please find then another one attached: tried flight from Milwaukee,WI to Gary,IN, with the two wpts recommended by SkyVectors: TALOR NILES. After takeoff I was instructed to turn 222 and then 233 to reach first wpt choosen according with selected departure but after this, once passed wpt (FANZI, the selected departure is strangely Z-shaped!), no turn indication anymore, as often happens to me.
bugReport.tar.gz
You do not have the required permissions to view the files attached to this post.

Post Reply