I can fly a Cutter through the mail slot but there are times (kids are fighting, someone at the door, I need a beer, etc...) where it would be nice if I could use the advanced docking computer to leave a station. Currently when I use the docking computer to depart it reminds me of a drunk trying to get a key into a door lock. I bounce off the walls all around the mail slot. if you are running shieldless to maximize cargo capacity your ship can be totally destroyed by the repeated collisions with the wall. The docking computers work on all of my other ships. We bought these using a few credits. They should work.
Ooh - that might make sense. Is there a ticket open for this? Will see if I can close mine if so, reduce clutter.
I think there is a ticket but can't go looking right now. More than likely it expired of course...
Because Advanced Docking Computer has no issues.
The problem lays with the lateral and vertical thrusters which are weaker in 4.0 than in Legacy (3.8)
When they will fix the lateral and vertical thrusters, the ADC will work decent enough again
But this is Elite Dangerous!
As far asI understand it, the Thrusters only work at 50% in an instance with a landing pad present, FA on and rotational correction enabled. As the docking computer enables RC and FA on, this is where the issue becomes apparent the most.
If it helps to locate by giving you the critical phrases:
- The specific problem is with Rotational Correction
- It occurs while landing pads are present
- It reduces deceleration to a level similar or equal to having Flight Assist disabled (or rather, Flight Assist loses its enhanced deceleration)
It so does. Aside from docking computers "malfunctioning" the best solution for now is to make it a habit to check that RC is disabled whenever you don't need it. Luckily ED even has a bindable action for it, I have it on one of my hat clicks on my left stick. I enable it only once I am inside a rotating station and disable it immediately when leaving the toast rack. It is also one of the few COVAS voice prompts I have enabled so I don't have to check via the right-hand panel.
This works only if you fly manually 100%
Else, if you turn off the RC, the docking computer will turn it back on
And flying manually with RC Off works nicely anywhere not close to a rotating spaceport (Coriolis, Orbis, Ocellus, )
Of course. I mentioned the ADC turning it back on earlier. Me, I always fly manually. I don't think I even own a single docking computer module
. Also, I don't fly cutters, so I don't need them.That's what I am saying. I usually fly through the toast tack, realize my pad is turning away from me, and either correct manually or (more likely) turn RC back on. When I depart the rotating station, I turn RC off as soon as I leave the toast rack.
My traders/haulers always run ADC and i work around the issues by approaching the station properly - for starports i try to always come out of supercruise exactly in front of the mailstlot, same for carriers and megaship - so i'm not really affected except when i mess the approach or when autolaunching when i'm dualloging and i cannot supervise both accounts at the same time..
However, i really wish they fix the thrusters issues in 4.0
Because real pilots* don't fit an ADC.
I found that the auto-launch was terribly annoying, banging you about (even before the thruster issue) and taking an age to decide whether to try to fit through the slot. Manually lining-up is simple (they provided aids in the design) and so it makes sense to just take charge and not waste time while the ADC fiddles about.
* (Lazy ones like me fit a standard DC though.)
This is simply not fully true. In 3.8 the ADC also crashes cutters into walls, though it happens with a much, much smaller frequency.
as you said - much much smaller frequency
Same! That earned itself a stick-mounted button immediately, and I enable it only within seconds of touching a rotating landing pad.
If only! Since update 14, Commanders who are defending a port from Thargoid attack do not even get that prompt, because the Frame Shift Anomalies disrupt the COVAS over time until eventually it cannot speak at all. Needless to say, in that scenario it is critical to ensure that Rotational Correction is disabled and the panel is the only good method.
Oh yeah I forgot about that. Is the jury still out if that is a bug or a feature?
I recall no official comment, though to me personally it feels actually like a feature, given that the degradation is deliberate and gradual. I have to credit those responsible at Frontier—the COVAS glitch-effects have been presented very well. Insofar as it also eventually reaches silence, that also feels like an intentional design choice and definitely it follows the same theme as some other aspects of fighting Thargoids.
In this case, I can understand the design intention being for the COVAS to stop working and therefore that the solution for determining Rotational Correction is just to check the panel (or fly within the attacked starport and discover it that way). The only trouble arises from having to do it as a workaround outside of a rotating structure for an unrelated actual problem which obviously was not intended, especially when the port involved is just an outpost and very much not rotating at all.
I think I would have stopped just short of total silence, where the words are unintelligible directly but a few messages might still be identifiable from the occasional syllable, if one knows them well enough. For example, if changing the Rotational Correction makes the COVAS emit a S-sound at some point, that must be part of disabled.