Release Candidate (RC) Version - Download and Feedback

Forum dedicated to the alpha, beta, and RC versions
RandomUser
Posts: 71
Joined: Fri Aug 31, 2018 10:15 pm

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

Post by RandomUser » Fri Aug 02, 2019 8:26 pm

h0use wrote:
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:
See the very first item on the brainstorming page here: https://www.tricider.com/brainstorming/2TApRulUj9x

WT3 integration very much depends on its developer, who has scheduled more possibilities for interaction wwith AI aircraft data for version 3.3.

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

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

Post by ntnll » Fri Aug 02, 2019 9:47 pm

vittop wrote:
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
Hi vittop, are you in LNAV? When on LNAV, the plugin won't vector while on cruise phase
Last edited by ntnll on Sat Aug 03, 2019 12:54 am, edited 3 times in total.
124thATC Developer

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

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

Post by ntnll » Fri Aug 02, 2019 9:59 pm

h0use wrote:
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:
Hi h0use,
thank you very much. The problem is that I'm doing "great things" for free, and the spare time is not much. Even so, I spend a lot of hours on it. I honestly can't speculate, but VR and WT support are definitely in the todo list. As soon the next version will be released, I'll probably start looking at the new features requirements, and I'll have better chances to make some consideration about the future path of the plugin.

There is a dedicated thread here, I'll post there relevant info about the WT integration :)

Antonello
124thATC Developer

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

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

Post by vittop » Sat Aug 03, 2019 7:11 am

ntnll wrote:
Fri Aug 02, 2019 9:47 pm
vittop wrote:
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
Hi vittop, are you in LNAV? When on LNAV, the plugin won't vector while on cruise phase
I was on the Laminar Beech 58, autopilot set to HDG to follow ATC instruction. I switched to NAV as I relized that FANZI was passed without any indication to turn toward next wpt (Btw, this is the same situation like my previous tests when I was in Washington state, flying from KPAE to KCLM via SEA ULESS ARRIE, but in this case, I eventually found on SkyVector a route to follow without this issue). I seldom use NAV mod, I usually set HDG mode after takeoff until, with APPR mode triggered, I intercept the ILS.
[Using XP11.36|Ubuntu 16.04\Mint 18.3|Kernel 4.15.0-60|amdgpu opensource driver]

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

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

Post by ntnll » Sat Aug 03, 2019 11:15 am

vittop wrote:
Sat Aug 03, 2019 7:11 am
ntnll wrote:
Fri Aug 02, 2019 9:47 pm
vittop wrote:
Fri Aug 02, 2019 10:55 am


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
Hi vittop, are you in LNAV? When on LNAV, the plugin won't vector while on cruise phase
I was on the Laminar Beech 58, autopilot set to HDG to follow ATC instruction. I switched to NAV as I relized that FANZI was passed without any indication to turn toward next wpt (Btw, this is the same situation like my previous tests when I was in Washington state, flying from KPAE to KCLM via SEA ULESS ARRIE, but in this case, I eventually found on SkyVector a route to follow without this issue). I seldom use NAV mod, I usually set HDG mode after takeoff until, with APPR mode triggered, I intercept the ILS.
On NAV, the plugin expect you being on autopilot, and won't bore you with heading correction calls. Except for approximation and departure phases.
124thATC Developer

jkeye
Posts: 17
Joined: Tue May 22, 2018 5:48 pm

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

Post by jkeye » Sun Aug 04, 2019 11:55 am

What about STARS during approaches? when does the plugin take over if you are flying a STAR programmed into FMC?

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

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

Post by vittop » Sun Aug 04, 2019 4:57 pm

ntnll wrote:
Sat Aug 03, 2019 11:15 am
vittop wrote:
Sat Aug 03, 2019 7:11 am
ntnll wrote:
Fri Aug 02, 2019 9:47 pm


Hi vittop, are you in LNAV? When on LNAV, the plugin won't vector while on cruise phase
I was on the Laminar Beech 58, autopilot set to HDG to follow ATC instruction. I switched to NAV as I relized that FANZI was passed without any indication to turn toward next wpt (Btw, this is the same situation like my previous tests when I was in Washington state, flying from KPAE to KCLM via SEA ULESS ARRIE ELWHA, but in this case, I eventually found on SkyVector a route to follow without this issue). I seldom use NAV mod, I usually set HDG mode after takeoff until, with APPR mode triggered, I intercept the ILS.
On NAV, the plugin expect you being on autopilot, and won't bore you with heading correction calls. Except for approximation and departure phases.
Wow, I believe this is the ultimate answer to all my doubts: I tried KPAE->KCLM without engaging a/p at all, and all wpts were taken into account. Thanks for clarifying.
Last edited by vittop on Mon Aug 05, 2019 8:13 am, edited 1 time in total.
[Using XP11.36|Ubuntu 16.04\Mint 18.3|Kernel 4.15.0-60|amdgpu opensource driver]

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

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

Post by h0use » Mon Aug 05, 2019 2:35 am

ntnll wrote:
Fri Aug 02, 2019 9:59 pm
h0use wrote:
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:
Hi h0use,
thank you very much. The problem is that I'm doing "great things" for free, and the spare time is not much.
Yeah, I understand that, anyway, I quite enjoy with latest build, only one thing still a bit annoying is transition altitude, most of Australian airport have initial altitude FL50/60, but plugin always says FL100.

Another problem is importing plan from Zibo FMS, it always return something like "+100-32" instead of real route.

I think big benefit would be in integration with Simbrief api, you can download all flight parameters from there by one button click even before Battery On

Thank you again for your work.

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

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

Post by ntnll » Mon Aug 05, 2019 8:40 am

jkeye wrote:
Sun Aug 04, 2019 11:55 am
What about STARS during approaches? when does the plugin take over if you are flying a STAR programmed into FMC?
Not sure to understand the question jkeye
h0use wrote:
Mon Aug 05, 2019 2:35 am
ntnll wrote:
Fri Aug 02, 2019 9:59 pm
h0use wrote:
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:
Hi h0use,
thank you very much. The problem is that I'm doing "great things" for free, and the spare time is not much.
Yeah, I understand that, anyway, I quite enjoy with latest build, only one thing still a bit annoying is transition altitude, most of Australian airport have initial altitude FL50/60, but plugin always says FL100.

Another problem is importing plan from Zibo FMS, it always return something like "+100-32" instead of real route.

I think big benefit would be in integration with Simbrief api, you can download all flight parameters from there by one button click even before Battery On

Thank you again for your work.
Hi h0use,
the initial altitude, when no SID restriction available, uses to be random, and not always FL100. Are you sure the FL100 is not a restriction coming from the SID?

I don't use zibo FMC, I'll try to test it and see where is the issue, thanks for report it
124thATC Developer

Rafalec
Posts: 16
Joined: Mon May 14, 2018 5:52 pm

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

Post by Rafalec » Mon Aug 05, 2019 1:23 pm

ntnll wrote:
Mon Aug 05, 2019 8:40 am
jkeye wrote:
Sun Aug 04, 2019 11:55 am
What about STARS during approaches? when does the plugin take over if you are flying a STAR programmed into FMC?
Not sure to understand the question jkeye
h0use wrote:
Mon Aug 05, 2019 2:35 am
ntnll wrote:
Fri Aug 02, 2019 9:59 pm


Hi h0use,
thank you very much. The problem is that I'm doing "great things" for free, and the spare time is not much.
Yeah, I understand that, anyway, I quite enjoy with latest build, only one thing still a bit annoying is transition altitude, most of Australian airport have initial altitude FL50/60, but plugin always says FL100.

Another problem is importing plan from Zibo FMS, it always return something like "+100-32" instead of real route.

I think big benefit would be in integration with Simbrief api, you can download all flight parameters from there by one button click even before Battery On

Thank you again for your work.
Hi h0use,
the initial altitude, when no SID restriction available, uses to be random, and not always FL100. Are you sure the FL100 is not a restriction coming from the SID?

I don't use zibo FMC, I'll try to test it and see where is the issue, thanks for report it
yes please, correct this problem, zibo is a must have!

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

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

Post by RandomUser » Mon Aug 05, 2019 8:21 pm

The problem is that the FMC logic of Zibo's 737-800X isn't accessible from the outside, which makes easy importing into 124th next to impossible.

What's so hard about typing a sequence of waypoints into the flight plan field anyway?

Using Onlineflightplanner, there is an "airways" field that contains all relevant airways and crossing waypoints, e.g.:
EDDV SID WRB UN850 KRH T715 PABLA Y163 HERBI Y164 OLBEN UN869 MILPA UN852 PIVUS UZ237 SISMO UN855 KENAS STAR LEPA

So in 124th ATC, you'd type:
WRB KRH PABLA HERBI OLBEN MILPA PIVUS SISMO KENAS

And that's your flight plan broken down to the most relevant waypoints from the SID to the STAR.

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

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

Post by ntnll » Mon Aug 05, 2019 8:38 pm

RandomUser wrote:
Mon Aug 05, 2019 8:21 pm
The problem is that the FMC logic of Zibo's 737-800X isn't accessible from the outside, which makes easy importing into 124th next to impossible.

What's so hard about typing a sequence of waypoints into the flight plan field anyway?

Using Onlineflightplanner, there is an "airways" field that contains all relevant airways and crossing waypoints, e.g.:
EDDV SID WRB UN850 KRH T715 PABLA Y163 HERBI Y164 OLBEN UN869 MILPA UN852 PIVUS UZ237 SISMO UN855 KENAS STAR LEPA

So in 124th ATC, you'd type:
WRB KRH PABLA HERBI OLBEN MILPA PIVUS SISMO KENAS

And that's your flight plan broken down to the most relevant waypoints from the SID to the STAR.
Thanks RandomUser for your contribute, I honestly don't know Zibo FMC.
Guys remember you can just edit the LastFlighPlan.txt and easily paste the flight plan there. Then, open the flight plan dialog and file it.
ntnll wrote:
Mon Aug 05, 2019 8:40 am
Hi h0use,
the initial altitude, when no SID restriction available, uses to be random, and not always FL100. Are you sure the FL100 is not a restriction coming from the SID?
I correct myself, I found a bug that can prevents the correct SID restriction recognition in some scenarios, fixed in the next build
Last edited by ntnll on Mon Aug 05, 2019 10:30 pm, edited 1 time in total.
124thATC Developer

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

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

Post by ntnll » Mon Aug 05, 2019 8:59 pm

v2.0-a60RC41 uploaded

- Fixed JumpToWaypoint dialog not destroyed on plugin reset
- Fixed missing altitude correction calls when vertical speed != 0
- SID function bug preventing the correct restriction detection in some scenarios, fixed
- minor fixes and improvements
124thATC Developer

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

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

Post by h0use » Tue Aug 06, 2019 2:41 am

RandomUser wrote:
Mon Aug 05, 2019 8:21 pm
And that's your flight plan broken down to the most relevant waypoints from the SID to the STAR.
Yeah, that's what I doing every time, didn't notice about unaccessible FMC. I think integration with most popular flight planners like https://www.simbrief.com/api/demo.php will be very useful, most of them have good API to get all flight plan details.
Also, ATC could support standard .fmc files which contains full flight profile with all transition levels, so ATC control will better follow plane FMC.

Example of my recent flight in X-Plane format, all what ATC need is already exists.

Code: Select all

I
1100 Version
CYCLE 1908
ADEP YSSY
ADES YBBN
NUMENR 8
1 YSSY ADEP 21.000000 -33.946111 151.177222
11 MATLA DRCT 30300.000000 -32.754889 151.531861
11 SORTI DRCT 35000.000000 -31.820961 151.879169
11 LOSKU H133 35000.000000 -30.492456 152.359203
11 VEGAH H133 35000.000000 -29.410000 152.823333
11 GAMBL H133 30900.000000 -28.874578 153.047969
11 BLAKA H66 16700.000000 -28.200000 153.221667
1 YBBN ADES 2500.000000 -27.384167 153.117500
Anyway, great job, very keen on this ATC solution.

jkeye
Posts: 17
Joined: Tue May 22, 2018 5:48 pm

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

Post by jkeye » Tue Aug 06, 2019 9:14 am

ntnll wrote:
Mon Aug 05, 2019 8:40 am
jkeye wrote:
Sun Aug 04, 2019 11:55 am
What about STARS during approaches? when does the plugin take over if you are flying a STAR programmed into FMC?
Not sure to understand the question jkeye

I was asking whether vectors are only provided by the plugin if one is flying manually.

Post Reply