Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Initial Flight & AI Chatter

Featured Replies

Just received my RC4 CD today. (Three days transit time to upstate NY for those who are wondering...)Just 15 minutes to get the key after sending the registration email. Thanks for the fast service!I installed RC4 on a second computer via WideFS. Installation and initial database creation went perfectly, thanks to the tips in the manual, and here on the forum.My initial flight was from JFK to CHS at FL 340 - using Level-D 767 and real-time weather via ASVEverything was almost flawless, from initial clearance through shutdown and final critique at the destination. One minor issue though.During initial setup, I selected the AI chatter option. However, AI chatter was almost non-existent throughout the flight. I use Ultimate Traffic, and the skies are quite "full" at all times, both in the terminal areas, and enroute.I did hear two AI aircraft talking to Kennedy ground during my taxi to the active. After that - almost nothing. I heard Washington Center give a traffic call-out to an AI plane once... but that was the only time. No other AI aircraft coms were heard on any of the center frequencies during the 1-hour enroute phase. Yet, there was definitely traffic aloft within the same center sectors and levels as my own aircraft. I saw at least 6 northbound flights pass within 5 miles. Per the TCAS altitude readouts, they should have been in contact with the same controller as my aircraft - but nothing was heard. Center had no problem communicating with me - I received several handoffs - and the approach and landing phases worked just as advertised - but again, no AI chatter to speak of.Curious as to how much chatter I would expect to hear in a traffic-dense environment.Other than that, I am EXTREMELY pleased with the quality of the program, and am looking forward to many more flights with RC4's ultra-accurate ATC and procedures.Regards,Jim Barrett

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

Hi Jim,I also use Ultimate Traffic. I'd probably expect to hear rather more chatter on a flight like that particularly when climbing. It will vary with the time of day etc. The ai will only be spoken to if there is something to say (contact new controller, traffic advisory etc)I've just tried a flight out of KJFK and by the time I'd got to FL340 I'd heard 11 calls to ai's. Once at FL 340 it's been a lot quieter, much of the traffic is well below me. There only seem to be about 3 ai in the same stratum as I am and I haven't heard any calls for the last 15 mins.I assume you have both 'interact with ai' and 'ai chatter' enabled.Basically try a few more flights. You might just have got a quiet period.All the best,John

Hi Jim,One other thing you might try is to go to the FSUIPC settings (on the FS toolbar modules fsuipc)On the Technical tab find the 'limit tcas range' and enter 80 in the box. See the FSUIPC manual for an explanation of exactly what this does. Essentially RC will be told about all aircraft within this distance of your aircraft. So the larger this value, the more ai RC will be dealing with up to a limit of around 100 ai.All the best,John

  • Author

Thanks for the info. I'll increase the TCAS range and see what happens. I'll definitely be doing many more flights in upcoming days!Jim Barrett

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

Hi Jim,I think you'll definitely get more enroute chatter with the tcas range set to 80 (or even 0, unlimited)One thing I just discovered, if you happen to use aismooth the tcas range will be set to 40 whatever you do whilst ai smooth is running.All the best,John

I tried a short flight from KMIA to MUHA, knowing there would be loads of AI traffic at Miami. Indeed, I had quite a few aircraft taxiing in front of me but was not hearing any calls.On takeoff, and climbing up to cruise, I heard about 3 calls, then I used the trick from RC3 and tuned comm2 to the FS9 ATC freq and set both comms on. I was hearing a lot of calls via FS9 which were not being made by RC4, but also noticed that the freqs were not always the same so this may account for it?Thanks also John for the tip about the tcas setting, will try that next flight.Jack

Jack Johnston

 

Banner_FS2Crew_NGX_Driver.jpg

  • Commercial Member

that's pretty strange. we all get a lot of ai chatter. do you have all the chatter pilot's selected on the voices page?are you running fshotseat something or other? there is a fsuipc setting for that product that doesn't like to work with rcalso, are you using com1 as your radio? the secret of ai chatter, being on the right frequency when the ai are saying something.jd

All chatter pilots are selected except you, JD - I switched you off as I had you selected as the pilot (I think, or maybe as a controller).No, I don't have FS Hotseat installed, the only addon I have of that nature is FS passengers and I did that flight without it running.Comm 1 was set as my radio for RC4, as mentioned I later set comm 2 to FS9 and set the Both Comms button on. I think it is definitely a frequency thing as you say, I did notice at least once that the 2 frequencies for center were not the same. I'll check out the frequencies and see if that is what it is.Thanks JD!Jack

Jack Johnston

 

Banner_FS2Crew_NGX_Driver.jpg

  • Commercial Member

no aismooth? it sets the tcas range to 40 milesjd

No, no AI Smooth nor the other similar programme. I'll check the FSUIPC setting as mentioned further up the thread and see what is in there as the tcas setting, though.Jack

Jack Johnston

 

Banner_FS2Crew_NGX_Driver.jpg

>All chatter pilots are selected except you, JD - I switched>you off as I had you selected as the pilot (I think, or maybe>as a controller).>>No, I don't have FS Hotseat installed, the only addon I have>of that nature is FS passengers and I did that flight without>it running.>>Comm 1 was set as my radio for RC4, as mentioned I later set>comm 2 to FS9 and set the Both Comms button on. I think it is>definitely a frequency thing as you say, I did notice at least>once that the 2 frequencies for center were not the same. I'll>check out the frequencies and see if that is what it is.>>Thanks JD!>>JackHi All,how do you set FS9 to com2??? I tried yesterday but I don't have a clue how to do that. Help is apreciated. ThanksConstantin

Hi Constantin,Usually on your radio stack you'll find buttons which allow you to select com1 or com2. Just press the com2 one. They are in different places on different panels.All the best,John

Can you remind me how to set RC 4 to com 1 and FS 9 to com 2?ThanksGreg

Greg Clark

Hi Greg,RC will always use com 1If you set your radio stack to com 2 (there should be a button somewhere to do that) FS will then use com 2 whilst RC continues to use com 1.All the best,John

I found that the ATc was calling AI flights Boeing rather than the airline the aircraft belonged to . I had FSHotFX on my PC, but had it disabled and didn't turn it on , once I got RC4. Then I uninstalled FS HotFX... After I did that I read about the TCAsid setting in the FSUIPC ini file and changed it from "type" and renamed it "flight"....Might be something to check, if you have had FSHot, cause apparently it changes that FSUIPC.ini setting permanently, and you have to change it manually using notepad and save it. . I also found that the TCAS range was at 10 so I changed that to 80.....

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.