Kerbal Space Program

I can confirm - this just happened to me and is causing me to lose a contract and a lot of funds (I built a ship that could capture a Class A asteroid, but the mass of 150t is never what any Class A asteroid should be so of course I didn't build for that and the mission can't be completed.)

I first noticed the problem when the delta-V meter went from my ship having 1500 m/s dV to about 115 m/s dV as soon as I docked with the asteroid. The PAW claims the asteroid was only 2.5 tonnes and the resources on it were only 2.22 tonnes. But the actual part's real mass is 150 tonnes, despite the lie the PAW display is showing. I confirmed it was 150 tonnes by comparing the difference in my ship's total mass when docked to it versus not docked to it.

Since the problem will happen on ALL class A asteroids - I cannot complete the contract properly ("Land a newly discovered Class A asteroid on Kerbin") without building a ship that costs more than the contract reward (the reward thinks it's an easy task when it's actually very hard because of the 150t bug).

POSSIBLE WORKAROUND by editing game data files:
1. Make a backup of your primary save file.
2. In your KSP install directory, navigate to the directory {$KSP_ROOT}/GameData/Squad/Parts/Misc/PotatoRoid/
3. Make a backup of the part data file part.cfg.
4. Open part.cfg in a text editor. Around line 21, a section begins
21: // --- standard part parameters ---
22: mass = 150
23: dragModelType = default

5. Comment out the mass property on line 22 with two backslashes.
21: // --- standard part parameters ---
22: //mass = 150
23: dragModelType = default

6. Save and exit.

• Fly a craft attached to an existing Class-A/C asteroid. Assuming this asteroid did not already have the incorrect mass written to the save file, the asteroid keeps the expected mass.
• Dock with a new Class-C asteroid. As far as I can tell, the asteroid gets the expected mass.

@Dunbaratu, can you try this workaround and see if it helps your situation?

It happened on mine too. Definitely destroyed my mission. It shows that the asteroid is 3t but in fact it's way over 100t.

I also got this bug. As it was my first ever asteroid I was quite confused and I struggled for a long time before realizing it's mass was 30x larger than I thought. The work-around worked for me, and although it should be obvious I should note for others that a game restart is required.

Wow, over 3 months now... where does the time go.
I chose to just stop playing (I had a bunch of asteroid missions) and wait for the fix to come in, rather than patch the data. Turns out I've been waiting a lot longer than I expected :-S

This happened to me as well. Said mass was 2.7 tons when I right clicked on the captured asteroid, but my delta-v went from like 1000 to 50 and kerbal engineer mod said my ship mass went up by 150 tons.

I wasted 3 days trying to figure out why I was not able to complete the scenario only to find that this bug was causing all my headaches. I see now that update 1.10 has dropped without this being attended to.
Very frustrating indeed!!

This bug appears RESOLVED by the 1.10 update.

I was fully ready to come on and put Squad on blast if it was true this issue was not resolved in 1.10. However...

• Fix asteroids having incorrect mass when docking.

To verify this, I launched the game and docked with an undisturbed Class C asteroid under the 150t limit. The save file shows the asteroid mass is correct.

@Wolvyreen, the bugfix in 1.10 only stops asteroids being assigned incorrect mass from this point forward. If you docked with an affected asteroid before the bugfix, the incorrect mass has already been written to your save file. The bugfix does not automatically undo this (my guess is it would complicate the fix and risk unintended changes). If you want to fix an asteroid that already has the incorrect mass, you can try manually editing the PotatoRoid's mass property in the save file (make a backup first).

Any other users can confirm this issue is resolved?

tjandreas, Thank you for your explanation :-) That is indeed what had happened. All is good in the world again.

The fix for this bug has introduced a related bug in 1.10, #25730. Every asteroid in the game is affected.

tjandreas wrote:

The fix for this bug has introduced a related bug in 1.10, #25730. Every asteroid in the game is affected.

This hasn't been fixed on console yet.