I am sure this has been discussed, but I am unable to find exactly the answer I need by searching the forum. RC continues to assign me a landing runway that is INTO oncoming AI traffic. i know that I can manually request a different runway but that takes away from the realism for me. Do I have a setting wrong or is there something I am missing? Any suggestions?

I am sure this has been discussed, but I am unable to find exactly the answer I need by searching the forum. RC continues to assign me a landing runway that is INTO oncoming AI traffic. i know that I can manually request a different runway but that takes away from the realism for me. Do I have a setting wrong or is there something I am missing? Any suggestions?

make sure your fsuipc setting for ai is set to unlimited milesmaybe you can screen print the fsuipc settings tabif that doesn't help, then make a log, instructions pinned to the top of the forum. duplicate the problem, zip it up, and email it to me.jd

make sure your fsuipc setting for ai is set to unlimited milesmaybe you can screen print the fsuipc settings tabif that doesn't help, then make a log, instructions pinned to the top of the forum. duplicate the problem, zip it up, and email it to me.jd

I always have this problem, what AI setting is there in fsuipc? Im using the fsx version, I took a look in the ini file and see nothing in regards to any AI setting.

Two add-ons can cause a problem.First if you are using the UT2 traffic application go into your settings and insure AI spawning is set to at least 50 miles so RC can examine their trend to seee what runways they are using.If you are using ASE in DWC mode for FSX that will cause AI at the global weather mode and AI at destination will behave according to the location weather according to your aircraft position, not what may be expected when you reach destination so RC when it assigns your runway at approach time will not get the correct environment. This is a problem independent of RC getting ATIS.Please see the pinned topic at the forum head and also the lengthy ASE threads in this forum.In assigning runways RC examines AI action as the first priority, then runway properties and winds, the latter a problem in certain cases with ASE used with FSX.Also insure that Interact with AI is checked in your RC options.To set FSUIPC for maximum range of AI peeking after backing up FSUIPC.ini in your modules folder add in the General section the line:TCASrange=0

Two add-ons can cause a problem.First if you are using the UT2 traffic application go into your settings and insure AI spawning is set to at least 50 miles so RC can examine their trend to seee what runways they are using.If you are using ASE in DWC mode for FSX that will cause AI at the global weather mode and AI at destination will behave according to the location weather according to your aircraft position, not what may be expected when you reach destination so RC when it assigns your runway at approach time will not get the correct environment. This is a problem independent of RC getting ATIS.Please see the pinned topic at the forum head and also the lengthy ASE threads in this forum.In assigning runways RC examines AI action as the first priority, then runway properties and winds, the latter a problem in certain cases with ASE used with FSX.Also insure that Interact with AI is checked in your RC options.To set FSUIPC for maximum range of AI peeking after backing up FSUIPC.ini in your modules folder add in the General section the line:TCASrange=0

As I use neither of these add ons, I am hoping that changing the TCASrange line in the FSUIPC.ini file will solve the problem. I will try a couple of flights and post the results.

You should also update FSUIPC and also makerwys.exe as noted:---------------Get the base FSUIPC version from:http://www.schiratti.com/dowson.htmland then interim update from the modules link on this page:http://forum.simflight.com/forum/142-download-links/FSUIPC now self installs initially based on your registry entry for your FS path. Check that with this free utility:FSX/FS9 Registry Repair Tool (36KB) from http://www.flight1.com/view.asp?page=library----------------It is important to update makerwys.exe to 4.61 or later (for both FSX and FS9) and from within RC rebuild your scenery rebuild. The updated makerwys.exe should replace the the one the RC installer put in your FS folder. Then from within RC run the rebuild and put in the correct path to your FS folder when requested. RC should be started with a shortcut set with advanced properties to run as admin so it can access your FS folder in VISTA and Win 7 and copy back to its folders processed files makerwys produces.This is necessary to insure RC sees in its database your installed scenery information regarding runways, taxiways, parking, etc. so RC can correlate your aircraft position and AI positions with the scenery data.

Do I have a setting wrong or is there something I am missing? Any suggestions?

You are missing AISmooth. Since I have been using it - never had problems like this.

AI Smooth is for incoming traffic separation. I am not aware of any runway direction selection capability. I have version 1.20, the last available. It works in FSX and FS9 and is in the AVSIM FSX Utility library if anyone wishes to try it.

You are missing AISmooth. Since I have been using it - never had problems like this.

To the OP:First, I am assuming you only have one RC folder (used with FSX) and do not also have an FS9 installation so you do not have dual folders.Second, if the problem persists, make a log and send it in to jd as noted in the forum top but to keep it fairly small alt-tab to RC and click Debug when you are about 80 nm from destination. This will allow jd to see the AI patterns and states as you get toward the phase where approach assigns the runway and then follows through till RC is terminated. The log includes the TCAS AI tables (applies whether you have a TCAS in your aircraft or not). If you wish you can terminate RC After you exit the runway. It also might be a good idea to rename the rcv4.log file in the RC folder to something like rc4-021111.log (I used the date) so it will not get overwritten by the next Debug. Then zip it up and send it in as described. In the e-mail you attach it to describe the problem, your pc setup, versions of FSUIPC, makerwys.exe, wide FS, and Windows, if you are using FS weather or other and whether in real-time download, etc., and any other applications you are running with FS and RC.Third, describe here the same details as in your message so we can see the description of your environment.You may be asked to make a complete log from the RC start.

You should also update FSUIPC and also makerwys.exe as noted:---------------Get the base FSUIPC version from:http://www.schiratti.com/dowson.htmland then interim update from the modules link on this page:http://forum.simflig...download-links/FSUIPC now self installs initially based on your registry entry for your FS path. Check that with this free utility:FSX/FS9 Registry Repair Tool (36KB) from http://www.flight1.c...sp?page=library----------------It is important to update makerwys.exe to 4.61 or later (for both FSX and FS9) and from within RC rebuild your scenery rebuild. The updated makerwys.exe should replace the the one the RC installer put in your FS folder. Then from within RC run the rebuild and put in the correct path to your FS folder when requested. RC should be started with a shortcut set with advanced properties to run as admin so it can access your FS folder in VISTA and Win 7 and copy back to its folders processed files makerwys produces.This is necessary to insure RC sees in its database your installed scenery information regarding runways, taxiways, parking, etc. so RC can correlate your aircraft position and AI positions with the scenery data.

I only see makerwys 4.41 is there a 4.61 or did you make a typo?

Typo, sorry. There is an interim update here;http://forum.simflight.com/topic/66136-useful-additional-programs/The release notes on that page explain all.

I only see makerwys 4.41 is there a 4.61 or did you make a typo?