| Minefield overflow |
Sun, 31 July 2022 00:28  |
|
 ricks03 |
 | |
Messages: 222
Registered: January 2012
Location: NC | |
|
I stumbled across two posts discussing the minefield overflow problem.
https://starsautohost.org/sahforum2/index.php?t=msg&goto =5252&rid=1532&srch=minefield+overflow#msg_5252
Quote:I actually did a quick check of minefileds and I found that they seem to overflow and dissapear if their radius get to 1020ly. I could get the field up to 1019ly (1039440 mines, decy rate 519720) but anything over that would simply dissapear
As that seemed like a bug I can detect and warn for, I did some deeper investigation.
I can't get to the precise number, but I can get a LOT closer. If the minefield + minelaying will be somewhere between 2022095 - 2022101 mines (1161 LY) it won't blow. In other words, 2022095 is safe. 2022102 you'll lose the minefield. If there's a power of 2 in there, I just fail to calculate it.
This is a massive single minefield supported by 143+ decked out nubians, with Minelayer 130s (SD Race). I don't see any other reports of it, so I can't see any value in coding up detecting it (yeah, so the value of the other things I've done is also of limited use, but this REALLY is), just documenting it.
https://www.irelandbybicycle.com
http://totalhost.sinister.net:999
https://github.com/ricks03/TotalHostReport message to a moderator
|
|
|
|
| Re: Minefield overflow |
Fri, 22 September 2023 12:39  |
|
| magic9mushroom |
 | Commander |
Messages: 1361
Registered: May 2008 | |
|
I have done some investigation of my own.
There are two anomalies with laying into large existing fields with large amounts of minelayers.
1) The minefield can "vanish". I use the scare quotes because it's not actually destroyed. Rather, the code for checking how the centre shifts is bugging out and moving the minefield's centre outside the map. I don't think it's going to (0,0); I think it's a bit over -2000 to the X and Y values from what they should be (2048, maybe?). A code dig on the .m and .exe would be needed to verify the exact amount.
If you only go a bit over the threshold, you won't be able to see the minefield afterward, hence the false idea of it "vanishing". But if you put an absurd amount of mines into the field, it can still overlap the map. And of course, it still counts as existing for the purpose of the minefield limit, and it's not going away any time soon since it's huge, probably doesn't overlap any planets and the off-map portion can't be swept, so you're basically playing with one less minefield cap for the rest of the game.
2) Under some circumstances (seems to involve higher mine amounts than needed to trigger #1), a fleet will lay a new minefield rather than laying into an existing one. I'm not sure whether this is a bug; it may be a not-quite-successful attempt to avoid triggering #1 (which is definitely a bug).
I also tested laying new fields; that works fine up to at least 57 million. Presumably a limit does exist, since the #mines entry in the description of the field presumably has a finite size, but it seems unlikely or impossible to hit it (that 57 million is slammed up against the cap for a non-SD with one design, since that's 32,000 36-minelayer nubians; you could go higher with SD and/or multiple designs, but come on). With that said, there's a bit of a hitch somewhere between 10 and 57 million: the decay rate drops to 50. As in, not 50% of the minefield like normal - 50 mines per year.
[Updated on: Fri, 22 September 2023 13:25] Report message to a moderator
|
|
|
|
Members
Search
Help
Register
Login
Home
