The moment you realised you screwed up a custom Race's home system

[Tikigod (OP)]

Looked at the binary system the game generated with the system and figured "Hey, would be cool to have a nice little belt going on between the two stars", wasn't until about 40 years in and I was pushing out survey ships to survey the home system that I realised the sheer distance between the two stars and that I'd ended up with 880 asteroids spread across 290 billon Kilometres well well weeeeeeeeeeellllll beyond the scope of the standing orders detection range of new targets.... now been some 15-16 years mapping out these asteroids using 3 survey ships.

Sometimes I get lucky with a close cluster that allows a survey ship to chain survey 10 or more before they start whining there's no more asteroids in range to survey, but for the most part the limitation on standing order range has turned this into what will likely be a two decade long survey micromanagement headache. lol


But a good lesson to learn when doing another custom start.... always sanity check distances before tweaking.... that and to dream of a day when Steve blesses us with a option to tune standing order ranges within the standing orders window. 


(Edit: Come to think of it, might be closer to 20+ years already spent mapping the asteroids out, I think my brain is trying to repress the memories of manually babysitting these survey ships for all this time)

[Garfunkel]

always sanity check distances before tweaking

Yes as well as before sending a surveyor to another star or a distant planet that happens to be 200 billion km away instead of "just" the 20 b km you thought it was.

[Droll]

always sanity check distances before tweaking

Yes as well as before sending a surveyor to another star or a distant planet that happens to be 200 billion km away instead of "just" the 20 b km you thought it was.

It makes for an interesting edge case where you wish your surveyor was also a lagrange stabilizer

[Tikigod (OP)]

always sanity check distances before tweaking

Yes as well as before sending a surveyor to another star or a distant planet that happens to be 200 billion km away instead of "just" the 20 b km you thought it was.

In that case at least I made sure the secondary star system had a lagrange point around one of the planets even without noticing the sheer distance involved, purely because I saw some of the planets would make great colonisation targets later on and from past experience I know that even if the range was 10 times less without a lagrange point civilian shipping would tie itself up most of the time just travelling back and forth on mundane orders and pretty much kill all early civilian shipping growth as they'd rarely earn anything initially. heh

So whilst surveying the asteroids is taking me decades, traveling between the two different star systems and populated colonies only actually takes ships around half a week.


On a side note, Aurora handles a binary system with 880 asteroids very well in terms of turn processing and saving, so may do similar again in the future..... just not with these kind of distances.

[Llamageddon]

Pretty impressive, you could use this sort of system generation abuse for benchmarking/stress testing the game. 

[Tikigod (OP)]

Pretty impressive, you could use this sort of system generation abuse for benchmarking/stress testing the game. 

Surveying all those asteroids meant I didn't end up leaving my home system until around year 74, but now exploring 9 systems (and a NPR active the entire time) I can clearly state that those 880 asteroids in my home system seem to have had zero performance impact... likely because these asteroids are stationary objects (Even though orbital behaviour for the asteroids supposedly enabled) so the game doesn't need to calculate orbital behaviour for each one.

[Llamageddon]

I wonder if that means they aren't actually having their orbits calculated or that C# is just so much faster than VB Aurora? Good to know I don't have to worry about it, performance-wise.