18.09.2012, 14:41
Hi,
It's possible that this was actually a mission creation error instead of an AI coding error. There is an extremely remote chance that it is caused by a corrupted file in your download of the patch. Testing for corruption of files, especially hash count, is the only way to be sure of nice, clean IL-2.
Did anyone else report those previous bugs? If no, then it would raise more suspicion of corrupt file in the downloaded folder.
Still... Does anyone else have this issue? :-?
Fireskull
It's possible that this was actually a mission creation error instead of an AI coding error. There is an extremely remote chance that it is caused by a corrupted file in your download of the patch. Testing for corruption of files, especially hash count, is the only way to be sure of nice, clean IL-2.
Did anyone else report those previous bugs? If no, then it would raise more suspicion of corrupt file in the downloaded folder.Still... Does anyone else have this issue? :-?
Fireskull