Build: 3266 Mode: Survival? Mode: Singleplayer? Scenario creation SERVER NAME: SEED-ID: 6330454 If applicable: MODIFIED PLAYFIELDS: Yes, trying to create custom scenario Reproducibility: Sometimes, Unstable Severity: Major Type: Scenario creation using fixed seeds and fixed POI positions Summary: Fixed Seeds in combination with fixed POIs not working properly Description: Toying around with fixed planet seed (planet created with the SSG) i am encountering major issues on getting the same planet/terrain when starting a new game. Sometimes the terrain is not the same as seen on the SSG while sometimes it is. The worst thing about it though: moving the fixed POIs around seems to actually impacting this?! Steps to Reproduce: Screenshots, Crash Logs, any other Relevant Information or Download links: Between the three attached savegames the only thing that changed inside the playfield file was the positioning of the POIs. The only other thing that changed was the chosen seed during the creation of the scenario, although the fixed seed should override that?!
I am not a content creator, and probably I am saying a nonsense but... moving a POI not should change the seed? I mean... if you change the location of a POI, it is not the same world anymore. Or the seed is related to the planet type, terrain and so on and the POIs location is stored in another way? POIs location and type are not part of the seed? sorry my ignorance.
To my understanding it should not, seems to be the same in empyrion. You're basically setting the planet seed and its biomes and inserting POIs later at fixed locations you define instead of the random placement the game usually does. I assume it is correlated to POIs being to close in some form but i could be totally wrong too. Later tests did not show the same results anymore.
I started out with the static and dynamic files and when i got curious about the playfield.yaml as i had never seen one of those before. I checked it out and to me it seemingly is just both files combined thus i started using the playfield.yaml. The reported bug occured with the playfield.yaml.
This could be a kind of 'evil' bug, the ones you have trouble to pin down... Im my case: POI of different factions spawning far too close in the SSG, but not ingame. (Usually factions exclude POI from other factions inside their zone- Maybe to not get 'overlap regions' of faction territory in the ingame planetary map.)
Can't remember exactly right now but they were all set to either Admin or None. Nothing that creates a faction territory as of now.
I assume that the procedural terrain generation probably does not use the random seed generator. I can certainly confirm that the asteroid generation does not use the random seed number. Any element of the game that is neither completely procedural nor driven by a seeded random function will produce different results each time you create a new galaxy.
I'm using a playfield.yaml file for my Refuge instanced planet. That uses a fixed seed and fixed POIs and the terrain is the same each time. But that planet is also in the sectors.yaml file (it's not randomly generated).
I did the same (i still use the very same playfield.yaml, sectors.yaml, seeds etc and did not have that occur anymore). Now after a 3 months of not having this issue (good job on necroing btw, i can't even find a one month old bug report when i want to ) i had the idea that it might actually have been caused by me switching between using playfield_static/dynamic and only playfield.yaml. As i am a dumpster tier noob i still don't really understand why there even is a playfield.yaml sometimes and sometimes not. What i can piece together though is that the playfield.yaml seems to write its contents to the other two at a certain point (when the scenario gets loaded maybe?) thus it was possibly only a bug that occured while this happened. Something just didn't get copied over properly and thus created the mishaps.
The static and dynamic files are used by the game to create the playfield.yaml that gets put in your save game. You can use one or the other, not both. playfield.yaml uses fixed values for most things and allowed you to set a specific seed and therefore have the same terrain each time.
