Bullethead
23 Aug 06, 21:47
I've noticed 2 very annoying problems with 1.014 that are pretty much game-breakers. I've reported them to ES and am sure they'll be fixed soon. In the meantime, however, if you haven't yet gotten 1.014, I strongly recommend that you DO NOT get this patch, because 1.012 doesn't have these problems. These problems are:
1. Massive Collisions at Battle Start
See my thread "Togo's Civil War". It appears that whenever a battle begins involving a division with more than 4 ships in it, most ships of that division are given the same spawn point and begin the battle colliding with each other. Divisions with 4 or less ships seem immune to this problem, even if the TF includes other divisions with more ships that do begin colliding.
Partial Workaround: Put your ships in divisions of 4 or less ships. However, this does nothing for the AI's TFs :(.
2. TF Mine Capacity Problem Returns
In 1.012, all TFs had their correct mine capacities based on the ships in them. In 1.014, most TFs now have a zero mine capacity again, and can no longer be given mine orders, even though they are composed solely of minelayers. There is no workaround, just like there wasn't before 1.010/1.012, or whenever this problem was fixed.
1. Massive Collisions at Battle Start
See my thread "Togo's Civil War". It appears that whenever a battle begins involving a division with more than 4 ships in it, most ships of that division are given the same spawn point and begin the battle colliding with each other. Divisions with 4 or less ships seem immune to this problem, even if the TF includes other divisions with more ships that do begin colliding.
Partial Workaround: Put your ships in divisions of 4 or less ships. However, this does nothing for the AI's TFs :(.
2. TF Mine Capacity Problem Returns
In 1.012, all TFs had their correct mine capacities based on the ships in them. In 1.014, most TFs now have a zero mine capacity again, and can no longer be given mine orders, even though they are composed solely of minelayers. There is no workaround, just like there wasn't before 1.010/1.012, or whenever this problem was fixed.