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
Did you choose a waypoint that was greater than 5km away and there was an obstruction 203.73 away so the game truncated your jump distance to prevent you from hitting the obstruction and then prohibited you from jumping such a short distance?
Space is big. It takes time to travel anywhere.
Ok, what I think is happening is that you are trying to do a blind jump of 1500km but the planet or an asteroid is closer than that distance. So the game truncated your jump to prevent you from hitting the object. The resulting distance was less than the 5km minimum jump distance.
I'm not saying you didn't find a bug. I'm just trying to understand what you did.
I set a waypoint 187 km away and then put myself behind an asteroid and got the same result as you. It told me my jump distance was too short and that their was an obsticle in the way.
When I move out from behind the asteroid it let me jump without issue.
Thus when any obstacle or natural gravity at the destination is detected, the jumps distance will be reduced.
In the image it is likely that when flying forward for just 203 m or even 2.2 km that you will end inside the natural gravity well already.
I'm 99.9% sure 2km won't get him into the gravity well, let alone 200m.
When you get into the gravity well, the planet covers 80%+ of your screen already when you are looking directly at it.
He may be well over 40km+ away from the planet. Something else is causing the issue rather than the planet itself.
I belive the distance is first truncated by the planet presence, and then something else is blocking the jump at the newly calculated destination. Or it's just a bug, more likely.