RCs public previews

Forum dedicated to the alpha, beta, and RC versions
ntnll
Posts: 186
Joined: Sun May 13, 2018 12:32 pm

Re: RCs public previews

Post by ntnll » Sat Jan 12, 2019 10:22 am

JANPIRO wrote:
Sat Jan 12, 2019 10:08 am
Thank you very much.
Everything works perfectly with the RC22 version.
In order to avoid confusion a small suggestion: would it be possible to put the words "Report missed approach" in white letters on a red background.
Image
Hi janpiro,
Not sure to understand what you mean

JANPIRO
Posts: 8
Joined: Sun Jan 06, 2019 8:16 am

Re: RCs public previews

Post by JANPIRO » Sat Jan 12, 2019 11:02 am

Did you see the picture I attached?

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

Re: RCs public previews

Post by ntnll » Sat Jan 12, 2019 11:27 am

JANPIRO wrote:
Sat Jan 12, 2019 11:02 am
Did you see the picture I attached?
sorry I did't see it, I was from mobile. Oh you mean changing the syle... I'll think about it, thanks for your suggestion. Feel free to vote your it on the brainstorming page.

a.

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

Re: RCs public previews

Post by argonius » Sat Jan 12, 2019 6:40 pm

I have just repeated my "famous" flight from EDDS to LSZB with RC22 in XP11.30 final, using the "Import from FMS" feature - No crash, Flawless SID/STAR selection, Flawless transition to arrival runway - Excellent!

Thank you very much for your great work, Antonello!

Regards
Christian

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

Re: RCs public previews

Post by ntnll » Sun Jan 13, 2019 2:13 am

argonius wrote:
Sat Jan 12, 2019 6:40 pm
I have just repeated my "famous" flight from EDDS to LSZB with RC22 in XP11.30 final, using the "Import from FMS" feature - No crash, Flawless SID/STAR selection, Flawless transition to arrival runway - Excellent!

Thank you very much for your great work, Antonello!

Regards
Christian
Good news!
Thank you also guys for contributing to the test phase.
a.

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

Re: RCs public previews

Post by ntnll » Sun Jan 13, 2019 12:46 pm

Hi guys,
not mayor bugs reported by the beta testers on the last build, please if you are still experiencing any bug report in this thread! Many thanks!

a.

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

Re: RCs public previews

Post by ntnll » Mon Jan 14, 2019 7:04 pm

v2.0-a60RC23 available. Addressed a bug preventing correct ATC Dialog menu activation

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

Re: RCs public previews

Post by vittop » Tue Jan 15, 2019 9:47 am

My first test with RC23, XP11.30 demo and IFR KSEA->KBFI, no manual STAR/SID selection. All fine and smooth up to the beginning of last turn before descent. Then had a crash, find as usual zipped logfiles attached
bugReport.tar.gz
(752.63 KiB) Downloaded 6 times

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

Re: RCs public previews

Post by ntnll » Tue Jan 15, 2019 3:13 pm

vittop wrote:
Tue Jan 15, 2019 9:47 am
My first test with RC23, XP11.30 demo and IFR KSEA->KBFI, no manual STAR/SID selection. All fine and smooth up to the beginning of last turn before descent. Then had a crash, find as usual zipped logfiles attached

bugReport.tar.gz
Thanks vittop, I'll have a look

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

Re: RCs public previews

Post by stewy81 » Wed Jan 16, 2019 3:17 am

Hi, testing out RC23 here. Seemed to go pretty well. A few things of notice though. My requested runway and Flight Level were overrode on clearance / delivery. I requested 23L and FL 250 I was given 23R and 199 feet. I then requested 23L and was given it but also at 199 feet initial altitude. (I'm attaching some screen shots and the bug report for all of these.) With previous RC I was getting initial altitudes of 0 ( I should note I think it later asked me to go to FL 199, but I can't be sure, it did start lowering me to FL120, Then FL090 and finally FL040 but the wording and text at the first part seems like only 199 feet not 19900 and why would it use 19900 and not FL190 or FL200 depending on direction.

I made it through all hand offs and had no issues and was handed off to approach no problem. As I was descending through 4000 feet I was vectored away from the runway and towards my missed approach holding point. (This could be my fault as I use little navmap and it always lists the missed approach as well, and I've always wondered if this confuses 124th ATC or how we should format a missed in the plan import etc?)

I followed the vectors and they kept going until I repeated my last 3 waypoints I think, then I landed with no problem getting handed over to tower and ground. I did keep getting asked to maintain 2500 feet a lot of times when I was at 2480-2500 best I could tell.......also this missed shows it should be 3000 on little navmap and on charts I got from AIRNAV online and as well through FMS on the default 737-800 I was flying.

*this one not in the log tried again while writing this post**

I tried again with same flight plan and was given RWY 32 which is what ATIS was saying was active, but this is the cross wind runway and rarely used. I had the wind at calm perfect for using RWY 23L or 23R as it asked the first time. This conflict seems to happen often but I overlook it not knowing if its x plane being off or 124thATC. I will do some more specific testing later such as requesting altitude changes during flight and seeing if ATC stays on previous altitude even thought it approved the change. This was happening in RC21 I think it was.

Thanks again for the great work !
Attachments
3.JPG
3.JPG (38.18 KiB) Viewed 150 times
1.JPG
1.JPG (29.64 KiB) Viewed 150 times
bugReport.7z
(20.66 KiB) Downloaded 5 times

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

Re: RCs public previews

Post by ntnll » Wed Jan 16, 2019 12:06 pm

stewy81 wrote:
Wed Jan 16, 2019 3:17 am
Hi, testing out RC23 here. Seemed to go pretty well. A few things of notice though. My requested runway and Flight Level were overrode on clearance / delivery. I requested 23L and FL 250 I was given 23R and 199 feet. I then requested 23L and was given it but also at 199 feet initial altitude. (I'm attaching some screen shots and the bug report for all of these.) With previous RC I was getting initial altitudes of 0 ( I should note I think it later asked me to go to FL 199, but I can't be sure, it did start lowering me to FL120, Then FL090 and finally FL040 but the wording and text at the first part seems like only 199 feet not 19900 and why would it use 19900 and not FL190 or FL200 depending on direction.

I made it through all hand offs and had no issues and was handed off to approach no problem. As I was descending through 4000 feet I was vectored away from the runway and towards my missed approach holding point. (This could be my fault as I use little navmap and it always lists the missed approach as well, and I've always wondered if this confuses 124th ATC or how we should format a missed in the plan import etc?)

I followed the vectors and they kept going until I repeated my last 3 waypoints I think, then I landed with no problem getting handed over to tower and ground. I did keep getting asked to maintain 2500 feet a lot of times when I was at 2480-2500 best I could tell.......also this missed shows it should be 3000 on little navmap and on charts I got from AIRNAV online and as well through FMS on the default 737-800 I was flying.

*this one not in the log tried again while writing this post**

I tried again with same flight plan and was given RWY 32 which is what ATIS was saying was active, but this is the cross wind runway and rarely used. I had the wind at calm perfect for using RWY 23L or 23R as it asked the first time. This conflict seems to happen often but I overlook it not knowing if its x plane being off or 124thATC. I will do some more specific testing later such as requesting altitude changes during flight and seeing if ATC stays on previous altitude even thought it approved the change. This was happening in RC21 I think it was.

Thanks again for the great work !

Thanks stewy81 for your feedback. I already corrected the bug of "199 feet initial", I'll replicate anyway your flight later and check for your notes.

a.

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

Re: RCs public previews

Post by vittop » Fri Jan 18, 2019 12:22 pm

ntnll wrote:
Tue Jan 15, 2019 3:13 pm
vittop wrote:
Tue Jan 15, 2019 9:47 am
My first test with RC23, XP11.30 demo and IFR KSEA->KBFI, no manual STAR/SID selection. All fine and smooth up to the beginning of last turn before descent. Then had a crash, find as usual zipped logfiles attached

bugReport.tar.gz
Thanks vittop, I'll have a look
Just purchased XP11, installed on a new HD with Ubuntu 16.04.5 kernel 4.15.0.43 , upgraded XP to last 11.30 rel and tested RC23 KCLM->KOLM IFR no manaul S/S selection. All fine and smooth right to landing, this time. Will repeat with it KSEA-KBFI asap to check if problem was on my demo installation (was on Mint 18.3 kernel 4.15.0.20) or whatever else, and come back here if the above error appears.

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

Re: RCs public previews

Post by ntnll » Fri Jan 18, 2019 5:04 pm

vittop wrote:
Fri Jan 18, 2019 12:22 pm
ntnll wrote:
Tue Jan 15, 2019 3:13 pm
vittop wrote:
Tue Jan 15, 2019 9:47 am
My first test with RC23, XP11.30 demo and IFR KSEA->KBFI, no manual STAR/SID selection. All fine and smooth up to the beginning of last turn before descent. Then had a crash, find as usual zipped logfiles attached

bugReport.tar.gz
Thanks vittop, I'll have a look
Just purchased XP11, installed on a new HD with Ubuntu 16.04.5 kernel 4.15.0.43 , upgraded XP to last 11.30 rel and tested RC23 KCLM->KOLM IFR no manaul S/S selection. All fine and smooth right to landing, this time. Will repeat with it KSEA-KBFI asap to check if problem was on my demo installation (was on Mint 18.3 kernel 4.15.0.20) or whatever else, and come back here if the above error appears.
Thanks vittop for your feedbacks. Actually I identified a couple of bugs on approach phase that can be the cause of your crashes. I'll release next build in the next days.

Antonello

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

Re: RCs public previews

Post by vittop » Fri Jan 18, 2019 7:00 pm

ntnll wrote:
Fri Jan 18, 2019 5:04 pm
vittop wrote:
Fri Jan 18, 2019 12:22 pm
ntnll wrote:
Tue Jan 15, 2019 3:13 pm


Thanks vittop, I'll have a look
Just purchased XP11, installed on a new HD with Ubuntu 16.04.5 kernel 4.15.0.43 , upgraded XP to last 11.30 rel and tested RC23 KCLM->KOLM IFR no manaul S/S selection. All fine and smooth right to landing, this time. Will repeat with it KSEA-KBFI asap to check if problem was on my demo installation (was on Mint 18.3 kernel 4.15.0.20) or whatever else, and come back here if the above error appears.
Thanks vittop for your feedbacks. Actually I identified a couple of bugs on approach phase that can be the cause of your crashes. I'll release next build in the next days.

Antonello
Still trouble with this KSEA-KBFI route, this time at TO I had my 172's GPS map indicating only the last leg and not a full plan. Anyhow, just passed the mid-way waypoint, Approach op ignored me about the route I was supposed to follow, only warning me about FL changes if any instead telling me to turn back and begin the approach. As usual, find here the logfile:
bugReport.tar.gz
(96.29 KiB) Downloaded 7 times

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

Re: RCs public previews

Post by RandomUser » Sun Jan 20, 2019 10:00 pm

Just got a hard application crash in 11.30r3 with a23. The log doesn't specify the plugin that crashed, but since the last logged action was reading the acc.dat, I'm posting this here as it could be related to the latest alpha.

My crash position was at N 51° 36' 53.24", E 9° 20' 20.83", around 10 nm away from WRB on a 52° radial (in case it could be a center handoff bug).
Attachments
bugReport.7z
(22.24 KiB) Downloaded 2 times

Post Reply