Kerbal Space Program

Might be similar to #28207

If both DORV-2 Moon Dolphin 3 and DORV-2 Moon Dolphin 2 share the same persistent ID that might be the issue.

Do you have a quick save from the video?

How would my two crafts get the same Persistent ID? They have been launched on two seperate occassions.

I am trying to upload the safefile, but get an error every time i try to upload it here. The file is <20mb

Zip the file. that will cut it down quite a bit

awesome! Ok lets see if its happening as I suspect it is

Ah yeah i see!! Thank you for the awesome help both here, and last week with the saving problems i encountered. How do i make sure that the persistent ID's wont be similar? Is it a game bug or something that i do wrong?

Anth12 wrote:

Confirmed.

QA Manager: This might be more about that each craft should have a different Persistent ID than it being a problem with the Alarm

I just set my version to 1.5.1 through Steam and I'm getting the same behavior w.r.t. persistent ids. The same ids are also saved to the craft file (which is presumably how vessels launched at different times get the same id). I don't know what the persistent id is for, but it does not seem like it was ever intended to be unique per vessel. Vessels do have a separate "pid" which seems to be unique (they are valid UUID's anyhow).

Am I missing something?

I don't see the point in a persistent ID for a craft if its not unique when its in "Flight"

Anth12 wrote:

I don't see the point in a persistent ID for a craft if its not unique when its in "Flight"

The "pid" field is unique. I don't know what the "persistentId" field is for, but its presence in craft files would suggest that it's not a unique identifier for vessel instances.

Interesting. A persistent file I have from 1.3.1 has no persistent ID at all. but the pid is definitely there

And a craft file from 1.2.2 which has no persistent ID at all compared to the current version

Looks like persistent ID started being a thing in 1.4

• Can't switch
• Can't edit
• Linked vessel is changed to current on edit
• Time left for maneuver alarms changes to current on edit
• SOI changes to current on edit

There are probably other variations on this, but it's all to do with the Alarm Clock not being able distinguish between related vessels, as well as the AOORE problem reported by Anth12.

I have issues with this when I launch 2 identical vessels, especially if they have the same name at launch.

I use the same types of space planes, and have several nearly-identical probes going to other planets and the alarm menu's "switch to" button doesn't work well for them, often dropping me into the wrong craft.

Deepspeed wrote:

I have issues with this when I launch 2 identical vessels, especially if they have the same name at launch.

I use the same types of space planes, and have several nearly-identical probes going to other planets and the alarm menu's "switch to" button doesn't work well for them, often dropping me into the wrong craft.

The name is irrelevant. I describe the problem in the link below and what you can do to fix it.
https://forum.kerbalspaceprogram.com/index.php?/topic/203958-alarm-clock-is-broken-and-impacted-saves-cant-be-fixed-programmatically/