The rotational correction vs. thrusters issue exists but I don't think it's the whole story.
I fly with kb+m, meaning ED is usually the "focused" app on my desktop (running in borderless fullscreen). Apart from being a little bit drifty due to the thruster problem, the autodock/launch never randomly rams into stuff.
However if I'm using a web browser or other app and ED isn't focused, the docking computer is absolutely useless; it will plow head first into the nearest structure as soon as it takes control. I've tested this a fair bit, all I need to do is press the windows key while the docking computer is active (which unfocuses ED and pops up the start menu in the foreground) and it instantly goes off course.
You have to test this out.
I have to keep EDO focused for the Auto-Launch to work.
It's almost as if as soon as you focus on something else, the autopilot breaks the forth wall and goes "What you reading?" and takes it's eye of the ball.
I often dual-log 2 of my accounts while flying a shieldless lightweight cutter as long range hauler (50ly jumps empty, 35ly laden, 768t cargo). With ADC on, including at launch
So i alt-tab between clients as needed - and it's working quite nice for trading runs (and/or filling a carrier) with the help of ADC and SCA.
The Cutter will always bump the wall above the mailslot (or one of the sides) if the launch pad is on the front row (right near the mailslot) but not if the pad is mid station or in the back
The Cutter will also have an increase chance to get entangled in the geometry (due to evasive maneuvers) in the same scenario as above if it has to stay in launch queue and other large ships are passing through the mailslot.
I only lost a single Cutter due to this while letting the ADC to do it's job and me being alt-tabbed (one of the evasive maneuvers combined with the weak laterals lead to the Cutter hitting the station and getting entangled in the geometry)
Even with the client unfocused, the Cutter is getting out of the station, not with hull 100%, but it is getting out - but as i said, the deciding factor seems to be the pad location and not the client being focused or not (i play fullscreen)
However, i noticed a focused client seem to have an impact during the thargoid sensors / guardian stuff relogging CGs
In that period i used to have 2 clients running, each with a Cutter inversed holding steady at very low altitude above the sites and i was alt-tabbing between them.
Well, the unfocused client had a much higher percentage of collectors failing to pick up the stuff from the ground than the focused client (hard to be sure, the RNG had a stronger role i suspect)
It was an impression, but it definitely led to me waiting for the first batch of collectors to reach their targets instead of immediately alttabing to the other account, with the net effect of slightly longer times between "runs" but with better collection rate per limpet than otherwise.
