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
I can select any system on any page of my Normal-game-discoveries and get correct indications for travelling there in my starmap.
Maybe reboot your game/steam will help?
I will try it again on my next session. Thanks!
Something is definitively wrong here.
The problem occurs when i try to set a waypoint to a system that is very far away.
If i select a system say 450 ly away, it wont set the waypoint. If i select one that is only 120ly away then it works fine.
Can anyone confirm they get this on their side as well?
My suggestions:
If you are using mods, try without them.
Delete the content of your SHADERCACHE folder and let the game reload the shaders upon the next gamestart (which might last a bit longer). steam-steamapps-common-NoMansSky-Gamedata-Shadercache
Verify the integrity of your gamefiles by rmb on NMS in your Libary-properties-local files (this might add the disabledmod.txt btw, if you are using mods)
I'm never going to go there mind you, it took 5 minutes to reach on max speed zoom on the galaxy map.
I dont use any mods. I will delete the shader cache as you suggested. Cant verify the files because i dont own the game on steam, i got it on GOG. Will find out if there is a similar feature on GOG galaxy.
thanks!
This works fine. I mean setting the waypoint from the discoveries list.
http://steamcommunity.com/sharedfiles/filedetails/?id=1256531866
The indicated path ends around 1k ly, so I would have to go to my selected destination in (a lot of) steps... not really recommended to travel long distances like that, as the game won´t show you the most direct routing based on your hyperdrive capabilities and forces you to make more (shorter) jumps. I think of it more like a "local area" navigation mode because of that.
Im about to delete the shader cache as you suggested earlier. I hope this works, because im all out of ideas on what to do next if it doesnt :(
It seems to be doing something different now. I set the waypoint on the discoveries list, go to the map, and when i select "Custom waypoint" there is a line to some system, but its not the system i selected on the list and the waypoint marker (the diamond shape) is not there.
My main interest in getting this feature to work, is that i somethimes want to go back to a system i previously visited, and finding it by looking at all the stars names on the map is a real PITA. So i figured i would locate it on the discoveries list, set the waypoint and easily find it on the map. But no luck.
I wanted to go back to a particular system that earlier i saw sold the upgraded freighter hyperdrive blueprints, but after several minutes of looking at the map, i just cant find it!
EDIT: forgot to say, i have not uploaded my discovered systems.
To test if its related, I uploaded one, then set the waypoint on the list, went to the map, but got the same result. The line points to another system, and at the end of the line there is no waypoint marker.
This is giving me serious problems. I actually took some notes on wich tech was for sale in wich systems as i ran a trade run, now i want to go back to buy some of those techs, and i cant because the stupid set waypoint feature on the discoveries list doesnt work.
Used a portal to travel to a system where i knew a capital freighter was sold, went back with the intention to travel there with my current freighter via a waypoint, again it dint work.
It works about 20% of the time, and there doesnt seem to be a pattern on wich systems it works, and on wich it doesnt.
I just cant figure out. No one here seems to have this problem. Maybe its a bug on the GOG version of the game? Its either that, or im missing something obvious, doing something wrong.
I just dont know what else to do.