I don't think but I'm not sure if the aircraft radius play a part in this. Someone better qualified than me might answer. As far as AI one radius that does matter is around the hold short point. If you bring it a diagram up in ADE9X or AFX or, for FS9, AFCAD there should be a View option to display the hold short radius. This fixed size radius must include within its boundary the edge of the runway for AI to enter it. In general, even for RC, it makes a good reference such as if it reaches just over the edge on an angled taxiway. AI will get stuck at the hold short if this criteria is not met. This is an FS AI engine thing, not RC.

---------snip-----------I found that using external view to put the nose on the line helped. Does the radius of the aircraft play a part Ron? I have seen AI planes stop about 100 meters behind me at holding points.CheersJulian

Hi All, I have gone over the hold line but no change. There is another boundary line there prior to the runway hold line. If my memory servers me correctly I believe it is an ILS boundary line or RF line used as a warning that your plane may block an RF signal. I dont think though that this is used in FS for any decision making on the part of ATC though. What I wondered was even though I am using the default scenery with UTX and GEX but still have ORBX PNW installed, would there be any way ORBX PNW could interfere even though it is not active?Thanks FellasBob

do you have the latest makerwys.exe in the fs root directory?have you clicked the rebuild rc scenery database button in rc?still having a problem?if so, the only way to know what is happening, is to make a log and send me a log. it's painless, it's quick, and you'll get an answer quickly.jd

Hey JD,Yes, latest makerwys.exe and rebuild was completed.Ok I will send a log sometime today. Where is it located?I am running a widefs client if that makes a difference in location of the file.ThanksBob

do you have the latest makerwys.exe in the fs root directory?have you clicked the rebuild rc scenery database button in rc?still having a problem?if so, the only way to know what is happening, is to make a log and send me a log. it's painless, it's quick, and you'll get an answer quickly.jd

JD, I wanted to point out that in my programs directory there are 2 rc folders in the root. One named "rc4" the other "rc4x". Not sure why but need to know if this could be an issue."rc4" contains only shortcuts and uninstall.exe.Bob

do you have the latest makerwys.exe in the fs root directory?have you clicked the rebuild rc scenery database button in rc?still having a problem?if so, the only way to know what is happening, is to make a log and send me a log. it's painless, it's quick, and you'll get an answer quickly.jd

Hi All (JD)Well I loaded the same flightplan - An 18 mi jog from KSEA to KPWT. I did set debug (wow what a monster output). Anyway, the only step I changed was moving past the runway hold a tiny bit and guess what?... everything went smooth. The only difference though with this flight was that I was #2 in takeoff position. Previously the runway was clear. Not sure if this could make a difference, but I did have to hold regardless. The flight went smooth as glass. I did try to trip up RC by requesting a visual approach and then making a turn towards the runway and then requesting an ILS. RC handled the change. So is my luck going to continue?Although a relatively easy flight in terms of length, weather and traffic, my next one will be from KSEA to Portland with a pit stop along the way. I will keep in touch with any issues.Thanks much for all who chimed in to help, and I really enjoyed the quick responses from all controllers and the chatter was quite nice also.RegardsBob

do you have the latest makerwys.exe in the fs root directory?have you clicked the rebuild rc scenery database button in rc?still having a problem?if so, the only way to know what is happening, is to make a log and send me a log. it's painless, it's quick, and you'll get an answer quickly.jd

Hi Bob,Well done for persevering and getting a result. You can use that experience in your next flight. Within a week I imagine you'll be flying from one side of the States to the other in a 777! And yes, the logs can be enormous. We had logging enabled by default when testing because JD got so fed up with us reporting a problem and then not having a log! :(

Just to insure some things in your process and answer one query:If you had RC installed for two versions of FS, there would be two folders created. It looks like you are using FSX and RC4X as that active folder with its applications, configurartion, and folders under that with data, sound files, scripts for audio, etc.. If you ever used FS9 that would explain the RC4 folder but apparently you uninstalled that. Your RC4X main folder has the log file when created.Since you are on a WideFS Client with RC and FS is on a host then you need to use a two step procedure when building the scenery database. First go into your host FSX folder and directly run makerwys.exe. After answering OK to the final dialog (you'll see an airport and runway count) it will finish up and exit.Now you can go into your client PC and start RC. Start the scenery rebuild utility. When it asks if you are using WideFS answer YES and you'll get a caution. Let it continue entering the path to your network host FSX folder. On proceeding you'll get some dialog boxes needing you to OK to continue. After the last one give it a minute to finish up allowing your PC to write the final files.To insure your files updated correctly if you wish go into your RC4X\data folder. Right click on r4.csv and then properties and look at the modified date and time. Do the same for a4.csv. These should be the date and near the time the scenery rebuild completed.It is very important that RC has the r4.csv and a4.csv files developed from your current scenery. Any time an add-on scenery or afd file (afcad similar) scenery file is added to your system you need to rebuild the scenery. These file correlate locations in your scenery of gates, hold points, runway data, etc., with the aircraft position RC sees via FSUIPC returns. Side effects of mismatch can be incorrect location of your aircraft matching the hold short points, for example, incoming relationship of landing AI with respect to the runway and your hold position, incorrect interpretation of the position of ground AI, seeing if you aircraft is properly positioned on the runway for take-off clearance, and runway number assignments plus other issues.As Ray stated, glad you got your clearance by moving forward just a bit.

Ronzie and JD, thanks for the reply.Yes the two spreadsheet files are current. All is well at this time and looking forward to my next flight. What a difference in immersion.I thought I might try IYP just for kicks with RC. I did try it in the SATC mode without RC, but repeating taxi instructions and any repeat for that matter that is somewhat long, just does not happen with that product, but it looks like the read backs for RC using IYP are a little more simplified. I am focusing on Plan-G right now to see it's capabilities, and so far for a freeware Flight Planner I am really impressed.RegardsBob

Just to insure some things in your process and answer one query:If you had RC installed for two versions of FS, there would be two folders created. It looks like you are using FSX and RC4X as that active folder with its applications, configurartion, and folders under that with data, sound files, scripts for audio, etc.. If you ever used FS9 that would explain the RC4 folder but apparently you uninstalled that. Your RC4X main folder has the log file when created.Since you are on a WideFS Client with RC and FS is on a host then you need to use a two step procedure when building the scenery database. First go into your host FSX folder and directly run makerwys.exe. After answering OK to the final dialog (you'll see an airport and runway count) it will finish up and exit.Now you can go into your client PC and start RC. Start the scenery rebuild utility. When it asks if you are using WideFS answer YES and you'll get a caution. Let it continue entering the path to your network host FSX folder. On proceeding you'll get some dialog boxes needing you to OK to continue. After the last one give it a minute to finish up allowing your PC to write the final files.To insure your files updated correctly if you wish go into your RC4X\data folder. Right click on r4.csv and then properties and look at the modified date and time. Do the same for a4.csv. These should be the date and near the time the scenery rebuild completed.It is very important that RC has the r4.csv and a4.csv files developed from your current scenery. Any time an add-on scenery or afd file (afcad similar) scenery file is added to your system you need to rebuild the scenery. These file correlate locations in your scenery of gates, hold points, runway data, etc., with the aircraft position RC sees via FSUIPC returns. Side effects of mismatch can be incorrect location of your aircraft matching the hold short points, for example, incoming relationship of landing AI with respect to the runway and your hold position, incorrect interpretation of the position of ground AI, seeing if you aircraft is properly positioned on the runway for take-off clearance, and runway number assignments plus other issues.As Ray stated, glad you got your clearance by moving forward just a bit.

Hey JD,Yes, latest makerwys.exe and rebuild was completed.Ok I will send a log sometime today. Where is it located?I am running a widefs client if that makes a difference in location of the file.ThanksBob

you are creating the log, so you specify where the log is writtenwidefs eh? walk me through how you are rebuilding the rc scenery database. are you following the steps in the manual on doing it for widefs configurations? if not, rc will never know where the end of the runway is on the fs machinethe rcv4 directory was installed because you chose the fs9 install optionthe rcv4x directory was installed because you chose the fsx install optionand it makes a difference which folder you're running rc from. and from the manual rebuild steps, the files have to be copied to the right directory so rc can rebuild the database.jd

Hi jd,I ran the latest makerwys.exe. I think I downloaded the latest as per your advice or someones. When that completed I copied the r4.csv file to my rc installation on the client then executed the rebuild to create the a4.csv. I checked the dates of both of the csv files and it looked good. The only files in the rcv4 dir were shortcuts and an uninstall file. I believe what I did was uninstall after I had selected fs9 as the target FS. Both the a4 and the r4 csv file have exactly the same datetime stamp which may or may not be correct. Since I only copied the r4 over to the program dir, how did the a4.csv get exactly the same timestamp. My memory is not the best. I can always do againBob

you are creating the log, so you specify where the log is writtenwidefs eh? walk me through how you are rebuilding the rc scenery database. are you following the steps in the manual on doing it for widefs configurations? if not, rc will never know where the end of the runway is on the fs machinethe rcv4 directory was installed because you chose the fs9 install optionthe rcv4x directory was installed because you chose the fsx install optionand it makes a difference which folder you're running rc from. and from the manual rebuild steps, the files have to be copied to the right directory so rc can rebuild the database.jd

As a suggestion for RC 5.0, I recommed that a supplemental, dedicated, key press, override the need to be at an exact location, just in case you are slightly short, on the taxi-way when waiting for ATC to respond or even know you are there. You need some sort of visual or aural feedback given you so you know ATC knows you are at the dashed line!I don't use RC 4.0 much anymore, and this issue, plus the super slow response occassionally, was one of the reasons I don't use it much.Bill Clark

Not quite correct for a networked scenery rebuild. From the manual:"On the RC main screen click the „Rebuild Scenery DB‟ button and answer „yes‟ when asked „Is this a WideFS configuration‟. You will be reminded to run makerwys.exe on the FS machine. If you have done so click OK. At the next screen, enter the network path to your main Flight Simulator folder. RC will now copy the r4.csv file from your Flight Simulator folder into the RCv4\data folder and will then rebuild the airport database (a4.csv). You will receive several messages telling you what is happening. Keep clicking OK until the process is completed."While the method is the same with RC copying the files for you one change from the description above is that RC 4.3 latest version copies the r5.csv to your rc4(x) data folder renaming it to r4.csv. From that it can build a4.csv. Your manual copy of r4.csv should not have been placed in there but if the procedure worked correctly the copy of r5.csv from your FS folder overwrote it.

Hi jd,I ran the latest makerwys.exe. I think I downloaded the latest as per your advice or someones. When that completed I copied the r4.csv file to my rc installation on the client then executed the rebuild to create the a4.csv. I checked the dates of both of the csv files and it looked good. The only files in the rcv4 dir were shortcuts and an uninstall file. I believe what I did was uninstall after I had selected fs9 as the target FS. Both the a4 and the r4 csv file have exactly the same datetime stamp which may or may not be correct. Since I only copied the r4 over to the program dir, how did the a4.csv get exactly the same timestamp. My memory is not the best. I can always do againBob

Hi Ray,Ok I did the Rebuild Scenery and everything went fine. I did verify the files being copied and received the prompts from RC for me to verify the copy and the rebuild.By the way the makerwys.exe version was 4.4.1.0I have a question off topic and it has to do with my server share. This may be an issue with shares between xp and Win7. I created the FSX share to allow for "Everyone read/write" . The issue is that when I try to connect manually from the xp box it asks for a name and password.What is interesting is that it does not care what you put in these fields, but it does ask. When I first did the rebuild scenery it failed. So I tried to connect manually on my xp machine and of course got the login/password. Once it connected, I reran the rebuild from RC and it went through. There is nothing on the Win7 side that mentions a login so I am not sure how I can fix this so no login is necessary. Just thought I would pass this to you and if you had any suggestions.Thanks Much!Bob

Not quite correct for a networked scenery rebuild. From the manual:"On the RC main screen click the „Rebuild Scenery DB‟ button and answer „yes‟ when asked „Is this a WideFS configuration‟. You will be reminded to run makerwys.exe on the FS machine. If you have done so click OK. At the next screen, enter the network path to your main Flight Simulator folder. RC will now copy the r4.csv file from your Flight Simulator folder into the RCv4\data folder and will then rebuild the airport database (a4.csv). You will receive several messages telling you what is happening. Keep clicking OK until the process is completed."While the method is the same with RC copying the files for you one change from the description above is that RC 4.3 latest version copies the r5.csv to your rc4(x) data folder renaming it to r4.csv. From that it can build a4.csv. Your manual copy of r4.csv should not have been placed in there but if the procedure worked correctly the copy of r5.csv from your FS folder overwrote it.

Hi Bob,Unfortunately I don't have Windows7 so I'm not familiar with the security and sharing with that OS. However, sharing in principle should be the same as with XP but others with in7 may be able to help.The fact that the OS is prompting you for a login suggests all is not well. Can you check if the file time stamps in the RC Data folder are the same as the originals in the root FS folder? If so they have been copied. If not then they haven't been copied over suggesting the sharing wasn't successful.

Hi Ray,Yes the filestamps are the same. The login prompt for the share concerns me as I have not been able to find the answer. Once I login then all is well. Not a big deal to click the share for a kick start but it would be nice to get it working without human intervention.RegardsBob

Hi Bob,Unfortunately I don't have Windows7 so I'm not familiar with the security and sharing with that OS. However, sharing in principle should be the same as with XP but others with in7 may be able to help.The fact that the OS is prompting you for a login suggests all is not well. Can you check if the file time stamps in the RC Data folder are the same as the originals in the root FS folder? If so they have been copied. If not then they haven't been copied over suggesting the sharing wasn't successful.