FSD Arriving in the correct place

Its been a while since I went out of the bubble (DWE) but last night I did a 100+ jump trip and noticed something odd.
At every single system I arrived in, the next system was behind the star, never sometime behind me like it used to be. That means we are now arriving at the "correct" point around the target star.
When did this come in ? It drastically improves scooping efficiency to the point that I am wasting time far too often.
 
Fly a zig-zag route :)

More seriously, if you just turn and head out sideways (rather than curving around the star) you'll clear the star to the point where you can jump pretty quickly. Somebody tested it in Beta and found it averages to about the same travel time.
 
In my opinion the new system brings pros for Anacondas and cons to ASPX

The sluggish Anaconda movement prevented it to be able to jump on FSD recharge in vast majority of cases anyway. Also it has a bad fuel consuption and many commanders like to undersize the tank anyway, so a sweepsccop in star corona was performed any jump anyway. Now you have next star conveniently aligned.

ASPX manueverability allowed jumping in the very moment FSD cooled down, and you could refuel every 6 jumps or so. The new system makes the ASPX loose few seconds on every jump, and it wouldn't need to scoop every star.

BTW with new achievable jumpranges we have, it's a little difference. Also since i can leap 55+ LY I like to take a good look at sys map and scan the main star anyway, so with Conda and my playstyle this new system makes me move sligtly faster.
 
The sluggish Anaconda movement prevented it to be able to jump on FSD recharge in vast majority of cases anyway. Also it has a bad fuel consuption and many commanders like to undersize the tank anyway, so a sweepsccop in star corona was performed any jump anyway. Now you have next star conveniently aligned.
It's not hard to hit the FSD with a Conda as soon as the cool down period finishes. But you will still be scooping at that point so you need to be heading away from the star to avoid frying - easy with smaller & cooler stars, requires practice with larger & hotter ones. If the next jump is behind a class F or higher star then you are definitely going to be delayed as it takes longer than the cool down period to get rid of the obstructed message.

It will still be possible to Buckyball in a Conda, but you'll need to use the route plotter to avoid the larger stars.
 
As I scan every star when I'm out in the black, this is slowing me down compared to pre 2.2.

How the heck is this slowing you down?

if you will arrive properly in relation to where you came from, so your destination, most often will be straight ahead allowing you to speed past and scoop a little and then jump? rather then maybe having to do a 180 turn to find next target?
 
How the heck is this slowing you down?

if you will arrive properly in relation to where you came from, so your destination, most often will be straight ahead allowing you to speed past and scoop a little and then jump? rather then maybe having to do a 180 turn to find next target?

Well as he said, he is scanning the star not speeding past it.
Which means he has to brake and then accelerate again, flying around the whole star. I concur with Allitnil, when buckyballing in a conda it makes a lot of sense now to avoid bigger / hotter stars.
 
Last edited:
Back
Top Bottom