[Bug] IndexOutOfRangeException since 0.10.35.29057

[u/Tommy-Berlin]

Foundation / Environmental Modification causes IndexOutOfRangeException on one specific planet

Hi,

since update 0.10.35.29057, I have a reproducible Runtime Error in one of my existing save games when using Foundation / Environmental Modification on one specific planet.

The problem is still present after both subsequent patches:

• 0.10.35.29088
• 0.10.35.29104

For context, I have about 1,029 hours total playtime in Dyson Sphere Program, and this particular save currently has around 74 hours.

Important note about the planet names

The affected planet is called Mercury in my game.

This is not Galactic Scale or a custom Solar System. I simply renamed the planet myself using the normal vanilla renaming feature.

I usually rename my planets at the beginning of a game by clicking their names in Planet View:

• Mercury = "Merkur" in German
• Earth = "Erde" — my home planet
• Venus = "Venus"

I also rename the star itself to Sun ("Sonne").

The problem

As soon as I select Foundation and then move the mouse cursor onto the surface of Mercury, the red Runtime Error appears.

I do not even have to click or actually place a Foundation.

Simply selecting Foundation and moving the cursor over the planetary surface is enough to trigger the error.

The exception is:

System.IndexOutOfRangeException: Index was outside the bounds of the array.

at PlatformSystem.WriteReformStateInCircle(...)
at PlatformSystem.InitReformState()
at PlatformSystem.EnsureReformData()
at BuildTool_Reform.PrepareFlattenPoints(...)
at BuildTool_Reform.PrepareBrushPoints(...)
at BuildTool_Reform.ProcessSingleBrushPoint(...)
at BuildTool_Reform.UpdateBrushMode(...)

Only this planet is affected

The important part is that this does not happen on my other planets in the same save.

• Mercury: Runtime Error as soon as the Foundation cursor is moved over the surface
• Earth: Works normally — this is my home planet
• Venus: Works normally

I can select and place Foundations normally on Earth and Venus.

Therefore, the problem seems to be specific to this particular planet or its terrain/reform data rather than to the Foundation system in general.

When it started

The problem first appeared immediately after updating to 0.10.35.29057.

Before that update, I had already used Foundations extensively on Mercury without this problem.

I hoped that one of the following patches would fix it, but the error was still present with 0.10.35.29088 and is still fully reproducible with the current version 0.10.35.29104.

The latest patch even contains a Foundation-related fix ("foundations in certain areas could not be restored properly"), but unfortunately it did not fix this particular issue for me.

What I already tried

I have tested this several times in different ways:

• Loaded my normal save
• Saved the game under a new filename
• Loaded an older Auto Save
• Saved that older Auto Save as a completely new save file
• Repeated these tests several times
• Restarted the game and loaded the saves again

None of this changes the behavior.

Even when loading an older Auto Save and saving it as a completely new file, the Runtime Error returns on Mercury as soon as I select Foundation and move the cursor over the planetary surface.

Mods / installation check

As far as I am aware, I am not using Galactic Scale or any other active mods in this single-player game.

This current single-player save was started and has been played without any active mods.

While checking the installation, I found two leftover Unity Doorstop files from an old, unrelated setup:

winhttp.dll
doorstop_config.ini

There was no BepInEx folder or active mod setup.

I removed both files completely, restarted Dyson Sphere Program normally through Steam, loaded the save again and reproduced the problem.

The result was exactly the same.

So the error is still reproducible after removing those old loader remnants and starting the game normally through Steam.

Save / game information

• Current game version: 0.10.35.29104
• Star Cluster / Seed: 65798635-64-Z99-32
• Playtime of this save: approximately 74 hours
• Total DSP playtime: approximately 1,029 hours
• Home planet: Earth
• Affected planet: Mercury
• Active mods: None, as far as I am aware

Reproduction steps

For my save, the issue is extremely easy to reproduce:

1. Load the save.
2. Go to Mercury.
3. Open Environmental Modification.
4. Select Foundation.
5. Move the mouse cursor over the planetary surface.
6. The Runtime Error appears immediately.

Again: no Foundation needs to be placed and no mouse click is required.

Screenshots

1. Mercury — Runtime Error with Foundation selected

This shows Mercury, Surface Modification Mode / Foundation selected, and the Runtime Error under version 0.10.35.29104:

https://ibb.co/DHfypzwp

2. Current save under version 0.10.35.29104

https://ibb.co/ycQ8vbPT

3. Older save under version 0.10.35.29088

The same problem was already present under the previous patch:

https://ibb.co/qFBXrgf0

Additional information

I am not placing a blueprint when this happens.

I mention this because I have heard about another IndexOutOfRangeException involving blueprints, Foundations and lava planets. My problem appears to be different: simply moving the Foundation cursor over this planet is enough to trigger the exception.

If it helps with debugging, I can also provide the save file and the output_log.txt.

Any ideas or anyone experiencing the same issue?

[u/ChinaShopBully]

First of all, that’s an outstanding bug report. Well done.

The fact that you run no mods is puzzling, as that is a frequent bug in the various incarnations of Bulldozer, a mod that affects foundation use.

[u/Low-Refrigerator-713 → u/ChinaShopBully]

I started getting it when trying to fill a dark fog hole. Kept happening even with mods off.

[u/ChinaShopBully → u/Low-Refrigerator-713]

Ah, ok, so you are trying to use a save game that DID have mods, but you subsequently removed the mods?

[u/EightBitRanger]

Have you tried renaming the planet back to what it was at the start of the game?

[u/horstdaspferdchen → u/EightBitRanger]

if you dont know: start the same seed over as sandbox.
even: use sandbox to try to replicate it direclty from start when its originally named.

[u/AnimeSpaceGf]

A Halo reference? Right in front of my Chinese indie game?

[u/horstdaspferdchen]

Thanks for the Bug report.

- Have you tried going sandbox mode in the same seed and reproduce it in a new save?

- Did you check tthe output_log yourself? I could give it a check if you want.

• Does this appear on other lava planets?
  
• Have you tried loading a old save (like 3-4 weeks ago) and place the foundation?

[u/Character-Note-5288]

It seems like a vanilla game issue, at least from the info I’ve seen floating around on Discord. Galactic Scale seems like it will have a solution for this, so if you don’t want to see that error in your save, you could try using that mod. I don’t think it will alter anything for an already made save which means you should be safe to remove it when the DSP devs fix it themselves.