Do you ever get this bug without first loading a save game? I think it should be linked to the "veterancy not saving" bug. Please try the test build in the waypoint loops discussion, since that bug is fixed there. (Also, that test build isn't compatible with existing save games.)

On further thought, I think I may know the exact cause. It looks like this will happen if you have a rank 3 medium tank and do a save -> load. There's a flag for "my next shot is the first shot of a two-shooter volley, so it gets a super short delay" that gets toggled each time a two-shooter unit fires. I think what's happening is that you're doing a save -> load while this flag is set to true (e.g., when the tank is idle), and then it's losing its two-shooter status along with its veterancy, which makes it unable to reach the code that toggles the flag back off, so every shot is on a 3-frame delay. Is that consistent with what you're seeing? If so, it should already be fixed along with the save -> load issue.

I'm not sure how you're getting a rank3 unit after loading a save game. Since the root of the bug is that RA's crazy-ass load routine is reinitializing my variables (to zero) after copying them, it shouldn't be possible to get a non-zero value there. Is it at least a unit that had rank3 veterancy before the save -> load? Or are random units getting unearned promotions? I'm going to *hope* this was somehow fixed along with the save -> load issue.

Overall, this reminds me: Since I'm breaking old save game compatibility with the next patch anyway, I might as well go back and undo the things I did to fit within the available space, since doing them "right" should have better performance and less risk of bugs.

It is entirely possible that the tank already had a rank 3 veterancy before I loaded, and I simply didn't notice. I guess it just caught my eye since veterancy doesn't save.

And yeah, what you are describing sounds accurate re: the bug.