Well, after all the time I've been spending talking about the Stalker being the absolute best brawler, the mvp, I recently discovered I was wrong, not totally but still big time.
Recently I decided to revamp my setup of planner plus chances calculator to remove some code I don't use anymore and add a few QoL extras (like auto assign weapons/equipment to slots, so I can check in a fast way if everything fits), and after I finished I decided it would be nice to add an alternate method to calculate chances using random number generation (instead of calculating the final chances) with the hope that perhaps would be faster. When I did it, I discovered that my SRM (and MG) code calculation was wrong, it didn't factor correctly diminishing returns. I investigated how could that happen, as I was pretty sure it was working right (and I still have the test sheets used for to compare results), because I did a lot when I first made it. I managed to track the error to one of the many performance upgrades that I did long time ago, when that was a big issue for me, as a a 5-6 mech calculation could take easily near two minutes (much more if two of them were LRM boats) and that being the reason I also had an specific mode for simplifying LRMs, which could easily exceed the maximum time allowed. Also ironically the mistake was due to overconfidence, because it is quite dumb, just two words in a bunch of code, while the LRM part, which took me a lot more time to get it into decent performance and I've redone it from scratch several times trying to get better performance, is working fine. Perhaps because that being the case I tested it more thoroughly each time I made changes, and not so much when I dealt with the easier parts. Becase the SRM code is fairly easy but it's not simple or fast to test that you can check with a binomial calculator like I can for single hit weapons.
So yes, I've been a fool, while I've had a mountain of data from logs I never bother to look into this specific issue after the first testing, as I was sure it was right, showing how easy is to keep believing what one already believes, but it was an honest mistake and while embarrassed of how long took me to discover it at least it didn't need anybody else to point it out.
Now, the correct numbers would be (for the usual comparison):
So still quite decent single salvo and very good dual salvo but not so much a powerhouse as I thought. That dual performance no doubt helped me believing it, because I almost never PS in an isolated way but almost always in couples, be it from the same mech in a row, two same mechs or a single Stalker plus a long range mech (LRM or direct damage).
Probably I'll add a comparison screenshot of several more builds, so I'll bump the thread enough time for regulars with who I've got many discussions will notice my mistake and they know I'm wrong in this.
Note that while changes my opinion in some aspects it doesn't in others, like the multi+breaching recurrent theme of discussion.
Here some more setups:
Recently I decided to revamp my setup of planner plus chances calculator to remove some code I don't use anymore and add a few QoL extras (like auto assign weapons/equipment to slots, so I can check in a fast way if everything fits), and after I finished I decided it would be nice to add an alternate method to calculate chances using random number generation (instead of calculating the final chances) with the hope that perhaps would be faster. When I did it, I discovered that my SRM (and MG) code calculation was wrong, it didn't factor correctly diminishing returns. I investigated how could that happen, as I was pretty sure it was working right (and I still have the test sheets used for to compare results), because I did a lot when I first made it. I managed to track the error to one of the many performance upgrades that I did long time ago, when that was a big issue for me, as a a 5-6 mech calculation could take easily near two minutes (much more if two of them were LRM boats) and that being the reason I also had an specific mode for simplifying LRMs, which could easily exceed the maximum time allowed. Also ironically the mistake was due to overconfidence, because it is quite dumb, just two words in a bunch of code, while the LRM part, which took me a lot more time to get it into decent performance and I've redone it from scratch several times trying to get better performance, is working fine. Perhaps because that being the case I tested it more thoroughly each time I made changes, and not so much when I dealt with the easier parts. Becase the SRM code is fairly easy but it's not simple or fast to test that you can check with a binomial calculator like I can for single hit weapons.
So yes, I've been a fool, while I've had a mountain of data from logs I never bother to look into this specific issue after the first testing, as I was sure it was right, showing how easy is to keep believing what one already believes, but it was an honest mistake and while embarrassed of how long took me to discover it at least it didn't need anybody else to point it out.
Now, the correct numbers would be (for the usual comparison):
Code:
SINGLE SALVO DUAL SALVO
DR 2xAC20++ 6xML++/4xSRM6++ 2xAC20++ 6xML++/4xSRM6++
0% 32% 39% 54% 83%
20% 32% 29% 54% 76%
40% 32% 13% 54% 59%
60% 3% 1% 15% 24%
So still quite decent single salvo and very good dual salvo but not so much a powerhouse as I thought. That dual performance no doubt helped me believing it, because I almost never PS in an isolated way but almost always in couples, be it from the same mech in a row, two same mechs or a single Stalker plus a long range mech (LRM or direct damage).
Probably I'll add a comparison screenshot of several more builds, so I'll bump the thread enough time for regulars with who I've got many discussions will notice my mistake and they know I'm wrong in this.
Note that while changes my opinion in some aspects it doesn't in others, like the multi+breaching recurrent theme of discussion.
Here some more setups:
Last edited: