Recently I've noticed that RC ATC is commanding go arounds after clearing another plane to land in the same runway I'm landing, but in opposite direction. I have been refreshing RC's runway db whenever I install new scenery. I'm only using World of AI traffic at about 40%. I'm not using any other program to control the AI planes, and finally, I've searched this forum.

 

Any suggestions?

First, just a routine check, you have rebuilt the RC database running the scenery rebuild from within RC usin g the network (RC and FS on different PCs) or local (same PC). The latest version 4.613 of makerwys.exe is here:

http://forum.simflight.com/topic/66136-useful-additional-programs/.

 

Also, your fsuipc is current from here:

http://forum.simflight.com/topic/66139-updated-modules/

 

RC does not clear ai aircraft assigning runways. That is FS and RC only reports what is happening. RC only assigns the runways for user aircraft.

 

If you are using FSX and Ultimate Traffic 2 for FSX then be sure the air rendering setting is set to maximum so RC can see ai patterns as you get into the approach phase starting 40 nm out. If there are no ai present then RC uses its best guess based on winds and runway properties to assign your runway. If you are using Active Sky Enhanced products under FSX then RC get the METAR direct from ASE. ASE has some service packs issued that assist in getting around the global weather problem when it runs in DWC mode. Please read the pinned topic.

 

RC looks at ai twice during the approach phase. ai are observed before your initial assignment and once more on the way in and RC may reassign your runway if things have changed.

Thank you Ron. I have rebuilt the RC db on local PC, using makerwys.exe 4.6.0.0. I also have registered FSUIPC, 4.8.5.9d. The Wx is from ASE. I'm using AI from World of AI. Perhaps an increase in traffic from 30% to 40% has made the conflicts more likely. Should I increase the percentage to ensure RC "see the ai patterns"? My Wx is from ASE, build 655 (latest).

 

I will increase the traffic to see if that makes a difference.

World of AI should noty be a problem. makerwys is at version 4.6.1.3 revised 12NOV2012.

 

Percent of ai traffic might help but more than likely it is your ASE settings. Some FSX users lock destination weather in that however it may not lock to the forecast METAR used for RC ATIS but whatever the weather is at whatever range it uses.

 

Apparently the DWC requirement of using global weather, which forces FS worldwide weather to be the same as your aircraft location, not what is reported in the METAR, causes problems with RC and other apps that look at ai. Instead of using the destination weather as it will be when you get there, the destination weather ai uses is the same as you aircraft location on the way in and in some cases that can set up a conflicting ai pattern when they are rendered.

 

Check the "unofficial" hifisim forum here on AVSIM for resolutions:

http://forums1.avsim.net/forum/171-the-unofficial-active-sky-support-forum/

for suggestions and current service packs.

 

There is a beta service pack out at http://dreamcatcher.hifisim.com/ASE_Update_SP4_B695.zip or perhaps it has been released according to that forum.

 

fsuipc4 current versions report for RC ATIS the weather according to the METAR in your ASE forecast, not the current weather forced by the global weather mode.

 

If this option is available in ASE but the destination weather may vary from the weather in the METAR:

 

"Force Destination Wx Zone – Forces the destination airport weather to all stations within 80nm of the destination. Works only when a flight plan is loaded. Useful to keep your entire approach conditions consistent to the departure airport area."

 

Finally, to avoid sudden changes I recommend you download a weather archive for the time of your FS slight as opposed to using real world weather. Then be sure you process your flight plan in ASE for added stability and to enable locking the destination weather.

Thank you Ron. Updated ASE to B695, and disabled DWC. Also read elsewhere to ensure to refresh AI after the flight plan is loaded in ASE. Did one flight and all went well. Clearly I would have to fly more to determine if this fixes it. :rolleyes:

 

Thank you for your help.

 

Regards