OnCourse Software

Today I witnessed a strange bug I have not encountered yet.

I was told to contact Seattle center several times even though I already was on the same frequency and every time I had a new voice. This happened several times and yes, I followed the instructions since every "new" center was the same frequency.

What happened there, can anyone help me, please?

Thanks in advance

Strangely enough I had the same thing happen to me last week and I forgot to save the log... so thanks for your log and I'll take a look to see what I can find.

I might have another log. I say might because on that flight I couldn't hear ATC's transmissions (PF3 seemingly didn't take well to me restarting it), but I could hear my FO's (MCE) responses, and at one point he started to repeatedly contact a facility, always on the same frequency. I then took over ATC and ended the flight without ATC. Anyway, let me know if you're interested.

Well, this might be a major issue, how has no one ever reported that before?

CapatinAlex wrote:

Well, this might be a major issue, how has no one ever reported that before?

Before you get carried away, this most certainly is not a major issue! A major issue is a problem experienced by all users and one that stops the program functioning completely. This is neither.

My current theory is it's caused by a series of events... one of which, as in your particular case, is following a request to go 'direct to'

dtsakiris wrote:

I might have another log. I say might because on that flight I couldn't hear ATC's transmissions (PF3 seemingly didn't take well to me restarting it), but I could hear my FO's (MCE) responses, and at one point he started to repeatedly contact a facility, always on the same frequency. I then took over ATC and ended the flight without ATC. Anyway, let me know if you're interested.

This sounds like a different issue and one related to 'restarting' PF3. Feel free to post about the problem, if you have the log, but do so in a separate post please.

dmarch wrote: *

Mon Nov 07, 2022 10:02 pm

CapatinAlex wrote:

Well, this might be a major issue, how has no one ever reported that before?

Before you get carried away, this most certainly is not a major issue! A major issue is a problem experienced by all users and one that stops the program functioning completely. This is neither.

My current theory is it's caused by a series of events... one of which, as in your particular case, is following a request to go 'direct to'

Okay, but you are working on finding a solution, right? Because not requesting a direct ever again is not a solution

Quote:

Because not requesting a direct ever again is not a solution

Is that what I suggested?

dmarch wrote: *

Tue Nov 08, 2022 10:53 am

Quote:

Because not requesting a direct ever again is not a solution

Is that what I suggested?

No, but it sounded like it, sorry

dmarch wrote: *

Mon Nov 07, 2022 10:02 pm

CapatinAlex wrote:

Well, this might be a major issue, how has no one ever reported that before?

Before you get carried away, this most certainly is not a major issue! A major issue is a problem experienced by all users and one that stops the program functioning completely. This is neither.

My current theory is it's caused by a series of events... one of which, as in your particular case, is following a request to go 'direct to'

Have you found any solution yet, please?