Good morning,I am seriously considering the purchase of RC4, and I see that it is compatible with Ultimate Traffic (According to the website). Is it compatible with Ultimate Traffic 2? And does it effectivly move AI traffic out of the way so I am not on approach with an AI plane at the same time? I appreciate any help you can give before I buy.,Brian A. Neuman

Good morning,I am seriously considering the purchase of RC4, and I see that it is compatible with Ultimate Traffic (According to the website). Is it compatible with Ultimate Traffic 2? And does it effectivly move AI traffic out of the way so I am not on approach with an AI plane at the same time? I appreciate any help you can give before I buy.,Brian A. Neuman

Brian, I anwered you question on the FSX forum a few minutes agoBob Johnson

Brian, I anwered you question on the FSX forum a few minutes agoBob Johnson

Yep, I saw it there. Thanks Bob.-Brian

Brian, I anwered you question on the FSX forum a few minutes agoBob Johnson

can you answer me please, I am also want to know the answer, I am at the same position as Brian

can you answer me please, I am also want to know the answer, I am at the same position as Brian

Akila,Yes, I have found that it will move the traffic out of the way about 99% of the time, I have been called to do a go around 1 time, thats it. It has been a very helpful program to use in heavy traffic.

Akila,Yes, I have found that it will move the traffic out of the way about 99% of the time, I have been called to do a go around 1 time, thats it. It has been a very helpful program to use in heavy traffic.

however, would it also control the UT2 AI (you can actually here the RC4 ATC talks to them and they talk back to the RC4 ATC) or only deviate you from crashing into them?

however, would it also control the UT2 AI (you can actually here the RC4 ATC talks to them and they talk back to the RC4 ATC) or only deviate you from crashing into them?

Akila,It actually speaks to them and controls them as well. Its a good fuctioning program that does deal with AI traffic well. Another program to look at along side RC4 is AI Smoooth (Freeware) that will also help keep fewer aircraft on approach.

Be sure UT2 has its AI spawning distance set to maximum so they are recognized in plenty of time especially when flying a jet. RC needs to see these at 40 nm out (or better) in order to give AI patterns a priority in selecting an arrival runway.

that was useful Information guys, thanks.Do you know if RC4 uses in any way the Navigraph Airac cycle (AIRAC) for SID/STAR, routes , etc?

No AIRAC updates are supported on this product. All SID and STAR infomation has to be included in the flightplan that you open in RC4. You are able to tell RC4 that you will be departing using altitude restrictions this will then give you 30NM from the airfield to follow the SID without the controller giving you vectors to your first departure fix.Hope this helps, Iv only just got this software and think its fantastic, certainly with UT2 at 100%.Stuart Turbefield

No AIRAC updates are supported on this product. All SID and STAR infomation has to be included in the flightplan that you open in RC4. You are able to tell RC4 that you will be departing using altitude restrictions this will then give you 30NM from the airfield to follow the SID without the controller giving you vectors to your first departure fix.Hope this helps, Iv only just got this software and think its fantastic, certainly with UT2 at 100%.Stuart Turbefield

So if I don't provide SID/STAR in the RC plan, would it be like vectors to final style?thanks man, was a helpful information.

Real world STARs can start well beyond the approach boundaries and SIDs can go well beyond the departure phase, both having influence on enroute (center) ATC. RC allows accommodation for SID and STAR waypoint flexibility within its departure and arrival phases. You can see these in the tutorials.SID and STAR waypoints that would appear within ATC center jurisdiction must be in the flight plan.To give you an idea on the length of a SID or STAR in the congested NE area of the US you'll often find a common transition point of the departure and arrival airport. The FAA has published 'preferred routes' that allow an entire trip to take place using just TRACON, the term here for Terminal Area Radar Control which is essentially the departure and approach facilities, and center does not even get involved in any part of these dedicated routes. In RC however all operations from outside of 30 nm of the departure airport and 40 nm of the destination airport occur using RC's center operation in this version.If you want to prepare a flight plan using FAA preferred routes you can query them on this site:http://www.fly.faa.gov/rmt/nfdc_preferred_routes_database.jspand just get the entire list and type of routes between the departure and destination as in the attached image by entering the three letter (no K) departure and arrival designators. If you look at the IFR charts and the filed routes on flightaware.com between these airports you'll recognize the Waukon SID included here and the MOTIF3 STAR for arrival.Here's the actual waypoints used for the H high jet airways route:KMSP UKN3 DBQ CVA MOTIF3 KMDW waypoints translate to:KMSP Origin Airport 44.8819567 -93.2217656FGT VOR-TAC (NAVAID) 44.6309444 -93.1820556LOAFR Reporting Point 44.4695278 -92.9799444SHUZE Reporting Point 44.3575556 -92.8406944BROTA Reporting Point 44.2205000 -92.6711667UKN VOR-TAC (NAVAID) 43.2800833 -91.5373611 ARTCC Boundary Crossing 43.0932778 -91.3588056CASSY Reporting Point 42.7446389 -91.0291389DBQ VOR-TAC (NAVAID) 42.4014722 -90.7090833---------------direct to betweeen SID and STAR-----------------CVA VOR-TAC (NAVAID) 41.7085556 -90.4833056BDF VOR-TAC (NAVAID) 41.1597222 -89.5878611MOTIF Reporting Point 41.2295833 -88.5010000MINOK Reporting Point 41.4688611 -88.3632778JOT VOR-TAC (NAVAID) 41.5464167 -88.3184167KMDW Destination Airport 41.7859722 -87.7524167many beyond the departure and approach limits of 30 nm and 40 nm in RC that must be in the RC enroute plan.

Real world STARs can start well beyond the approach boundaries and SIDs can go well beyond the departure phase, both having influence on enroute (center) ATC. RC allows accommodation for SID and STAR waypoint flexibility within its departure and arrival phases. You can see these in the tutorials.SID and STAR waypoints that would appear within ATC center jurisdiction must be in the flight plan.To give you an idea on the length of a SID or STAR in the congested NE area of the US you'll often find a common transition point of the departure and arrival airport. The FAA has published 'preferred routes' that allow an entire trip to take place using just TRACON, the term here for Terminal Area Radar Control which is essentially the departure and approach facilities, and center does not even get involved in any part of these dedicated routes. In RC however all operations from outside of 30 nm of the departure airport and 40 nm of the destination airport occur using RC's center operation in this version.If you want to prepare a flight plan using FAA preferred routes you can query them on this site:http://www.fly.faa.g...es_database.jspand just get the entire list and type of routes between the departure and destination as in the attached image by entering the three letter (no K) departure and arrival designators. If you look at the IFR charts and the filed routes on flightaware.com between these airports you'll recognize the Waukon SID included here and the MOTIF3 STAR for arrival.Here's the actual waypoints used for the H high jet airways route:KMSP UKN3 DBQ CVA MOTIF3 KMDW waypoints translate to:KMSP Origin Airport 44.8819567 -93.2217656FGT VOR-TAC (NAVAID) 44.6309444 -93.1820556LOAFR Reporting Point 44.4695278 -92.9799444SHUZE Reporting Point 44.3575556 -92.8406944BROTA Reporting Point 44.2205000 -92.6711667UKN VOR-TAC (NAVAID) 43.2800833 -91.5373611 ARTCC Boundary Crossing 43.0932778 -91.3588056CASSY Reporting Point 42.7446389 -91.0291389DBQ VOR-TAC (NAVAID) 42.4014722 -90.7090833---------------direct to betweeen SID and STAR-----------------CVA VOR-TAC (NAVAID) 41.7085556 -90.4833056BDF VOR-TAC (NAVAID) 41.1597222 -89.5878611MOTIF Reporting Point 41.2295833 -88.5010000MINOK Reporting Point 41.4688611 -88.3632778JOT VOR-TAC (NAVAID) 41.5464167 -88.3184167KMDW Destination Airport 41.7859722 -87.7524167many beyond the departure and approach limits of 30 nm and 40 nm in RC that must be in the RC enroute plan.

the only issue is that usually (if not always) SID/STAR are direct depended on the Runway in use and that is not known to me before submitting the flight plan as the ATCs both on Departure and arrival had yet allocated them to me.

You'll find that by direction many of the SIDs and STARs have waypoints common to runways. Just include the common points in your flight plan and either take vectors to/from the common point or use the alt-options to navigate the first 30/40 nm on your own adding NOTAMS to the mix.If you are an FSBuild user there is a build option that is not sticky between FSB sessions. It lets you build from the grid rather than route window. That way you can delete the non-common points from the expanded SID/STAR introduced waypoints just keeping the common ones in your build.

the only issue is that usually (if not always) SID/STAR are direct depended on the Runway in use and that is not known to me before submitting the flight plan as the ATCs both on Departure and arrival had yet allocated them to me.