Has anyone here heard of the program AISmooth? It is a freeware program which will put the AI aircraft into holding patterns to space them out more on approach to airfields. You can customize the length of time between planes, distance at which incoming aircraft can be stalled for holds, etc. You as the user plane will never be told to hold, and theoretically AI planes will halt their approach and start holding if you come at them from behind.
In theory it all sounds great, and in practice it works out pretty well. I have seen some odd behavior, and also sometimes I still get traffic incursions which I must fix with the MS Traffic SDK's traffic explorer (which can delete specific aircraft from the airspace). IMO it's a pretty good solution to the go-around problem and makes STAR-AFCADs obsolete. Landing at major airports is now (usually) go-around free and also you will be landing at the correct runway according to the wind.
With AISmooth running I have modified my AFCADs to the standard parallel runway ops. One runway dedicated to takeoffs, the other dedicated to landings. For airports with multiple sets of parallel runways, I've made it so each pair has one dedicated T/O and one dedicated Landing runway. Airports with quad-parallel runways (like KATL or LAX) I have set up so the two runways on one side are a T/O+Landing pair, same for the other side. Basically they are paired up following the runway designations (25L/R, 26L/R, etc).
Using this setup, which was what everyone used prior to STAR-AFCADs (?), and how most non-STAR-AFCADs are setup (like the default FlyTampa OMDB is set up like this) and running AISmooth- the traffic is spaced out enough such that go-arounds are very rare on the dedicated landing runway. Takeoffs are very steady too with the dedicated T/O runway.
This seems more realistic to me since there are few go-arounds, and you do not have traffic operating on crossing runways which might lead to a collision. Anyways hope you guys understand what I am talking about

Ruahrc