Project

General

Profile

Bug #27241

Finish construction of a rover mission can't be completed

Added by sycorax 3 months ago. Updated about 2 months ago.

Status:
New
Severity:
Low
Assignee:
-
Category:
Mission
Target version:
-
Start date:
02/09/2021
% Done:

0%

Version:
Platform:
Windows
Expansion:
Breaking Ground
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

Finish construction of a rover KSP breaking ground no mod.
I needed to move the rover to the target. I drove it there, exactly on the spot and the mission didn't complete. I also reloaded the old save and moved it several times to that spot with no success.
Please fix the mission completion parameters.

sc.png (3.67 MB) sc.png screenshot sycorax, 02/09/2021 07:19 AM
quicksave #35.sfs (2.5 MB) quicksave #35.sfs sycorax, 02/09/2021 11:01 AM
at destination.sfs (2.52 MB) at destination.sfs rover at destination. [email protected], 02/18/2021 02:46 PM
56113

History

#1 Updated by Dunbaratu 3 months ago

sycorax wrote:

Finish construction of a rover KSP breaking ground no mod.
I needed to move the rover to the target. I drove it there, exactly on the spot and the mission didn't complete. I also reloaded the old save and moved it several times to that spot with no success.
Please fix the mission completion parameters.

Is there a chance you might have the same problem as in this bug?

> https://bugs.kerbalspaceprogram.com/issues/27222 <

These contracts are supposed to match an ID number mentioned in the contract with the ID number of the vessel it spawned, and they don't seem to be in agreement, which is causing this problem for several people.

Can you read that issue and see if it's the same? I'd like as many people to vote it up as possible because it's a big deal.

#3 Updated by sycorax 3 months ago

VESSEL {
pid = fb3349b8463743799f70929dc71dbc65
persistentId = 6247374
name = Unfinished Ike Surveyor ZCDT

CONTRACT
            {
guid = 2739215e-bc9e-428f-af52-c17ac51bf3f5
type = RoverConstructionContract
...
agent = Dinkelstein Kerman's Construction Emporium
...
bodyName = Ike
roverVslId = 2321460093

Yes, it seems to be the same problem.
I voted up.

Dunbaratu wrote:

sycorax wrote:

Finish construction of a rover KSP breaking ground no mod.
I needed to move the rover to the target. I drove it there, exactly on the spot and the mission didn't complete. I also reloaded the old save and moved it several times to that spot with no success.
Please fix the mission completion parameters.

Is there a chance you might have the same problem as in this bug?

> https://bugs.kerbalspaceprogram.com/issues/27222 <

These contracts are supposed to match an ID number mentioned in the contract with the ID number of the vessel it spawned, and they don't seem to be in agreement, which is causing this problem for several people.

Can you read that issue and see if it's the same? I'd like as many people to vote it up as possible because it's a big deal.

#4 Updated by [email protected] 3 months ago

Drove it to destination to confirm it and make bug tracking easier.

#5 Updated by ogaduby about 2 months ago

sycorax wrote:

Finish construction of a rover KSP breaking ground no mod.
I needed to move the rover to the target. I drove it there, exactly on the spot and the mission didn't complete. I also reloaded the old save and moved it several times to that spot with no success.
Please fix the mission completion parameters.

The issue is that the "roverVslId" value inside contract parameters does NOT match "persistentId" value of the vessel. You can help yourself and fix it by editing your persistent.sfs savegame file and replacing vessel's persistentId value with the roverVslId value of the said contract. Make sure you backup your save files before editing them.

I'd say this bug should be easy to fix. Your post just needs a bit more upvotes for devs to notice it.

#6 Updated by Dunbaratu about 2 months ago

ogaduby wrote:

fix it by editing your persistent.sfs savegame file and replacing vessel's persistentId value with the roverVslId value of the said contract. Make sure you backup your save files before editing them.

I think the safer edit would be to do it the other way around by leaving the vessel's persistentId as-is and instead edit the contract's roverVsId to match it. PersistentId is sort of the vessel's "primary key", while a contract's roverVsId is sort of a "foreign key", if you get my drift.

Also available in: Atom PDF