30.03.2005, 23:56:18
Sorry dude, but it's the other way round
I've just played a wonderful, hours-long game of TD: SE's Alpha. Without the patch.
It was several hours long. i.e. it was not interrupted by some weird-ass error. And it was with your patch deactivated.
It was the exact same version that gave me reconnection errors all over the place while the patch was active.
However, the exact same version did give me errors while the patch was activated.
Yet, I have yesterday killed a trojan that camped on my HD.
i.e. my testing environment was not clean, therefore I cannot say whether the results are conclusive.
Since it can only have been there for two days at max, it is highly unlikely that it generated the REs, but it is still possible.
The intervall between the kill-the-trojan test and the test before, which showed no virus, was minimal. In fact I'm not even sure if I played in that intervall at all. Therefore, I'm pretty sure those errors were not caused by the trojan, but by something related to the game (either my code or your patch). Unfortunately, I cannot exclude the possibility that the trojan generated the errors. So I have to test again.
I will do new tests with a new version of the mod later.
I will play today's build of the mod online as well, again testing if more errors occur with the patch enabled or not. Probably tomorrow afternoon.
I've just played a wonderful, hours-long game of TD: SE's Alpha. Without the patch.
It was several hours long. i.e. it was not interrupted by some weird-ass error. And it was with your patch deactivated.
It was the exact same version that gave me reconnection errors all over the place while the patch was active.
However, the exact same version did give me errors while the patch was activated.
Yet, I have yesterday killed a trojan that camped on my HD.
i.e. my testing environment was not clean, therefore I cannot say whether the results are conclusive.
Since it can only have been there for two days at max, it is highly unlikely that it generated the REs, but it is still possible.
The intervall between the kill-the-trojan test and the test before, which showed no virus, was minimal. In fact I'm not even sure if I played in that intervall at all. Therefore, I'm pretty sure those errors were not caused by the trojan, but by something related to the game (either my code or your patch). Unfortunately, I cannot exclude the possibility that the trojan generated the errors. So I have to test again.
I will do new tests with a new version of the mod later.
I will play today's build of the mod online as well, again testing if more errors occur with the patch enabled or not. Probably tomorrow afternoon.
Forum Rules
(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!
(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.