Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The game will always default to the fastest route (which, mind you is not the same as the "shortest") as in the one that takes less in-game days to reach the target.
Now, let's say you want the fleet to move one system away but the starting position is on the other side of the star system and the target position is on yet the other side of the target system; your fleet would have to travel through the initial system, then jump, then go through the second system until it reaches the target position. All of that takes time.
Depending on the position of the gateways relative to the start position and the target, the length of the lanes and even local conditions, it's absolutely plausibile that the longer route is, in fact, the fastest.
And the AI will always, always, choose the fastest route, even if the difference is only a couple of days and even if that route takes the fleet through a guardian system (unless you've selected evasive stance beforehand).
I'll leave you to your comfortable certainty that precludes inconvenient information.
Were you at war? FTL inhibitors?
You can go into that system, and at the bottom tab click the line, or whatever it is to red out the system. Ships will now no longer use that wormhole or whatever gate is in the way. Altering the route.
Mind you this may still not stop the ships from supposedly 'glitching out' as you put it in your terms. Disable culprit mods. Could be a bug in latest patch but I couldn't care less.
I'll be waiting to see how troll this thread is. Your post is so cookie cut its breaking the immersion of my ability to believe your sincere.
I had this "bug" a couple of times, and all I could guess was that at some time, total sublight route was much shorter this way than the one that would cross only one star sytem, because jyperlane egress points were very close to each other. Hence, the pathfinder proposed me to fly through two systems before reaching my target instead of directly flying to the targeted adjacent system.
I gave up gathering evidences for this hypothesis, however, so I can't rule out that it is actually a bug.
Just gotta say that military ships cannot use evasive stance.
Also you should lock down any dangerous systems with that restriction button in the local star system interface
I just wish there was an override of the behavior with a modifier key, like [Ctrl+C], to force taking the shortest route as the space crow flies.
for the rest it's usually fine.
as an aside have you tried simply right clicking the arrow at the edge of the solar system and giving the travel to command there? doubt it'll help but who knows.
if you have mad OCD you can simply temporarily restrict all other routes to force the behavior but you know then you are spending a lot of real world time to save a little bit of in game time.
That is true until hyper relays. They will take those no matter what. You could be sitting on a hyperlane jump point to the system you want and have a hyper relay on the otherside of both systems they will still travel the entire star system take and take the hyper relay to the neighbouring system. IT"S BROKEN. Other then that case yes you are correct.
I need to take screenshots.
It would do that though if it then took a hyper relay to the destination it over prioritizing those.