Hi,Thought I lost comms but did a couple of "say agains" and it was functioning but sat at the runway with no traffic for 15 minutes. finally aborted the take off.What causes this and when should I make the determination that the tower just forgot about me? RegardsBob

Hi Bob,A bit more info is needed. Does it happen at all airports or only one? If only one, which one?Have you added 3rd party scenery for that airport? If so, have you rebuilt your database?Finally, do you have 'Interact with Ai" enabled in Settings? That's from memory so I hope I got it right.This type of problem usually occurs when RC sees you in a different place to where you actually are. hence the need to rebuild the database.

Update FSUIPC and Makerwys.exe as detailed in this thread.:http://forum.avsim.net/topic/323531-no-takeoff/The current makerwys is at version 4.63.

Hi Ray,Database/Scenery was completed so no problem there. Interact with AI was off. Ground had me taxi to 16L plus it had me tune to the proper tower freq. So it seems something else has gone sour. Is there some sort of a log file that I can look at. I could try degug "on" to see if it tells me anything. Again,after sitting for 15 minutes, I went through the menu system and found "Abort TO", which appears to me that RC was functioning at some level. Maybe the tower crew took a break and lock themselves out LOL. Any other ideas would be appreciated. I will try the same flight again and seewhat happens with debug on. Not sure where to look for the log file but I can check the folders.RegardsBob

Hi Bob,A bit more info is needed. Does it happen at all airports or only one? If only one, which one?Have you added 3rd party scenery for that airport? If so, have you rebuilt your database?Finally, do you have 'Interact with Ai" enabled in Settings? That's from memory so I hope I got it right.This type of problem usually occurs when RC sees you in a different place to where you actually are. hence the need to rebuild the database.

Ronzie, I will check that thread and do the update just in case and report back. Thanks for the lead!!Bob

Update FSUIPC and Makerwys.exe as detailed in this thread.:http://forum.avsim.n...531-no-takeoff/The current makerwys is at version 4.63.

Bob,'Interact with AI' must be enabled. Enable it and try again. I think you'll find the problem is solved.

Bob,'Interact with AI' must be enabled. Enable it and try again. I think you'll find the problem is solved.

If not, make analog and send it to me. Instructions pinned to top of forum. Be sure to click debug before loading the plan

Ok Thanks Fellas. I did have this off so let me give it a try tonight. I did not see anything in the docs on this but I have been known to make an error ocassionally LOL I did rebuild the db too with the newer version.I will check back with you but I have been grounded for awhile (wife home). Thanks Again.Bob

If not, make analog and send it to me. Instructions pinned to top of forum. Be sure to click debug before loading the plan

Are you near enough to the runway ?Have you added new airports; if so are their 'holding points' too far away from the runway edge ?If they are too far away use an airport editor (like AFCAD) to adjust those holding points.

Hi,KSEA, right behind the runway hold line. The database is up to date. Not sure why this is happening but this was the second attempt and the same problem.Bob

Hi,KSEA, right behind the runway hold line. The database is up to date. Not sure why this is happening but this was the second attempt and the same problem.Bob

That's very strange Bob. I suggest you make a log and sent it to JD. Refer to the locked topic further up for instructions.

Hi RayThis also happens at EGLL (simwings) at 27L (Right Holding point) . For example, you need to move over the hold line a bit to be seen by "Tower". It is to do with hold nodes not placed correctly. You can fix them with an afcad utillity any airports that have this problem. RC4 is seeing you correctly, just not at the holding point that has a mis placed node.CheersJulian

Hi RayThis also happens at EGLL (simwings) at 27L (Right Holding point) . For example, you need to move over the hold line a bit to be seen by "Tower". It is to do with hold nodes not placed correctly. You can fix them with an afcad utillity any airports that have this problem. RC4 is seeing you correctly, just not at the holding point that has a mis placed node.CheersJulian

Hi Julian,I have the same Heathrow scenery. I am aware I need to taxi right up to the holding point but always get recognised by TWR.I still don't know if Bob's problem is limited to KSEA or if he has the same problem at other airports. I'd like him to try a default airport just so we can eliminate 3rd party scenery.

It has been my experience where hold points (particularly ILS) are on an angled taxiway entry into the runway they are further back from the runway edge to allow wing clearance. This goes beyond the acknowledged boundary.The other thing is that on large airliners the forward view from a high cockpit somewhat distorts the perception of where nose is and you have to pull up closer to the hold line.

Hi Julian,I have the same Heathrow scenery. I am aware I need to taxi right up to the holding point but always get recognised by TWR.I still don't know if Bob's problem is limited to KSEA or if he has the same problem at other airports. I'd like him to try a default airport just so we can eliminate 3rd party scenery.

Hi Ray,I wonder if I have a double afcad then for egll, ( or an outdated one) . I better invetigate that. There was one other airport I had to move to the threshold to get recognised on radar, not sure if it was KJFK FSDT) or KSEA (default). For default airports I use Ray Smith's afcads, and they are usually as a rule, trouble free.Will get back to you on this.CheersJulian

It has been my experience where hold points (particularly ILS) are on an angled taxiway entry into the runway they are further back from the runway edge to allow wing clearance. This goes beyond the acknowledged boundary.The other thing is that on large airliners the forward view from a high cockpit somewhat distorts the perception of where nose is and you have to pull up closer to the hold line.

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

Hi Ray,I wonder if I have a double afcad then for egll, ( or an outdated one) . I better invetigate that. There was one other airport I had to move to the threshold to get recognised on radar, not sure if it was KJFK FSDT) or KSEA (default). For default airports I use Ray Smith's afcads, and they are usually as a rule, trouble free.Will get back to you on this.CheersJulianI 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