Kerbal Space Program

I am unable to reproduce. The asteroid is identical in screenshots taken before a quicksave compared to another taken after a load. Do you have mods installed? Could you please attach your logs?

The forum post indicates that this is related to older saves. Asteroids do not change shape following the reproduction steps in 1.3.1.

The workaround is to load the game in 1.3.0, go to the captured asteroid, undock, and save. When this save is loaded in 1.3.1 the asteroid can be captured again without causing problems.

No mods. As you say, it is an issue of importing save-files from older versions.

The file ARM_Asteroid2.sfs in a fresh install happens to be the same file as shipped with 1.2.0, and has a ModuleAsteroid having an 8-digit seed = 34614706, so it was just a convenient way to make a brief bug report. Quicksave produces a quicksave.sfs with the ModuleAsteroid seed = 3.46147E+07, and a peristent.sfs with seed = 8.588609E+07.

Version 1.3.1.1836-prerelease preserved the 8-digit seed. Some save-games have bases built around asteroids, which might be impractical to bring forward to 1.3.1

The issue is not restricted to older saves.

Saves and log in the attached AsteroidShapeSaves.zip made by these steps: ====
Version 1.3.1.1891; start new sandbox game.
Tracking station; Track 6 asteroids (first two have same name)
Rename the asteroids Alpha, Beta, etc.
Vehicle Assembly Building, launch stock Ion-powered Probe
Alt-F12/SetOrbit/Rendezvous with each asteroid in turn, screenshot, save, reload, screenshot.
Alt-F12/SetOrbit/Rendezvous back to Alpha, save.
Second visit to 'Alpha' shows a different shape than the first.
--
Load the save "AtDelta"; switch craft to asteroid 'Delta' using '[' ; quicksave.
The resulting quicksave.sfs that shows a different asteroid shape on each F9 reload.

I confirm this issue on 1.3.1 on Linux.

Asteroids do change when first loaded from 1.3.0 save.
The reason is the incorrect format in which ModuleAsteroid.seed is saved:
In 1.3.1 there's no KSPUtil.LocalizeNumber(int value, string format) method;
so when BaseListField.Save calls KSPUtil.LocalizeNumber((int)obj), the variant
with float argument gets called with implicit conversion:
KSPUtil.LocalizeNumber((float) (int) obj, string.Empty).
As the result the newly saved .sfs file contains this:

MODULE
{
    name = ModuleAsteroid
    isEnabled = True
    seed = 5.788284E+07            <===== incorrect format of the seed = 57882842 present in the original .sfs
    AsteroidName = Ast. N3559095
    prefabBaseURL = Procedural/PA_E
    currentState = 1
    stagingEnabled = True

Invalid integer value! Field seed, value 5.788284E+07 on object of type ModuleAsteroid
UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogError(Object)
PDebug:Error(Object)
BaseField:ReadPvt(FieldInfo, String, Object)
BaseField:Read(String, Object)
BaseFieldList:Load(ConfigNode)
PartModule:Load(ConfigNode)
Part:LoadModule(ConfigNode, Int32&)
ProtoPartModuleSnapshot:Load(Part, Int32&)
ProtoPartSnapshot:Load(Vessel, Boolean)
ProtoVessel:LoadObjects()
Vessel:Load()
Vessel:Update()

Thanks for all of the information and suggested workarounds. We have identified the problem and it is being addressed.

Squelch wrote:

The forum post indicates that this is related to older saves. Asteroids do not change shape following the reproduction steps in 1.3.1.

The workaround is to load the game in 1.3.0, go to the captured asteroid, undock, and save. When this save is loaded in 1.3.1 the asteroid can be captured again without causing problems.

I have a similar problem with a game I started with 1.3.1
I Use Linux
The versal name is Asteroid it is docket to the asteroid but now the asteroid locks different

Starting in 1.4.0 and still in 1.5.1, the save-file has an un-changing 'seed' written as an integer, and asteroids stay the same shape.