benjoglove wrote:

mach2000 wrote:

I had the same issue yesterday on a flight out of KIAH. The winds were out of the south (190/8 if I remember correctly), the ATIS advertised runway 15L in use and all the AI traffic appeared to be going to 15L; but when I called ground, I was told to taxi to runway 33R

The zipped logs are attached. I also had issues when contacting ground at my destination (KLBB)... I never heard any taxi instructions from ground; but the pilot read back instructions as if they had been issued.

Mach2000 so you had AI traffic talking to ATC (PF3) before requesting clearance and got Rwy different to AI. I only get it when I havent waited for the AI to fire up and then I get in que and they give me the same runway as AI.

I have posted another topic re the ground issue and PF3 dying once landed. I dont even get pilot read back so thats interesting. Maybe post that section in my other post so we keep it seperate? Here is the link to the post viewtopic.php?f=8&t=1936

benjoglove wrote:

benjoglove wrote:

mach2000 wrote:

I had the same issue yesterday on a flight out of KIAH. The winds were out of the south (190/8 if I remember correctly), the ATIS advertised runway 15L in use and all the AI traffic appeared to be going to 15L; but when I called ground, I was told to taxi to runway 33R

The zipped logs are attached. I also had issues when contacting ground at my destination (KLBB)... I never heard any taxi instructions from ground; but the pilot read back instructions as if they had been issued.

Mach2000 so you had AI traffic talking to ATC (PF3) before requesting clearance and got Rwy different to AI. I only get it when I havent waited for the AI to fire up and then I get in que and they give me the same runway as AI.

I have posted another topic re the ground issue and PF3 dying once landed. I dont even get pilot read back so thats interesting. Maybe post that section in my other post so we keep it seperate? Here is the link to the post viewtopic.php?f=8&t=1936

Can someone please please have a good look re the ground atc issue. This is interesting that its been raised by someone else and not just me with a sightly different result. This issue is really bugging after a good flight and pf3 dies for a better word. Is it a bug or a setting issue?

dmarch wrote:

Well I've just check through your logs and really can't see any problem. You made contact with Ground control and receive taxi instructions. Or am I missing the point?

3/15/2016 8:29:59 PM: 750 - Transcript: 'Acey 4054 exit Left next available taxiway Contact Ground on 121.9 when clear of the active  '
3/15/2016 8:30:13 PM: 850 - Transcript: 'Acey 4054 Good day  '
3/15/2016 8:30:43 PM: 590 - Transcript: 'Ground Acey 4054 Clear of the active runway  '
3/15/2016 8:30:49 PM: 620 - Transcript: 'Acey 4054 hold your position  '
3/15/2016 8:31:03 PM: 640 - Transcript: 'Acey 4054 Good day  '
3/15/2016 8:31:12 PM: 600 - Transcript: 'Roger. Taxi to parking number 22 using taxiway November   Mike   Sierra    '

Quote:

Well I've just check through your logs and really can't see any problem. You made contact with Ground control and receive taxi instructions. Or am I missing the point?

dmarch wrote:

Well at that precise moment I can assure you PF3 detected an AI aircraft using 33R. We don't actually look to see where an aircraft is or which way it is facing, we simply use the AI data table provided by FSUIPC and this shows the actual runway assigned to each aircraft. When PF3 first checked (when you selected ATIS) 15L was detected.

I can't explain why this should happen, all we can do is use the information available to us at the time

ThomasAH wrote:

I guess the second "Good day" indicates the problem here: "hold your position" does not need a Roger/Readback (similar to "stand by"), and the extra Roger seems to have confused PF3.

mach2000 wrote:

ThomasAH wrote:

I guess the second "Good day" indicates the problem here: "hold your position" does not need a Roger/Readback (similar to "stand by"), and the extra Roger seems to have confused PF3.

As Thomas pointed out - no taxi instructions were given, just the readback.

If the "Roger" to the "hold your position" instruction is the cause - that probably needs to be looked at. Why would ProATC not expect a reply? If it's a control instruction, it deserves a readback. Even in situations where a readback is not warranted, an inadvertent press of the "roger" key shouldn't cause ATC to go mute.

I also see the "roger/readback" function being problematic in other areas of the program. ATC occasionally has a tendency to rattle off two or three messages in a row before allowing the reply to be played. Then the "roger" key needs to be pressed multiple times to clear out the "backlog".

mach2000 wrote:

If the "Roger" to the "hold your position" instruction is the cause - that probably needs to be looked at. Why would ProATC not expect a reply? If it's a control instruction, it deserves a readback. Even in situations where a readback is not warranted, an inadvertent press of the "roger" key shouldn't cause ATC to go mute.

I also see the "roger/readback" function being problematic in other areas of the program. ATC occasionally has a tendency to rattle off two or three messages in a row before allowing the reply to be played. Then the "roger" key needs to be pressed multiple times to clear out the "backlog".

benjoglove wrote:

Reading the manual could this have something to do with it?
Pause Mode - this determines the distance from either the FAF, runway or
your destination airport you would like to pause FS/PF3.