Testing AI For RC Compatibility and Examination by RC and AI Behavior

This is in response to both presales and current users in regards to RC seeing AI aircraft. You do not need RC for this test.

Users that do not have RC or other application that uses FSUIPC should install the correct FS version downloaded from the following link (registration not required):

http://forum.simflig...pdated-modules/

Then install this free utility Traffic Look (.exe) from this page:

http://forum.simflig...ional-programs/

and set up a shortcut to TrafficLook.exe.

No fees or the presence of RC is required for this test.

After installing FSUIPC and Traffic Look start up your version of FS and load a parked flight at a busy airport at a busy time for local traffic. Be sure FS is NOT set to pause on task switch. Alt-tab to get to your TrafficLook.exe shortcut and start up TrafficLook.exe.

Traffic Look will open up a table type grid in a window outside of FS. You can alt-tab between FS and Traffic Look, run each in tiled windows, or if a dual monitor setup run each on its own monitor.

Traffic Look has a row for each aircraft showing items like its identification by flight call and number or tail ID, its current state, destination runway with distance from your location, take-off runway, taxi state, or sleeping (parked) and other useful items.

RC uses FSUIPC and frequently examines this type of ai data. If Traffic Look shows it RC should be able to see it at appropriate times.

Users of Ultimate Traffic 2 for FSX should set it for the maximum spawning distance of ai so RC can examine it for incoming traffic and traffic at destination when RC approach assigns runways while your are about 40 nm out from destination. Another peculiarity reported about UT2 is that initially it identifies ai by tail number until they seem to have contacted ground and start taxiing for departure later than other ai are identified by flight airline and number in the ai process. RC in its departure airport chatter may give you an airline flight by tail number until UT2 assigns the flight code.

Another use of Traffic Look is to alt-tab to it if you are observing discrepancies on RC assigning runways at departure and throughout approach where ai and your aircraft result in conflicting patterns. This can occur with some weather applications mostly in FSX as ai change patterns as you approach. AI are assigned runways within FS by a complicated runway scoring system that makes it difficult to always use weather only to predict runway assignments. That is why RC examines ai patterns first as a priority in assigning runways.

I hope this helps users check the compatibility and behavior of ai as seen by RC.