Why the heck is navigation around the core so crappy?

kris44dad · Aug 6, 2015

I'm exploring around the core (fastest route) and the game seems unable to plot a course longer then 100LY. Why the heck is that?
I'm running an i7-3930K @3.2Hz with 8GB RAM, and a Radeon HD 6800 series card. I'm 1,000 lights years away from the core. I should be able to jump there in about 30 minutes, but it takes 5 minutes just to plot a course 1/10 that far.

This sucks.

CMDR StackOfCups · Aug 6, 2015

Aren't there significantly more systems near the core? I would imagine this would cause the pathfinding some more trouble than usual.

EUS · Aug 6, 2015

because this: https://forums.frontier.co.uk/showthread.php?t=151389

kris44dad · Aug 6, 2015

I would suspect the same for that reason. The question was largely rhetorical. I was complaining that the system does not work well near the core. Even though you're a short distance away, it takes forever to get there. Their algorithm needs work.

IronGremlin · Aug 6, 2015

Yeah, and it has improved substantially.

However, it's a sophisticated problem.

What I'd dearly love to see instead is the ability to calculate a route based on a manually set jump range limit, which I think would probably be easier to implement and have wider reaching impact.

Calculation would get a lot easier if you could just tell it to only count systems inside 7 lightyears, and I could also more easily plot interesting routes elsewhere.

Dr Black · Aug 6, 2015

Maybe FD are unable to fix it.
Maybe FD are unwilling to fix it.
Maybe FD do not want to fix it.
Maybe FD do not give a hoot.
Maybe FD do not need to fix it as it is cost neutral.
Maybe FD do not worry about the few explorers that this affects. (yep that is the one)

Rauminen · Aug 6, 2015

Because the number of stars is too damn high!

knowles2 · Aug 6, 2015

Dr Black said:
Maybe FD are unable to fix it.
Maybe FD are unwilling to fix it.
Maybe FD do not want to fix it.
Maybe FD do not give a hoot.
Maybe FD do not need to fix it as it is cost neutral.
Maybe FD do not worry about the few explorers that this affects. (yep that is the one)

or may be FD haven't figured out how to fix it yet.

EUS · Aug 6, 2015

The "fix" for navigating in the core is given already. Thanks to Esvandiary for all his hard work in figuring it out.

kris44dad · Aug 6, 2015

I think one of the previous comments I heard was the correct one. Sometimes it's better to have a less than optimal path for the sake of calculation speed. I noticed it takes exceptionally long if you're mapping the fastest route, and not the most economical one. One of the routes i charted twice, and the fastest route took much longer to chart.