Hi RayI've just read one of the many posts about v4, go arounds, and AI on the runway etc etc....I have a great little flight from Brussels Int to London Heathrow and always get this problem.I am so looking forward to v4..... but the post did make me think...I start at Brussels around 8:15 am working towards a departure time around 8:30. Ultimate Traffic is set to around 85% to give me some hope of a landing slot at Heathrow.....Anyway...by the time I push back and taxi, there are lots of other flights either in the queue or taxiing to the active.Here's my question:Does V4 control the ground traffic and stop lots more of it joining the queue ahead of me, once I've contacted ground for clearance?Or is it first come first served as it is now?Hope this makes sense.RegardsMark

Mark,<>If only this was possible :-) Then again, if it was we could have a deluxe version of RC4 for a premium of course ;-) that always made you number one in the morning queue.The queing is frustrating at times. When I'm short of time I tend to use Toggle Ai Traffic (button command in FSUIPC) to instantly zap all the other traffic! But if you prefer the "real as it gets" scenario then I'm afraid you'll have to join the rest in the queue :-(One other thing. There's a great program called Ai Smoother that will help a lot with sorting out arriving traffic which will minimise the chance of go-arounds.Cheers,

Regarding AISmooth:If in its options (since release 1.00) if you have respond to user aircraft enabled, it tends to place all arriving aircraft in hold if you are anywhere near the runway. It tends to appear stuck and on take-off you may have to insure you don't have collision problems.I have it disabled and set incoming seperation at 120 or 90 seconds and it works well for me. The takeoff queue is still there but not as long as without using AISmooth.To the original poster:I highly suggest you install the TCAS on your panel that came with UT2 (unless you have another one in place) so you can worm your way around any aircraft in your path and also maintain your proper seperation (by speed control) when merging on arrival into AI Traffic. With AISmooth respond to user aircraft disabled, you lose the prevention of AI overtaking you on final. AI seem to do final at a higher airspeed than called for.The most dense airport I use regularly is KMSP but also use KLGA and KBOS all with dense traffic with AI set to 80% (UT2).Ray:Have you noticed if in AISmooth if respond to user aircraft is enabled, does it offer any prevention of ground AI invading the runway when you are on short final? I would not think so in this version.Also to the OP:Check out the freeware FSConfigurator. One of its features is the ability to increase taxi speed control for FS9 to get arrival AI off the runways faster to reduce your chances of a go-around.

Thanks guys....Both your posts are gratefully received. I'll check out both utilities.Thanks again :)Mark

Ronzie,Thank you for your suggestions re AiSmooth. The situation is slightly diferent for me because RCv4 doesn't clear you for departure until it's safe to do so. I also have to ensure that any changes I may make to external software does not affect my beta testing of RC.With v4 all aircraft awaiting departure are temporarily frozen so there's no chance of someone encroaching onto your arrival runway. And that's with UT set to 100% ;-)Cheers,

I was refering to V3.1. I would expect V4 to conflict with AISmooth or AI Seperator since all want to control AI in the local region.I just mentioned those as a temporary work-around until V4 is released at which point I would not be using AI Smooth but without Respond To User Aircraft enabled AIS just might be worth a check in its attempt to establish holding patterns at 30 to 40 miles out. RC 4 may be working at a closer range unless j.d. brings this kind of control into the mix further out.

Hi Ronzie,<< I would expect V4 to conflict with AISmooth or AI Seperator since all want to control AI in the local region.>>Well AIS controls aircraft a lot further out than v4 does so there won't be a conflict. I anticipate still using both once v4 is finished.Cheers,