Tourists not being transported and empire spawn location bug
Posted: Thu Feb 29, 2024 6:07 pm
Hi.
I'm currently experiencing two different bugs(?) on the 1.2.0.8 Beta build.
The first one affects all my games, the other one seems to only affect some of them.
The first one is the game spawning almost all the empires right next to my empire, even though I'm playing on the largest galaxy size and 2000 stars. They spawn so close that I cannot colonize any planets and I'm immediately boxed in from the start of the game. The rest of the galaxy is almost always empty of empires, sometimes one or two spawn elsewhere. This happens regardless of the amount of AI empires I select, and game settings like "hostile empires near the player" make no difference. It seems like there is too high of a preference for empire spawn location to be right next to the player even if the setting is set to "normal". It doesn't seem to factor in the galaxy size, as on a small galaxy the distance those empires spawn would not be a problem. I have so far tried maybe a dozen games, changing the number of empires by a few each time, and unless I only spawn 1 or 2 AI empires, the problem persists. Something to note would be that I always start games with the "pre-warp" tech setting and the smallest amount of preset expansion.
The other problem is related to passenger ships not transporting tourists at all. If I reload a save, they transport one batch of tourists, and then immediately return to "no mission" status. If I however make a save then and reload that save they once again transport one batch of tourists and then stop. This happens no matter which save I load, and refitting passenger ships/resort bases does not affect the problem. I've tried going through every possible scenario that could cause the passenger ships to stand idle, but no reasonable explanation is apparent. This combined with the reloading save oddities leads me to believe this is most likely a bug. This problem is also not affected by restarting the game, verifying the game files, or any other method I could think of. The only fix I've found is starting a new game, which works maybe 50% of the time.
I'm currently experiencing two different bugs(?) on the 1.2.0.8 Beta build.
The first one affects all my games, the other one seems to only affect some of them.
The first one is the game spawning almost all the empires right next to my empire, even though I'm playing on the largest galaxy size and 2000 stars. They spawn so close that I cannot colonize any planets and I'm immediately boxed in from the start of the game. The rest of the galaxy is almost always empty of empires, sometimes one or two spawn elsewhere. This happens regardless of the amount of AI empires I select, and game settings like "hostile empires near the player" make no difference. It seems like there is too high of a preference for empire spawn location to be right next to the player even if the setting is set to "normal". It doesn't seem to factor in the galaxy size, as on a small galaxy the distance those empires spawn would not be a problem. I have so far tried maybe a dozen games, changing the number of empires by a few each time, and unless I only spawn 1 or 2 AI empires, the problem persists. Something to note would be that I always start games with the "pre-warp" tech setting and the smallest amount of preset expansion.
The other problem is related to passenger ships not transporting tourists at all. If I reload a save, they transport one batch of tourists, and then immediately return to "no mission" status. If I however make a save then and reload that save they once again transport one batch of tourists and then stop. This happens no matter which save I load, and refitting passenger ships/resort bases does not affect the problem. I've tried going through every possible scenario that could cause the passenger ships to stand idle, but no reasonable explanation is apparent. This combined with the reloading save oddities leads me to believe this is most likely a bug. This problem is also not affected by restarting the game, verifying the game files, or any other method I could think of. The only fix I've found is starting a new game, which works maybe 50% of the time.