Does anyone else have trouble responding to traffic alerts? 

 

No matter what I do, when ATC warns me of traffic I can't seem to get a reaction when reporting traffic in sight or don't have the traffic, etc.

I don't think I have ever heard Radar Contact V4 ATC reply to a "Traffic in sight" " Don't have the traffic".

 

I doubt its modelled.

 

Perhaps the guys at RC would know exactly.

 

However, you could do a Vox Script that would emulate an ATC reply. You could script "Traffic insight"/"Don't have the traffic" and record a sound clip from a live ATC or make one up yourself, that would play as a response. I know its a bit faux, but it would add a response. Only you would know its a Vox Script. ^_^

 

regards

 

David

Does anyone else have trouble responding to traffic alerts? 

 

No matter what I do, when ATC warns me of traffic I can't seem to get a reaction when reporting traffic in sight or don't have the traffic, etc.

 

If it's Native FSX (FS9) or Prepar3D ATC, the command is supported.

 

What exact phraseology are you using? Please don't check the manual. Want to see if what you speak naturally is good canddate for addition to native ATC speech grammar. Thx

Default reply in RC is simply 'Roger.' (default key '7'). Maybe RC devs tried to get around telling a "traffic in sight" scenario from a "looking out for traffic" case.

RC (and ATC r/l)  will report traffic, bearing (clock values) and distance. But this is a traffic "advisory".  e.g. "caution traffic, a B17  1 o clock at two miles".

 

Its up to you, the pilot in command, to react to what ATC has given you. Whatever you reply is also advisory, in that ATC has been advised, by you, that you have seen the traffic or not. After that there is no further interaction with ATC, unless you have not seen the traffic and continue to fly on the same heading and altitude, in which case ATC will repeat the advisory.

 

Once you take avoiding action ATC (and RC) sees this and assumes all is now OK.

 

Your TCAS (if you have one) is the other weapon in your armoury to avoid a disaster. :blush:

 

Is this what the op was asking? 

 

Cheers

 

David

RC (and ATC r/l)  will report traffic, bearing (clock values) and distance. But this is a traffic "advisory".  e.g. "caution traffic, a B17  1 o clock at two miles".

 

Its up to you, the pilot in command, to react to what ATC has given you. Whatever you reply is also advisory, in that ATC has been advised, by you, that you have seen the traffic or not. After that there is no further interaction with ATC, unless you have not seen the traffic and continue to fly on the same heading and altitude, in which case ATC will repeat the advisory.

 

Once you take avoiding action ATC (and RC) sees this and assumes all is now OK.

 

Your TCAS (if you have one) is the other weapon in your armoury to avoid a disaster. :blush:

 

Is this what the op was asking? 

 

Cheers

 

David

 

My problem is that I get no response after I report 'traffic in sight'.  The ATC window still shows the options for reporting.  So to clkear it I have to choose option 2 and it reports and clears the ATC responses.

If you take a look at the below video.
 
At 7.40 and 8.30, RC4 ATC issues traffic advisories. I just reply with " Roger...Warrior 399".
 
If you use the latest MCE with the F/O or F/E working the radios then he/she will automatically reply to RC4 "Have the traffic" ( or something similar)  and the message will be accepted. This is even better since it gives you the sense that your F/O actually is looking outside for you! B)

Hope this helps.

Cheers
David

 

 

My problem is that I get no response after I report 'traffic in sight'

 

I assume we are talking native FS ATC here.

 

What complete verbiage are you using?

 

MCE will only select the relevant option in ATC menu when it is aware of the available options at any given time.

 

Next time this happens, and provided you spoke the correct message and it was displayed in red font, temporarily switch FO voice to a TTS voice, as recorded voice packs cannot handle reading unexpected text.

 

With a TTS voice as your FO, ask him/her "confirm ATC options" or "what are the ATC options". If the TTS voice is unable to read the content of the ATC window, report it as a bug with as much information as possible, notably...

 

Aicraft flown.

Area flown (Flight plan??)

I assume we are talking native FS ATC here.

 

What complete verbiage are you using?

 

MCE will only select the relevant option in ATC menu when it is aware of the available options at any given time.

 

Next time this happens, and provided you spoke the correct message and it was displayed in red font, temporarily switch FO voice to a TTS voice, as recorded voice packs cannot handle reading unexpected text.

 

With a TTS voice as your FO, ask him/her "confirm ATC options" or "what are the ATC options". If the TTS voice is unable to read the content of the ATC window, report it as a bug with as much information as possible, notably...

 

Aicraft flown.

Area flown (Flight plan??)

I usually fly a mooney bravo with no first officer.  I simply use MCE for a more relalistic communication with ATC.  I commony fly Hawaii and souterhn Florida 9Approach to West Paml beach).

 

I will try turnig on the FO and see what his verbage is to ATC to confirm aircraft in sight, but I beleive it is what is usually typed on the screen from native FSX.