Postby Cometborne » Mon Apr 04, 2016 6:41 am
One thing I know that can cause the effect of the ship decelerating "with no apparent reason" is crossing asteroid belts in SC, these do not show up on the scanner in SC. I managed to verfiy the theory once by doing an emergency exit, and found myself near asteroids. However, the repair bill for that action was big, and if I had been a little faster, it may have been insurance screen time.
However, I am wondering why you try to keep speed in the blue section during SC. I have bound F1-F8 to the speed settings from 100% to -100%, and if the target is far enough away (>100 Ls is my rule of thumb), I just go for 100% throttle and then wait for the arrival ETA to drop to about 7 seconds. At that point, I go for 75% throttle, and then wait for the disengage ready message. If the target is close to where I drop out of hyperspace, I simply do 75% throttle all the way.
The point where you need to throttle down depends a little on the ship type, big ships like the Python I am currently flying or the Type 7 I used for CGs do well on 6 seconds; with the Cobra Mk III I used for most of my earlier playing, I already had to throttle down at an ETA of 8 seconds.
This "75% at 7 seconds" methods works well both for approaching stations and approaching planets and moons for detailed scans. It may look a little scary at first, but it works. However, it does not work that well if you want to do a planetary landing after a long SC run, I am still experimenting to find a good approach for this.
Dirty deeds done dirt cheap for reasonable prices