HiI'm having this problem that when I taxi to the runway, I se AI taking off, but when I'm at the holding point as number tree, the first one takes off, but the in front lines up and gets the clearence, but never starts

HiI'm having this problem that when I taxi to the runway, I se AI taking off, but when I'm at the holding point as number tree, the first one takes off, but the in front lines up and gets the clearence, but never starts

thanks jd. I have interact with ai enabled. I will try to rebuild this evening. But what is strange is that the first one takes off.

All airports or just one. If one and it is default, which one?Rebuilding the scenery library insures the correct location of runways and taxiways, etc., so RC has the exact location of these elements in its database.RC 4 would not be controlling AI in front of you in a take-off situation. Is there any AI on an entry holding point taxiway across from the stuck AI? Are any AI on approach?Make sure you have the current FSUIPC 4.53 from the link at the forum top as well as the latest makerwys before rebuilding your scenery folder,plus the following link:http://fsuipc.simflight.com/beta/FSUIPC4537.zip which fixes some issues in 4.53 regarding AI traffic.And, just to verify, you are using Ultimate Traffic FSX, not Ultimate Traffic II, correct? There were some issues within UT II.While available for FS9, there is a traffic zapper feature in FSUIPC which I'm not sure it is available for FSX that allows you to delete an aircraft in front of you by assigning a hot key to thios function. You'll have to check the FSUIPC 4 user guide. This would only be a temporary fix.A couple of other suggestions:1. To see how other AI are operating go to a wide overhead view. See if anything is stuck on the runway.2. If you want to look at a status list of AI around you, run Trafficlook.exe in your FSUIPC install folder. This will open a separate window with a grid that looks like a spreadsheet that you can alt-tab to from FS. It will list AI in the air, ground, or both and the location and status of each. You can sort the order of entries by clicking on the column header.If your AI queued for take-off is stuck due to a string of landing aircraft, you might want to investigate a freeware utility called AI Smooth that will let you specify how far to separate landing aircraft. aismv120.zip is available on flightsim.com and avsim.com. This version is for FS9 and FSX and includes a user guide.

RC 4 would not be controlling AI in front of you in a take-off situation.

Unless I'm seeing things RC is "controlling" AI in front of me in the take-off queue. Isn't it true that RC freezes AI (if only for a second or two), so that the AI based chatter doesn't seem delayed? I've been into AI for years now, I know the flow of the FS AI engine, so I noticed it immediately, when an AI aircraft was frozen for an instant. Definitely when it is told to line up, but perhaps also when it is told to take-off.I'm currently in the take-off queue at KCVG (36C, set for take-offs only), early morning rush hour and AI were taking off fine, one after the other. There were like 7 aircraft still in front of me, when all of a sudden a departing AI got stuck. It was lined up and ready to go, but then nothing. Now, I wasn't paying that much attention, so I don't know if it was cleared to take-off already, but it's stuck differently than normal, as I've already seen AI aircraft nearest the runway time out, because the stuck aircraft is there.And because it is still there way after the normal time-out period, I'm inclined to say RC is the culprit. And it's not like this is an isolated incident, I've seen it happen at other airports as well. And yes, the database is up-to-date.I'd turn off AI interaction, but I prefer AI chatter as opposed to the prerecorded chatter and I can't seem to set the former independently from the interaction option. Which is strange, unless... RC needs to freeze AI for the chatter not to appear delayed...I'm new to RC and like it so far, my adventure with PFE was not a success, but this take-off problem is just that, a problem.:(

If you are using AI Smooth turn off Respond To User Aircraft and also ATC comms in its settings. Interact with AI in RC should be on as it does some enroute separation and when the user aircraft is landing within about four miles from the threshold it freezes AI from encroaching onto your landing runway.In some instances due to dense taxiway traffic landing AI stalled on the runway or exit taxiway too close to the runway freezing an AI lined up for take-off. If it happens at a specific airport it could be a broken taxi link in its AFD file. If on FS9 you can use AFCAD to check the airport with its fault finder tool. FSX and FS9 users can use ADE9X which has similarities to AFCAD for checking puposes.For an immediate relief of AI stuck in front of you FS9 users can use the traffic zapper utility. Check the FSUIPC user guide. I think it works with the RC registration of FSUIPC.In FS9 without RC running I've seen stalled AI on take-off caused by AI on a parallel taxiway. The aircraft radius in its aircraft.cfg was set too wide and it extended too close to the runway. Turning Crash Protection off in FS might help.FS9 users should turn off FS ATC Comms by putting in the General section of FSUIPC.ini (back it up, first) RemoveATC=Yes . This will not affect FS control of AI.

If you are using AI Smooth turn off Respond To User Aircraft and also ATC comms in its settings. Interact with AI in RC should be on as it does some enroute separation and when the user aircraft is landing within about four miles from the threshold it freezes AI from encroaching onto your landing runway.In some instances due to dense taxiway traffic landing AI stalled on the runway or exit taxiway too close to the runway freezing an AI lined up for take-off. If it happens at a specific airport it could be a broken taxi link in its AFD file. If on FS9 you can use AFCAD to check the airport with its fault finder tool. FSX and FS9 users can use ADE9X which has similarities to AFCAD for checking puposes.For an immediate relief of AI stuck in front of you FS9 users can use the traffic zapper utility. Check the FSUIPC user guide. I think it works with the RC registration of FSUIPC.In FS9 without RC running I've seen stalled AI on take-off caused by AI on a parallel taxiway. The aircraft radius in its aircraft.cfg was set too wide and it extended too close to the runway. Turning Crash Protection off in FS might help.FS9 users should turn off FS ATC Comms by putting in the General section of FSUIPC.ini (back it up, first) RemoveATC=Yes . This will not affect FS control of AI.

make sure you have the latest makerwys.exe installed, and you have clicked the rebuild rc scenery database button after any scenery changesjd

If you are using AI Smooth turn off Respond To User Aircraft and also ATC comms in its settings.

I do not use AI smooth.

In FS9 without RC running I've seen stalled AI on take-off caused by AI on a parallel taxiway. The aircraft radius in its aircraft.cfg was set too wide and it extended too close to the runway. Turning Crash Protection off in FS might help.

Is turned off. And an aircraft's radius is actually saved in the .mdl file.

FS9 users should turn off FS ATC Comms by putting in the General section of FSUIPC.ini (back it up, first) RemoveATC=Yes . This will not affect FS control of AI.

Already taken care off.

If it happens at a specific airport it could be a broken taxi link in its AFD file.

Well, no. If literally dozens of aircraft can taxi to and take-off from the runway just fine, then there's nothing wrong with the Afcad.

make sure you have the latest makerwys.exe installed, and you have clicked the rebuild rc scenery database button after any scenery changes

4.42 and I do.

In some instances due to dense taxiway traffic landing AI stalled on the runway or exit taxiway too close to the runway freezing an AI lined up for take-off.

It's a take-off only runway, with two true parallel landing only runways on both sides, so FS should not land traffic there anyway and did not in this case. Also, the AI aircraft in this specific example was already lined up and ready to take-off. Normally, if the runway is still "occupied", the AI aircraft will not be allowed to the enter the runway, but will simply time out at the hold short node. That's one of the gripes against the AI engine, the runway must be completely vacated in order for an aircraft to enter it. (A runway is considered vacated as soon as an AI aircraft (its contact points to be precise) crosses the runway edge. Ideally, the AI engine would allow a departing aircraft to taxi into position as soon as a landing aircraft is a safe distance past the threshold.

For an immediate relief of AI stuck in front of you FS9 users can use the traffic zapper utility.

That's fine for one aircraft stuck in front of me, but there were 7-ish aircraft in front of me in the queue, when the one aircraft decided to get stuck on the runway (or when RC forgot about it?). I'm not gonna zap them all, that ruins the realism. I let them all time-out this time (not much better), only the stuck aircraft remained, I zapped it and immediately RC told me to line up. I did, was told to take-off and did. Behind me were dozens more AI and from what I could hear, they continued normally.So this is a very peculiar issue and I've never seen anything like it.:(

Any chance AI landing on 36L would be crossing the end of 36C on Taxiway A and maybe stuck there?Parking was not overloaded, was it?The next time you use KCVG try running TrafficLook and if things get funny alt-tab to it. It no longer comes with FSUIPC but is available here:http://forums.simflight.com/viewtopic.php?...0bb17d5f103fb10It loads down FS less than the MS SDK Traffic Toolbox. Just alt-tab to it.And then you can run the RC log as well if you think you'll be in the same situation.

Any chance AI landing on 36L would be crossing the end of 36C on Taxiway A and maybe stuck there?

Not very likely, all runway crossings are made in such a way that AI aircraft will always cross and never be stopped. Besides, it was the morning departure rush hour, very few flights were actually landing, most of which happened on 36R to boot.I wonder, would RC do something with a landing aircraft crossing 36C? Or does it only keep a runway clear when the user is about to land?

Parking was not overloaded, was it?

Depends on what you mean. It was busy, most of the coded parking spots were in use, certainly with DALX traffic, but there were plenty of overflow parking spots still available. And a lot of traffic was heading to 36C, so there definitely wasn't any shortage of parking spots. And even if there was, arriving traffic would simply disappear shortly after landing. A departing aircraft would not get stuck like it did.And again, I've never seen this behavior until I started using RC and I've been runing 100% customized AI traffic for years. I've seen some crazy things, but departing AI traffic is always dependable, provided you have a properly working take-off only runway. Which was the case here. And I also leave the sim running for 15-20 minutes before I actually get going.

The next time you use KCVG try running TrafficLook

I use it extensively, great little utility. It would've probably indicated a take-off mode for the aircraft in question. I wonder what it would say if an aircraft is "frozen".

And then you can run the RC log as well if you think you'll be in the same situation.

I definitely will, I'm curious as to what kind of info is in there anyway.

The log contains the AI traffic tables every time during a polling sequence. It looks for key activations, states RC commands and actions, queries, and so forth. It shows in summary a number of states constantly being updated. It can be very huge and take a long time to load in a word processor.It shows the RC version, flight plan, scenery rebuild activities, - it all depends on when you start it.Each polling event has a sequence number associated with it once you have activated RC. By looking at the actions associated with the flight you can get an idea of where you are. It will tell you what phase you are in.I have not used the RC4 log for quite some time so I can't tell you what specific actions are recorded.The only RC4 AI freezing capability is during the landing phase. During final it can slow AI in back of you (via a skewing technique) so they don't run you over but I wouldn't try landing a C-152 at normal landing speed in front of any twin-prop or bigger :)The only other skewing technique used is enroute AI traffic avoidance.You'll have fun looking at the log. It will cause a lot of disk activity and CPU activity due to its time slice polling. For this case shut RC down after you roll and lift off. Then rename the log since you might want to save it and not have it overwritten.

The only RC4 AI freezing capability is during the landing phase.

An AI aircraft taxies to the hold short node of the departure runway, if the runway is free, the AI engine will allow the AI aircraft to taxi into position. As soon as the green light for that is given, the AI turns on its strobe lights and will taxi onto the runway, then come to a complete stop and then take off. (The strobe and (other) lights are a great indicator of the state of an AI aircraft.)I've just done another flight and I was right behind an AI aircraft, so I was in an excellent position to observe. It arrived at the hold short node. The AI engine decided it was all good, so the aircraft was told (by the AI engine) to taxi into position, it turned on its strobe lights and moved slightly, at that point a freeze occurred. A second (as in a unit of time), two, maybe three. Almost simultaneously then, RC's AI based chatter was played back and the aircraft was unfrozen. This to create the illusion that RC is controlling AI and that RC's AI based chatter precedes the AI aircraft's movements, not follows.But it doesn't end there, it was unfrozen and it continued taxiing into position. Then it was frozen again! RC played back the take-off clearance, it was unfrozen, the aircraft continued some more and only then came to a full stop as it would normally do. And then it took off.Two clear interventions by RC during the take-off phase. Unfortunately, I've not been able to find evidence of this in the log, but I did find an interesting paragraph:

<freeze_departure_ground_ai> 							freezing -520			   N477DM rwy  182 </freeze_departure_ground_ai>

That was also during the take-off phase as I was still on the ground and taxiing into position. N477DM was a GA aircraft behind me.Anyway, I have no problem with this RC practice, unless an aircraft gets stuck of course... In which case it might be a good idea to build some kind of time-out feature into RC. User configurable, in minutes.IMHO, the stuck aircraft from my earlier experience was frozen for the second time, the take-off clearance may or may not have been played back by RC (I don't know for sure) and then RC forgot to unfreeze the aircraft for some reason, perhaps it was just too busy, that would explain why I saw something similar at EGLL during a departure frenzy there. That would also explain why it didn't time-out like AI normally do, it was not under the control of the AI engine, but of RC...Taking a wild guess, RC probably recognizes AI state changes. Perhaps the first freeze in the departure process is based on the Take-off 1 state, second freeze on take-off 2?! I don't know, but it... something is happening.:(