Release Candidate (RC) Version - Download and Feedback

[Andi111882]

There seems to be something with the radio frequencies.
e.g. EDDH Tower:
X-Plane Freq.: 126.855
12th ATC Freq.: 126.850

v2 RC73

[ntnll]

There seems to be something with the radio frequencies.
e.g. EDDH Tower:
X-Plane Freq.: 126.855
12th ATC Freq.: 126.850

v2 RC73

Hi Andi111882, all good on my default scenario. The frequency is correctly tuned, and the x-plane frequency on default scenario is .850, not .855


How do you get that frequency? Are you using a custom airport? Did you see my previous post about custom airports? Maybe it applies also to your case. Please also remember to upload the log, without it I can't help.

a.

[vittop]

Good morning all,
In 2.0-a60RC73 I pulled back the new Makefile building pipeline that in the past has been pushed back because causing instability. Please report any crash issue.
I'm aiming to release this weekend, if no further macro bugs will identified.

Cheers,
a.

Tried RC73 a couple of time with a brief IFR from Vagar EKVG to Kirkwall EGPA. All fine, only issue is that I put in my flight plan NL NDB (Nolso, some mile from Vagar), which appeared in Skyvector. Plugin included instead NLK (Nordliskampen, near Oslo more than 500 miles away. I guess because on standard XP11 scenario I verified that NL NDB is missing and nearest possible waypoint beginning with "NL" was actually NLK. So all clear. This situation had anyhow a payback, since I was able to test the plugin function to skip a waypoint, which worked perfectly. Well done, mate!

[ntnll]

Good morning all,
In 2.0-a60RC73 I pulled back the new Makefile building pipeline that in the past has been pushed back because causing instability. Please report any crash issue.
I'm aiming to release this weekend, if no further macro bugs will identified.

Cheers,
a.

Tried RC73 a couple of time with a brief IFR from Vagar EKVG to Kirkwall EGPA. All fine, only issue is that I put in my flight plan NL NDB (Nolso, some mile from Vagar), which appeared in Skyvector. Plugin included instead NLK (Nordliskampen, near Oslo more than 500 miles away. I guess because on standard XP11 scenario I verified that NL NDB is missing and nearest possible waypoint beginning with "NL" was actually NLK. So all clear. This situation had anyhow a payback, since I was able to test the plugin function to skip a waypoint, which worked perfectly. Well done, mate!

Thank a lot vittop!
Can you please provide a log of this flight, or at least, the flight plan?

cheers,
a.

[vittop]

Good morning all,
In 2.0-a60RC73 I pulled back the new Makefile building pipeline that in the past has been pushed back because causing instability. Please report any crash issue.
I'm aiming to release this weekend, if no further macro bugs will identified.

Cheers,
a.

Tried RC73 a couple of time with a brief IFR from Vagar EKVG to Kirkwall EGPA. All fine, only issue is that I put in my flight plan NL NDB (Nolso, some mile from Vagar), which appeared in Skyvector. Plugin included instead NLK (Nordliskampen, near Oslo more than 500 miles away. I guess because on standard XP11 scenario I verified that NL NDB is missing and nearest possible waypoint beginning with "NL" was actually NLK. So all clear. This situation had anyhow a payback, since I was able to test the plugin function to skip a waypoint, which worked perfectly. Well done, mate!

Thank a lot vittop!
Can you please provide a log of this flight, or at least, the flight plan?

cheers,
a.

Unfortunately I afterwards tested a plane so logfile is gone, but since I did not even use the plugin for what was a simple test flight around the airport, flight plan for mentioned flight did survive. Please find them in the attached zip file.

Thanks

FlightPlanVagar2Kirkwall.zip

UPDATE!!!UPDATE!!! I was able to repeat the flight on my demo installation, sceneries are missing but who cares? Please find the full debug with the related search for missing "NL" NDB and the discovery of "NLK" VOR instead. Thanks

bugReport.tar.gz

[ruetzi]

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.

I wrote this after the attempted approach on RW 08 from LOWI. I didn't need to generate own waypoints. They were all contained in the approach RNAV WI750, which Little NavMap showed me. And after entering these individual waypoints into the 124thATC flight plan line and deactivating the SID and STAR selection, the plugin took me well down through the valley areas.
Well, except for the very last section, where I was passed a bit too high to the tower.
The runway was then too short!

Greeting
ruetzi

[Andi111882]

There seems to be something with the radio frequencies.
e.g. EDDH Tower:
X-Plane Freq.: 126.855
12th ATC Freq.: 126.850

v2 RC73

Hi Andi111882, all good on my default scenario. The frequency is correctly tuned, and the x-plane frequency on default scenario is .850, not .855


How do you get that frequency? Are you using a custom airport? Did you see my previous post about custom airports? Maybe it applies also to your case. Please also remember to upload the log, without it I can't help.

a.

You're right. I checked my installation and indeed I have a custom version of EDDH. It's the latest Gateway version https://gateway.x-plane.com/scenery/page/EDDH

That means the plugin does not use the requencies specified in the apt.dat files of any add-on airport?
I attached the bugReport.7z and the apt.dat of the add-on airport.

Edit:
The plugin seems to search for the airport in the X-Plane 11\Custom Scenery\Global Airports\Earth nav data\apt.dat file. This data could easily be out of date. X-Plane uses this data only if no custom scenery with the required apt.dat is available.
I double checked the requencies with RL charts (see attachment) and the tower frequency of the Gateway version is correct. The frequency of the default apt.dat is incorrect or out of date.

Code: Select all

124thATC v2.0-a60RC73 13:38:21: -------------------------- Parser started!!! --------------------------
124thATC v2.0-a60RC73 13:38:21: File opened: C:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Scenery\Global Airports\Earth nav data\apt.dat
124thATC v2.0-a60RC73 13:38:21: found 'EDDH'
124thATC v2.0-a60RC73 13:38:21: Runway found: '5' '05' lat'53.618233' lon'9.963711' heading 50.21
124thATC v2.0-a60RC73 13:38:21: Runway found: '23' '23' lat'53.636909' lon'10.001511' heading 230.21
124thATC v2.0-a60RC73 13:38:21: Runway length: 1.7509 magnetic variation: -2.70
124thATC v2.0-a60RC73 13:38:21: Runway found: '15' '15' lat'53.654411' lon'9.975212' heading 152.89
124thATC v2.0-a60RC73 13:38:21: Runway found: '33' '33' lat'53.625107' lon'10.000507' heading 332.89
124thATC v2.0-a60RC73 13:38:21: Runway length: 1.9752 magnetic variation: -2.70
124thATC v2.0-a60RC73 13:38:21: atisFrequency found: '123125', parsed in 123125.000000
124thATC v2.0-a60RC73 13:38:21: groundFrequency found: '121800', parsed in 121800.000000
124thATC v2.0-a60RC73 13:38:21: towerFrequency found: '126850', parsed in 126850.000000
124thATC v2.0-a60RC73 13:38:21: approachFrequency found: '118200', parsed in 118200.000000
124thATC v2.0-a60RC73 13:38:21: departureFrequency found: '134250', parsed in 134250.000000
124thATC v2.0-a60RC73 13:38:21: tower frequency on leaving: '126850.000000'
124thATC v2.0-a60RC73 13:38:21: total parkings found: 30
124thATC v2.0-a60RC73 13:38:21: -------------------------- Parser ended!!! --------------------------

[ntnll]

There seems to be something with the radio frequencies.
e.g. EDDH Tower:
X-Plane Freq.: 126.855
12th ATC Freq.: 126.850

v2 RC73

Hi Andi111882, all good on my default scenario. The frequency is correctly tuned, and the x-plane frequency on default scenario is .850, not .855


How do you get that frequency? Are you using a custom airport? Did you see my previous post about custom airports? Maybe it applies also to your case. Please also remember to upload the log, without it I can't help.

a.

You're right. I checked my installation and indeed I have a custom version of EDDH. It's the latest Gateway version https://gateway.x-plane.com/scenery/page/EDDH

That means the plugin does not use the requencies specified in the apt.dat files of any add-on airport?
I attached the bugReport.7z and the apt.dat of the add-on airport.

Edit:
The plugin seems to search for the airport in the X-Plane 11\Custom Scenery\Global Airports\Earth nav data\apt.dat file. This data could easily be out of date. X-Plane uses this data only if no custom scenery with the required apt.dat is available.
I double checked the requencies with RL charts (see attachment) and the tower frequency of the Gateway version is correct. The frequency of the default apt.dat is incorrect or out of date.

Code: Select all

124thATC v2.0-a60RC73 13:38:21: -------------------------- Parser started!!! --------------------------
124thATC v2.0-a60RC73 13:38:21: File opened: C:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Scenery\Global Airports\Earth nav data\apt.dat
124thATC v2.0-a60RC73 13:38:21: found 'EDDH'
124thATC v2.0-a60RC73 13:38:21: Runway found: '5' '05' lat'53.618233' lon'9.963711' heading 50.21
124thATC v2.0-a60RC73 13:38:21: Runway found: '23' '23' lat'53.636909' lon'10.001511' heading 230.21
124thATC v2.0-a60RC73 13:38:21: Runway length: 1.7509 magnetic variation: -2.70
124thATC v2.0-a60RC73 13:38:21: Runway found: '15' '15' lat'53.654411' lon'9.975212' heading 152.89
124thATC v2.0-a60RC73 13:38:21: Runway found: '33' '33' lat'53.625107' lon'10.000507' heading 332.89
124thATC v2.0-a60RC73 13:38:21: Runway length: 1.9752 magnetic variation: -2.70
124thATC v2.0-a60RC73 13:38:21: atisFrequency found: '123125', parsed in 123125.000000
124thATC v2.0-a60RC73 13:38:21: groundFrequency found: '121800', parsed in 121800.000000
124thATC v2.0-a60RC73 13:38:21: towerFrequency found: '126850', parsed in 126850.000000
124thATC v2.0-a60RC73 13:38:21: approachFrequency found: '118200', parsed in 118200.000000
124thATC v2.0-a60RC73 13:38:21: departureFrequency found: '134250', parsed in 134250.000000
124thATC v2.0-a60RC73 13:38:21: tower frequency on leaving: '126850.000000'
124thATC v2.0-a60RC73 13:38:21: total parkings found: 30
124thATC v2.0-a60RC73 13:38:21: -------------------------- Parser ended!!! --------------------------

Hi Andi111882, thanks. I'll make some tests ASAP.
Meanhiwle I would like to ask, regardless being the frequency incorrect, is the plugin functionality compromised? I mean, is the frequency selector working, and the dialog opening when tuned on the (incorrect) frequency?

[Andi111882]

Hi Andi111882, thanks. I'll make some tests ASAP.
Meanhiwle I would like to ask, regardless being the frequency incorrect, is the plugin functionality compromised? I mean, is the frequency selector working, and the dialog opening when tuned on the (incorrect) frequency?

Despite of the wrong frequencies everything worked well. I dialed in the freqency as the plugin advised and it worked as it should.

[ntnll]

Hi Andi111882, thanks. I'll make some tests ASAP.
Meanhiwle I would like to ask, regardless being the frequency incorrect, is the plugin functionality compromised? I mean, is the frequency selector working, and the dialog opening when tuned on the (incorrect) frequency?

Despite of the wrong frequencies everything worked well. I dialed in the freqency as the plugin advised and it worked as it should.

Thanks for the feedback Andy

[Andi111882]

Thanks for the feedback Andy

Thanks for devloping this great plugin

[vittop]

I had a strange crash while testing a freeware plane around St.Catalina island with RC74. The crash occurred after a plugin reset and the following new filing of the same flight plan I had took off with, i.e. KAVX->KAVX, but changing it from IFR to VFR. The reason why I reset the plugin was just this change from IFR to VFR: a detail, the plane I was testing, Nord 1101 Ramier from Restauravia, has no transponder so I was unable to squawk the code. Therefore I reset the plugin in an attempt to see if so doing I could bypass the step, but I had a crash. Please find the debug archive as usual attached. Thanks

bugReport.tar.gz

[luisrdm1]

I was doing a flight last night where the ATC have chosen the wrong runway, based on winds, so I've landed with tail wind. The aerodrome had ILS on both runways, so it shouldn't be a factor. I could have changed the runway based on the ATIS, but I decided to verify if the conditions had rapidly changed or something.

Regards

[Mr_Smith]

Hello there,

just wanted to give a very brief feedback based on my first impression:

Wonderful! Much better than the default ATC.
Keep up the good work!
Thanks for making this.

Greetings

[Mr_Smith]

Hello there,

here comes my detailed feedback.

• option to have more than 3 rows in ATC communication box

Weather Report: Sometimes it is hard to tell which number belongs to the wind direction and which to the wind speed. Therefore it would be very cool to have an

• option to report wind- direction & speed with a separator inbetween
o “Wind 230 at 15 knots”

Pressing “m” brings up the map in X-Plane. Unfortunately there is no option to
show a propper airport chart. Therefore it would be a big help to

• create one of these yellow arrows pointing to the parking position, if possible

• do not show “hand over to” warning until corresponding ATC voice message has been fully read

In GA aircraft with analog instruments it is sometimes visually impossible to set a precise heading.
Therefore it would be a nice little feature to have an

• option to show indicator of selected heading (autopilot)

• possibility to readback
o “continue your approach”
o “contact tower on…”

• It should not be possible to readback when already on the next frequency.

• interaction box should have same width as frequency box
• interaction box should snap to frequency box if next to it

• if ATC voice is female, readback voice should be male and vice versa

• option to request Altimeter (before take off)

• auto-mute COM as long as 124 ATC is talking

This would allow to still have traffic going on without having two overlapping ATC voices.

I would be glad if you could make use of some of my ideas
in order to further improve this amazing little plugin.

Best Wishes!