Submit Feedback

[205.024] Planetary encounters can spawn inside dynamic entities (grids, asteroids, trees)

Digi shared this bug ago

Solved

Az4NJKp

You can tell from the gigantic grid spam that I did it intentionally =) but it did spawn by itself inside that grid spam, the grids were there before the encounter.

It would really suck if someone's landed ship or rover or anything that is not static got destroyed like this.

The spawn could do a simple check for entities within the radius of the prefab, it could delete floating objects if present and reroll if it hits a grid or character or asteroid (boulders), and of course ignore the planet itself.

To reproduce I changed PlanetaryEncounterDesiredSpawnRange to 1 and PlanetaryEncounterTimerMin/Max to 1 as well in sandbox_config.sbc, went to a snowy area, littered the place with gigantic wheeled grids so they'd land safely, and sat on the terrain in the middle (at 1m you pretty much have to be on the terrain to trigger any spawns).

The radius of the spawned thing gets added to the radius so it won't spawn directly on you. Use spec cam to get an idea of the radius they'll spawn away from you and sprinkle more grids.

I have the same bug

Replies (3)

erlgrey ●

lol, but tbh. that does not really suprise me at all as the config parameter is called PlanetaryEncounterExistingStructuresRange and Structures usually refer to static grids.

Reply URL

Digi ●

Yes and that is fine, the setting should not be including dynamic grids either because flying around in a ship would prevent you from ever spawning any encounters =)

What this needs to do is not something admins should be configuring, it needs to use the prefab's boundingbox/sphere if there's something there, they already are storing that and using it for other things in regards to the spawning, but they're not checking if the area is free.

Although there is code for checking trees, it has some bugs as well.

URL

Keen SWH QA Agent 3 ●

Hello, Engineer!

Thank you for reaching out to us with this problem.

The issue was reproduced on our side and reported.

Kind regards,

Keen Software House: QA Department.

Reply URL

Keen SWH QA Agent 1 ●

Hello Engineer,

We would like to inform you that the issue you reported was fixed in the 1.206 (Fieldwork) update.

While reviewing a list of resolved tickets, we noticed that we hadn’t posted an update here earlier — our apologies for the delay.

If you encounter any other problems, please don’t hesitate to create a new thread.

I’ll now close this one as solved.

Kind Regards,

Ludmila Danilchenko

Head of Space Engineers QA Department

Reply URL