I´m a totally new user of RC and I must say this program turn FSX upside down for me in a good way! First flight LSZH to EKCH with my “Mad dog” was a challenge because RC and FSX ATC competed in use of my radio. Then after passing CDA, RC started to vector me into rwy 22R and told me to turn 010! I have planned to use rwy 22L and programmed the FMC (and flight plan) with the wpts of STAR CDA3N and an option in the menu made me press 4 IAP APP (selected rwy 22L). I was cleared to fly my STAR as I have done a few (hundred) times. After landing I was impressed of myself as usual and hit menu option 2 Critique. I was “Busted” big time and the academic fist RC hit me with in the face made me motivated to do the following:1. Read the manual2. Learn the difference between issued FL or altitude (don´t hit the B button in Europe)3. Learn about “level bust” in real world Now to my question about AI logic. Yesterday I went to EHAM and let RC vector me to rwy 18C and get clear to land about 5 miles out. The weather was cloudy yesterday so when I get of the cloud about 300 ft above ground a Learjet 45 occupied the rwy in opposite direction and I saw two more AI aircraft (I use UT2) approaching rwy 36C. I made a missed approach and RC told me to keep 3000 ft and started to vector me for another go (Stated my intension). This time RC vectored me nice to active rwy 36C. Another thing happened during the second vectoring attempt. Controller informed me QNH 1032 and by now I immediately switched to 1032 in hope to not get “Busted” again :( After 10 sec the controller asked if I have some problems maintaining altitude and I was, yes; “busted” again Now I pressed B to see current pressure and my altimeter turned 1019. I noticed FSX made dramatic QNH change on the same altitude in the area so this is not an RC issue. This led me to just about one only question and that is how to make RC use the active rwy earlier if possible? /Patrik Soderberg

I´m a totally new user of RC and I must say this program turn FSX upside down for me in a good way! First flight LSZH to EKCH with my “Mad dog” was a challenge because RC and FSX ATC competed in use of my radio. Then after passing CDA, RC started to vector me into rwy 22R and told me to turn 010! I have planned to use rwy 22L and programmed the FMC (and flight plan) with the wpts of STAR CDA3N and an option in the menu made me press 4 IAP APP (selected rwy 22L). I was cleared to fly my STAR as I have done a few (hundred) times. After landing I was impressed of myself as usual and hit menu option 2 Critique. I was “Busted” big time and the academic fist RC hit me with in the face made me motivated to do the following:1. Read the manual2. Learn the difference between issued FL or altitude (don´t hit the B button in Europe)3. Learn about “level bust” in real world Now to my question about AI logic. Yesterday I went to EHAM and let RC vector me to rwy 18C and get clear to land about 5 miles out. The weather was cloudy yesterday so when I get of the cloud about 300 ft above ground a Learjet 45 occupied the rwy in opposite direction and I saw two more AI aircraft (I use UT2) approaching rwy 36C. I made a missed approach and RC told me to keep 3000 ft and started to vector me for another go (Stated my intension). This time RC vectored me nice to active rwy 36C. Another thing happened during the second vectoring attempt. Controller informed me QNH 1032 and by now I immediately switched to 1032 in hope to not get “Busted” again :( After 10 sec the controller asked if I have some problems maintaining altitude and I was, yes; “busted” again Now I pressed B to see current pressure and my altimeter turned 1019. I noticed FSX made dramatic QNH change on the same altitude in the area so this is not an RC issue. This led me to just about one only question and that is how to make RC use the active rwy earlier if possible? /Patrik Soderberg

make sure your fsuipc settings are correct. look in the fsuipc.ini file - or in the registered version of fsuipc. find tcas range. make sure that is set to 0.did you request a specific runway? if you did, that's the problem. i give you what you asked for, the ai still do what they want to.if this happens a lot, make a log, i'll tell you whats going wrong on your flights.jd

make sure your fsuipc settings are correct. look in the fsuipc.ini file - or in the registered version of fsuipc. find tcas range. make sure that is set to 0.did you request a specific runway? if you did, that's the problem. i give you what you asked for, the ai still do what they want to.if this happens a lot, make a log, i'll tell you whats going wrong on your flights.jd

Thank you for the fast replay JD!I have changed the value to 0 for tcas range= (it was set to 40) so I hope for less crazy AI traffic now :smile:By the way, I´m very pleased with my purchase!/Patrik

1. Be sure in UT2 AI spawning is set to the maximum so RC approach can see the AI in time in the proper pattern when you are 40 nm out from diestination.2. The FS 'B' key is hard coded to a transition altitude of 18,000 feet as used in the FAA territories. That would get you busted altitudes flying elsewhere. You need to use the TA off of charts or as shown on the Controller Tab in RC before your flight. If RC assigns your next altitude in feet use local pressure. If RC assigns your next altitude as a flight level use standard pressure of 29.92 in. or 1013 mb.If you are using ASE under FSX the search out the difficulties that can occur with it using the threads in this forum.Here's the links for updating FSUIPC and makerwys.exe: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/From that download link page under the Additional Programs link get the latest makerwys.exeFSUIPC 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=libraryAfter getting FSUIPC installed and then makerwys.exe installed in your FS folder start RC and rebuild the scenery database.If you have both an FSX and FS9 installation two RC4 folders were created. Be sure you have two shortcuts for each RC version to its respective folder for each FS version. (VISTA and Win 7 users will want for each shortcut set its advanced properties to run as admin.) Rebuild from within each RC version the scenery database.

1. Be sure in UT2 AI spawning is set to the maximum so RC approach can see the AI in time in the proper pattern when you are 40 nm out from diestination.2. The FS 'B' key is hard coded to a transition altitude of 18,000 feet as used in the FAA territories. That would get you busted altitudes flying elsewhere. You need to use the TA off of charts or as shown on the Controller Tab in RC before your flight. If RC assigns your next altitude in feet use local pressure. If RC assigns your next altitude as a flight level use standard pressure of 29.92 in. or 1013 mb.If you are using ASE under FSX the search out the difficulties that can occur with it using the threads in this forum.Here's the links for updating FSUIPC and makerwys.exe: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/From that download link page under the Additional Programs link get the latest makerwys.exeFSUIPC 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=libraryAfter getting FSUIPC installed and then makerwys.exe installed in your FS folder start RC and rebuild the scenery database.If you have both an FSX and FS9 installation two RC4 folders were created. Be sure you have two shortcuts for each RC version to its respective folder for each FS version. (VISTA and Win 7 users will want for each shortcut set its advanced properties to run as admin.) Rebuild from within each RC version the scenery database.

Hi Ronzie!Thank you for all the good advice. I don´t use ASE but I´m well aware of the Flight1 registry fix.Lets run the checklist:

• Updated FSUIPC to 4.664 interim

• Updated MakeRwys.EXE to 4.43

• Turned UT2 to spawn max! (600 ac)

• Run Registry fix

• Rebuild RC scenery database

Done!I have created another problem now! What if I don´t hear “good job” and “excellent” when I use the Critiqe function? After all your good support I have no one to blame except……….Bryan the copilot! :smile:Once again, thank you!Patrik