You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I accepted the contract to point a dish at the outer planets, but hadn't taken any steps towards completing it yet. Some time passed. Then I got a message that the contract had been completed, which surprised me. I went to mission control and examined the contract to see which vessel qualified, and was surprised to find that a vessel with zero communications dishes was identified.
I don't know what data or log files would be useful for tracking this down. I can provide save files, .craft files, log files, etc but don't want to spam you with all that until I know what is actually desired.
The text was updated successfully, but these errors were encountered:
Let's start with a save file, and a screenshot of the tracking station showing the RemoteTech stuff (the dish/omni lines). Hopefully that'll be enough to diagnose this one.
As requested zipfile contains save file and screenshot (screenshot 19) of tracking station. Also screenshotted are the completed contract description (screenshot 16) and a view of the vessel that the contract said was responsible for completing it (screenshot 17)... as you will be able to see the vessel has no antennae nor any remotetech connections showing on the tracking station view.
I accepted the contract to point a dish at the outer planets, but hadn't taken any steps towards completing it yet. Some time passed. Then I got a message that the contract had been completed, which surprised me. I went to mission control and examined the contract to see which vessel qualified, and was surprised to find that a vessel with zero communications dishes was identified.
I don't know what data or log files would be useful for tracking this down. I can provide save files, .craft files, log files, etc but don't want to spam you with all that until I know what is actually desired.
The text was updated successfully, but these errors were encountered: