Page 34 of 48

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

Posted: Wed Jul 10, 2019 2:26 am
by earlcw
ntnll wrote:
Sun Jul 07, 2019 11:31 am
earlcw wrote:
Thu Jul 04, 2019 3:31 am
Ah 38 seems to have gained back a bug I haven't seen in ages. The injection of lat 0, long 0 +/- waypoints. Flight plan was CYYB ODKOB DASUG MEBSI YSP DUPUL CYQT with a star at CYQT NOTER1 and landing at runway 07.
Hi earlcw,
unable to reproduce the issue. And actually your FlightPlan.kml doesn't show 0 lat/lon in google Earth. I'm unable to find it either in your log. Can you elaborate please?
Checked the log I uploaded and I see the lat/long 0/0 injection happen near the end during star assignment up to this point ATC was fine then this kicked in.

124thATC v2.0-a60RC38 20:32:17: Entering FMS Programming (processing 10 fixes)
124thATC v2.0-a60RC38 20:32:17: FMS cleared, entries now: 0
124thATC v2.0-a60RC38 20:32:17: FMS Content start
124thATC v2.0-a60RC38 20:32:17: FMS fix 1/12: CYYB
124thATC v2.0-a60RC38 20:32:17: FMS fix 2/12: ODKOB
124thATC v2.0-a60RC38 20:32:17: FMS fix 3/12: DASUG
124thATC v2.0-a60RC38 20:32:17: FMS fix 4/12: MEBSI
124thATC v2.0-a60RC38 20:32:17: FMS fix 5/12: YSP
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
124thATC v2.0-a60RC38 20:32:17: FMS fix 12/12: CYQT
124thATC v2.0-a60RC38 20:32:17: FMS Content stop

EDDM problem fixed ?

Posted: Fri Jul 12, 2019 4:57 pm
by BerlinFlyer56
Hello,

may be that I have fixed the problem with EDDM. Actual I use the x-plane version 35b4. There is in the apt file an airport named Klippenek and ICAO coded XEDDM. First the airport has no ICAO code (to small) and second, every airport in the world is ICAO coded with four characters.

So I think that 124thATC was confused which airport to use.

I send this information as a bug report to Laminar Research because this field (gliderfield) is also an included scenery, which I could not change.

Lets hope that that the reason was.

With regards

Olaf

Airport name correction

Posted: Fri Jul 12, 2019 5:03 pm
by BerlinFlyer56
The airportname is Klippeneck - sorry.

Olaf

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

Posted: Sun Jul 14, 2019 5:45 pm
by SHaneD
i had a problem with "38" today, I was flying from LFBO to EGSS, 124thATC v2.0-a60RC38 picked the wrong intersection when looking for D335W, instead of picking the closest (332' @ 26.6 Nm) it chose one 268Nm away (almost on the same heading 331') with the same name 23.4 Nm north of LFRS, to carry on with the flight I just chose the next waypoint, the flight completed with no other problems. Not had this problem in a while.

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

Posted: Sun Jul 14, 2019 10:48 pm
by RandomUser
Just had a great flight from EFHK to EDDV with RC38 and Zibo's 737 v3.35.7.
The only minor bug encountered was ATC making me pick a STAR very early on after departure. But that's okay as I could re-choose my STAR later on.
And 124th did have a bit of trouble with the CEL27 STAR for EDDV (landing runway 27R), but I can't blame it as it has a really weird zig-zag style routing.

Anyway, here's the bug report in case you want to investigate.

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

Posted: Mon Jul 15, 2019 6:49 am
by sg72
crashed while inserting flight plan

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

Posted: Mon Jul 15, 2019 11:28 am
by ntnll
Thanks a lot guys for all the feedback, I'll test all of them in order to spot any remaining bug.

a.

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

Posted: Mon Jul 15, 2019 7:10 pm
by ntnll
earlcw wrote:
Wed Jul 10, 2019 2:26 am
ntnll wrote:
Sun Jul 07, 2019 11:31 am
earlcw wrote:
Thu Jul 04, 2019 3:31 am
Ah 38 seems to have gained back a bug I haven't seen in ages. The injection of lat 0, long 0 +/- waypoints. Flight plan was CYYB ODKOB DASUG MEBSI YSP DUPUL CYQT with a star at CYQT NOTER1 and landing at runway 07.
Hi earlcw,
unable to reproduce the issue. And actually your FlightPlan.kml doesn't show 0 lat/lon in google Earth. I'm unable to find it either in your log. Can you elaborate please?
Checked the log I uploaded and I see the lat/long 0/0 injection happen near the end during star assignment up to this point ATC was fine then this kicked in.

124thATC v2.0-a60RC38 20:32:17: Entering FMS Programming (processing 10 fixes)
124thATC v2.0-a60RC38 20:32:17: FMS cleared, entries now: 0
124thATC v2.0-a60RC38 20:32:17: FMS Content start
124thATC v2.0-a60RC38 20:32:17: FMS fix 1/12: CYYB
124thATC v2.0-a60RC38 20:32:17: FMS fix 2/12: ODKOB
124thATC v2.0-a60RC38 20:32:17: FMS fix 3/12: DASUG
124thATC v2.0-a60RC38 20:32:17: FMS fix 4/12: MEBSI
124thATC v2.0-a60RC38 20:32:17: FMS fix 5/12: YSP
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
124thATC v2.0-a60RC38 20:32:17: FMS fix 12/12: CYQT
124thATC v2.0-a60RC38 20:32:17: FMS Content stop
That doesn't look the lat/lon 0,0 injection, rather the FMS name description for approach and ILS points. Those fixes are not real fixes, so they can't be named in FMS, thus they are called 0,0 from the XPlane SDK.

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

Posted: Tue Jul 16, 2019 1:43 am
by earlcw
ntnll wrote:
Mon Jul 15, 2019 7:10 pm
earlcw wrote:
Wed Jul 10, 2019 2:26 am
ntnll wrote:
Sun Jul 07, 2019 11:31 am


Hi earlcw,
unable to reproduce the issue. And actually your FlightPlan.kml doesn't show 0 lat/lon in google Earth. I'm unable to find it either in your log. Can you elaborate please?
Checked the log I uploaded and I see the lat/long 0/0 injection happen near the end during star assignment up to this point ATC was fine then this kicked in.

124thATC v2.0-a60RC38 20:32:17: Entering FMS Programming (processing 10 fixes)
124thATC v2.0-a60RC38 20:32:17: FMS cleared, entries now: 0
124thATC v2.0-a60RC38 20:32:17: FMS Content start
124thATC v2.0-a60RC38 20:32:17: FMS fix 1/12: CYYB
124thATC v2.0-a60RC38 20:32:17: FMS fix 2/12: ODKOB
124thATC v2.0-a60RC38 20:32:17: FMS fix 3/12: DASUG
124thATC v2.0-a60RC38 20:32:17: FMS fix 4/12: MEBSI
124thATC v2.0-a60RC38 20:32:17: FMS fix 5/12: YSP
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
124thATC v2.0-a60RC38 20:32:17: FMS fix 12/12: CYQT
124thATC v2.0-a60RC38 20:32:17: FMS Content stop
That doesn't look the lat/lon 0,0 injection, rather the FMS name description for approach and ILS points. Those fixes are not real fixes, so they can't be named in FMS, thus they are called 0,0 from the XPlane SDK.
Why I refer to it as injection is because just before ATC asks which STAR to use the fixes in the log are

124thATC v2.0-a60RC38 20:32:17: Entering FMS Programming (processing 5 fixes)
124thATC v2.0-a60RC38 20:32:17: FMS cleared, entries now: 0
124thATC v2.0-a60RC38 20:32:17: FMS Content start
124thATC v2.0-a60RC38 20:32:17: FMS fix 1/7: CYYB
124thATC v2.0-a60RC38 20:32:17: FMS fix 2/7: ODKOB
124thATC v2.0-a60RC38 20:32:17: FMS fix 3/7: DASUG
124thATC v2.0-a60RC38 20:32:17: FMS fix 4/7: MEBSI
124thATC v2.0-a60RC38 20:32:17: FMS fix 5/7: YSP
124thATC v2.0-a60RC38 20:32:17: FMS fix 6/7: DUPUL
124thATC v2.0-a60RC38 20:32:17: FMS fix 7/7: CYQT
124thATC v2.0-a60RC38 20:32:17: FMS Content stop

The upon selecting the star there are the 10 fixes. The jump to waypoint list becomes scrambled with the landing waypoints not at the end as usual. As for these being unnamed points 'labels' unfortunately the fms is reprogrammed a route to the north atlantic and back.

Why I think this is a bug is because it doesn't always happen when I fly the same flight plan the problem doesn't appear. It appears randomly. Used to appear randomly once every couple of flights now vary rare.

Using airnac cycle 1907.

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

Posted: Wed Jul 17, 2019 3:15 pm
by ntnll
earlcw wrote:
Tue Jul 16, 2019 1:43 am

Why I refer to it as injection is because just before ATC asks which STAR to use the fixes in the log are
Hi earlcw,
I double checked, you'll definitely right. Not the same 0/0 lat/lon bug, but definitely a bug, I'll try to replicate the issue on my computer.
Thanks for reporting.

a.

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

Posted: Fri Jul 19, 2019 2:42 pm
by ntnll
a60RC39 uploaded. Fixed the prematurely ILS approach generation on change departure runway, causing lat/lon 0/0. Minor bugs fixed.
Please report any issue with the window dialog.

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

Posted: Fri Jul 19, 2019 9:51 pm
by ruetzi
Just tested the RC38 and found that now also the flight plan can be given after the start. It is certainly intended that then no change in flight altitude is possible. At this point, only "Top of descent reached" is output.

greeting
ruetzi

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

Posted: Fri Jul 19, 2019 9:58 pm
by ruetzi
An oversight. This is the bug report after closing X-Plane.

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

Posted: Sat Jul 20, 2019 6:15 pm
by oncleseb
Hi gentlemen
Just end a test flight MIAMI - TAMPA : lovely ! (ATC124 RC39 / XP11.34)
thanks Antonello
Sebastien

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

Posted: Sun Jul 21, 2019 2:05 am
by earlcw
Thanks for rc39 none of that 0/0 lat/long oddness yet but I did hit one I've had before. Kept forgetting to report because it isn't major but it is a decent bounce while flying a particular star, and yes it is reproducible. CYWG GOTAG DEGVA YHD YSP MEBSI DASUG NAGNO BEMOG CYOW with the star LEAMY4 (AIRAC 1908) I get the following decent instructions:

124thATC v2.0-a60RC39 20:12:40: Communication: 16000 feet, amelia 8009.
124thATC v2.0-a60RC39 20:12:55: Communication: amelia 8009, descend to 13000 feet
124thATC v2.0-a60RC39 20:13:00: Communication: 13000 feet, amelia 8009.
124thATC v2.0-a60RC39 20:16:13: Communication: amelia 8009, descend to 8000 feet
124thATC v2.0-a60RC39 20:16:21: Communication: 8000 feet, amelia 8009.
124thATC v2.0-a60RC39 20:17:08: Communication: amelia 8009, climb to 13000 feet
124thATC v2.0-a60RC39 20:17:13: Communication: climb to 13000 feet, amelia 8009.
124thATC v2.0-a60RC39 20:18:23: Communication: amelia 8009, descend to 3300 feet
124thATC v2.0-a60RC39 20:18:28: Communication: 3300 feet, amelia 8009.

As you see I get the 16,000 to 13,000 to 8,000 then back to 13,000 with a drop to 3,300 after.