inconsistency in Case Blue scenario
Posted: Sun Oct 07, 2001 5:31 pm
I recently noticed a minor inconsistency in the case blue scenario in both 3.0 and 3.1 versions.
There appears to be two 103rd Panzer battalions, one attached to O.K.H and the other to 3rd Motorized Division in the 24th Panzer Korps. A quick peek into the save file reveals that these units are indeed two separate units and occupy slots 168 and 197 in the save file.
I suppose this could be intentional, but to me it looks like a bug.
I probably wouldn't even have noticed this if I hadnät been working on a "little" (not so little anymore... <img src="smile.gif" border="0"> save file viewer with a friend of mine, and come across some very strange behaviour when testing its unit hierarchy tree view using a save from the case blue scenario.
Oh well, its nice to see that not all the problems with that particular application are because of our inability to write decent java code. <img src="biggrin.gif" border="0">
There appears to be two 103rd Panzer battalions, one attached to O.K.H and the other to 3rd Motorized Division in the 24th Panzer Korps. A quick peek into the save file reveals that these units are indeed two separate units and occupy slots 168 and 197 in the save file.
I suppose this could be intentional, but to me it looks like a bug.
I probably wouldn't even have noticed this if I hadnät been working on a "little" (not so little anymore... <img src="smile.gif" border="0"> save file viewer with a friend of mine, and come across some very strange behaviour when testing its unit hierarchy tree view using a save from the case blue scenario.
Oh well, its nice to see that not all the problems with that particular application are because of our inability to write decent java code. <img src="biggrin.gif" border="0">