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'm not normally advocating for self-help measures, but this seems like it might be worth the trouble :) Hang on a sec
First things first
Submit a feedback entry via F8 and include your latest save with this issue. Kevin needs his data :) You can type in the following in the notes
logData entry
"showMapPin": true,
(...)
"summary": "\"<i>You can rotate a module prior to placement by pressing [A/D]. Asymmetric...</i>\"",
.
.
.
So I can't guarantee that some tutorial-related flag failed to set ; if that affects your future progression, that may not be ideal. But I can get rid of the map item for you.
1. Resave your game in case you need your prior save, for some reason
This fix won't need you to quit the game (just dart back and forth between the game, the OS, and a text editor)
2. Find the affected re-save, and back it up
Saves should be in your
%username%\AppData\LocalLow\Wx3 Labs, LLC\Starcom Unknown Space\saves
if you're using Win10, for example
Copy all five files corresponding to that save
i.e.
.json
.png
_info.json
_FOE1.png
_FOE2.png
to some other location temporarily
The reason I recommend saving again and then editing the re-save is this:
the _info.json contains metadata about the save, so if you duplicate the save at the file level and then don't also edit the metadata file, the save points to the old save file.
3. Select the save's .JSON file (the biggest of the five, usually a megabyte or more) and edit it
This has the key "shipLogData" which contains all your log entries.
(you don't need to understand JSON keys, values, arrays, etc. to do this, but it helps)
4. I searched for the offending entry on your map screenshot and found (in my file, at least),
"shipLogData": {
"index": 45,
"entries": [
.
.
.
{
"id": bla,
"type": bla,
"gameTime": bla,
"coord": {bla bla bla}
"showMapPin": true,
"spriteId": "DEFAULT.Portraits/STARCOM_ENGINEER",
"categoryText": "Lt. Milton",
"summary": "\"<i>You can rotate a module prior to placement by pressing [A/D]. Asymmetric...</i>\"",
"intro": "<i>Walker</i>: 2641.11.18 04:35 at 5.50 x 5.50 Unknown Space, Crew Log Entry",
"details": "Lt. Milton:\n\nYou can rotate a module prior to placement by pressing [A/D]. Asymmetric modules can be mirrored by pressing [X]."
.
.
.
]
}
So this is the log entry relating to that dialogue. The 'id' key identifies the unique log entry, and the matched braces enclose the log entry 'entry' as a data object. So long as we don't edit the wrong entry we should be fine.
Yours appears to have a showMapPin key set with the value 'true'. I tested this, and the value doesn't normally appear as true in my early games. Also, it popped onto the map the moment I loaded the save with the value changed to 'true'
5. Edit that so that the key:value is "showMapPin": false,
6. Save the file
7. Load the edited save
and the pinned map comment should disappear.
IF everything looks good (your ship is intact, your research tree is as it should be, all your missions are completed or in-progress as you remember them) then I think you're safe to proceed from this revised save.
8. Resave the game again through the UI to ensure the new(est) save data is clean.
Hope that helps!
That's handy :)
And, to be fair, I was trying to figure out in my head how that variable would ever get set like that.
Ohhh, brilliant!
I wouldn't have had any problems with editing save files (because in my case, I actually do understand JSON ;) ), but this makes it way easier.
Thank you - this is actually quite a neat feature that I totally missed. Worked like a charm