Quote:
thejeff said:
There is definitely a version of this bug in v3.10, that does not require different patch levels, operating systems, etc. I've seen it in 1 machine SP games, which I had not seen before 3.10
|
You are talking about several different things.
"Different patch levels" is one thing. A difference between patch versions or in the content of mod files between the hosting computer and the viewing computer causes a difference between the battle report and the viewable simulation because the host resolves the battle using certain unit stats that are different from the client viewing the simulation, and so you get different results. This is not really a bug, it's just a glitch you get because you used incompatible (well, at least "not fully compatible" versions of the game. (ie is your fault
)
"Different operating systems" is another thing. In this case the difference was caused because different checks in turn resolution employed something that looked like "if (random()+modifiers1>random()+modifiers2) then etc." and on some OSs the random() on the left was called first, while on others the right random() was called first, which basically "flips" the results you get in random rolls between the hosting machine and the viewing machine, leading to different combat replays than what actually happened. I believe this bug has been resolved.
So this is not "a version of the bug" but a completely different bug (currently unexplained) that has similar (but not identical) effects.
If it really is caused by v3.10, my guess would be that this patch introduced some change between the code used to resolve battles when hosting and the code used to resolve battles when replaying them.
EDIT: its => it's