AI Callsigns

[BlinkNFG 0]

Hi,I have just bought RC4 and am impressed with it so far (only done one flight). However I notice that with my UT2 traffic that Radar Contact is not using the correct callsign for AI traffic despite having the callsign recorded. Instead it just uses the first letter - for example United Airlines are referred to as "Uniform" and American Airlines as "Alpha". Is there anything I can do to fix this?thanksJon

[Drumcode 1,893]

There's a thread about it in this forum, search for it. It instructs the user to edit a csv file that would take care of this issue.

[BlinkNFG 0]

There's a thread about it in this forum, search for it. It instructs the user to edit a csv file that would take care of this issue.

Thanks for the reply. I searched the manual (should have thought to also do a search of the forum!)I now have the callsigns working.A couple of other things I have noticed with RC4 ...i) There is very little gap between the controllers speaking and the pilots - a small gap would add to the realism (similar to the gap between you and the controller). I assume nothing can be done but thought I would mention it ii) After I receive my clearance and am not told to contact ground (though the text box tells me to do so). Then when I switch to ground and ask for start-up I am then told to contact ground on the frequency I am already on - is that right?thanksJon

[jd 57]

Hi,I have just bought RC4 and am impressed with it so far (only done one flight). However I notice that with my UT2 traffic that Radar Contact is not using the correct callsign for AI traffic despite having the callsign recorded. Instead it just uses the first letter - for example United Airlines are referred to as "Uniform" and American Airlines as "Alpha". Is there anything I can do to fix this?thanksJon

send me a log, tell me which ai are spoken incorrectly. also send me your fsuipc.ini file.instructions on how to do a log, is pinned at the top of the forumjd

[BlinkNFG 0]

Thanks for the reply and Radar Contact itself.However since editing the csv file as explained in another thread (thanks to Drumcode for recommending the search) all callsigns are now correct.Would be interested in your thoughts on my other two points thoughthanks a lot Jon

[ronzie 21]

In UT2 also be sure your spawning distance option is to set to the maximum range. This is important especially at approach time when RC assigns a runway based on AI patterns (if present) at 40 nm out from destination. AI need time to settle down as well.As always, be sure your FSUIPC4 is at the latest version from the links pinned at the forum top section threads.