|
Bernd Hesberg -> Some new effects of memory leaks (8/12/2002 12:15:21 PM)
|
This one is really weird. Playing as Japanese I had sent a MSW back to Japan. When I checked for ships en route to Truk a couple of turns later, it had totally vanished from the list. Now, where was it? It must have been boarded by Allied special forces or its crew must have been infiltrated by a bunch of Allied spies. :eek: Yep, at least it looked like that, because as I saw this ship again it was escorting an Allied convoy along the coast of Australia. Of course it got the same 'treatment' as any other enemy ship, although it was still listed as Japanese ship in the AAR. Even the victory points for sinking were credited as Allied success. Now I'm waiting for the first Allied ship showing up as part of the Japanese fleet, and I wouldn't mind if it's a capital ship. :D
Compared to that it's only a nuisance, that you sometimes can't load the specified troops and get some other unit instead (even enemy units). Taking a closer look at that unit aboard the ship, you'll see that it doesn't really exist.
On a more serious approach, I suspect a memory leak to be the origin of several effects posted by various players. And I'm quite sure that this topic has a rather high priority for Matrix and 2by3, even if that means a delay for e.g. WiTP. Well, all those among you who are at least self-educated programmers will agree, that a combination of an MS operating system and the standard stack handling of C/C++ compilers can be really a nightmare! (Can you spell 'exception handling'?)
On the brighter side, if... sorry, when it's finally fixed that solves several probs at once. :)
|
|
|
|
