For the record, bman654 is THE MAN. We were down to deconstructing the wrong code trees for this problem, animation was not an intuitive place to look for this. A testament to bman's intuition for sure. This is such a great example of how easily things can be pinpointed once we can reproduce the problem, it isn't even funny.
Hindsight is 20/20, but for those who aren't coders, there are about 14,000 files in our code, and another 8,500 in data and scripts. If something doesn't generate an error or warning (it doesn't), and you can't get it to reliably happen (we couldn't), then you are throwing darts at what you think is the bullseye on a dart board that is very large.
As far as how long before you can play with this fix in the next patch, that is mostly up to Stardock's testing. We are reworking several associated animation scripts right now, and will likely hand this off to Stardock tonight. If it takes a while, it probably won't be because of testing this fix, but several of the matchmaking fixes that have gone in over the last week, and require much more rigorous tests. We will obviously put in a good word for "fast tracking".
Great stuff Servo! Thanks for the update, means alot to us (the community) to know that you have seen this, and yes, BMAN is DEFINITELY THE MAN!!! Even if its too late to implement this in 1.01 by now, at least we know this annoying bug as finally spotted and targeted for liquidation, which means ALOT!!
I for one got renewed hope again