Post by ck07 on Aug 13, 2023 7:55:38 GMT -6
1.00.18.
In the 2nd war in an 1890 game, started getting messages at the start of battles: "Error in GetDamagePercentage Procedure! [BB][AI ship name] invalid floating point operation" and "Error in DoDamageControl Procedure Invalid floating point operation" several times each for the first few turns; then they would disappear for the remainder of that battle.
After backing out using Task Manager and running forward again, I soon got another battle that produced those error message. I saved the game immediately and looked in the .SAC file. The ship's division consisted of that ship only. Both the division and ship names had asterisks and both showed speed 0. The ship had a "sinking" report dated the minute before, the same as the start of the battle.
The ship named was actually a CA, not a BB. Investigation of ship design files showed that the ship had been refitted 3 times, along a different path from its sisters, and that the ship type in the design file had changed from CA to BB between the first refit design file and the second (before the war).* I could find nothing else wrong in the design files and nothing in the .BCS file or the Almanac. (* The 3rd refit ran from the 1st month of the war to the 7th, which is when the errors appeared.)
Looking back in old saves I was able to verify that the ship type error in the refit design file did appear as soon as that design file did, or at least the same year.
Oh yes. I searched all of that country's (FR) ship design files without finding more errors. I did not search all design files.
Correcting the design files did not help. Backing up to before the first design file that included the error did (fortunately just 1 year).
3 wars later, against a different opponent, the same thing happened again, except that this time it was a BC being misreported as a BB.
Investigation showed that this time 3 out of 5 ships in that BC class were affected, although the error messages in the 1st battle mentioned only one. Each of that class had followed different refit paths, with the ship type error first appearing in the 2nd or 3rd refit design file (again all before the war).
Error messages and sinking the same.
This time I can't get around it by backing up because 2 of the the refit design paths that include the errors got them 7 and 8 years earlier.
I can send you the scenario save file. Not sure how useful design files would be since I have edited them to correct the ship type.
But surely the conditions will be easy to replicate.
In the 2nd war in an 1890 game, started getting messages at the start of battles: "Error in GetDamagePercentage Procedure! [BB][AI ship name] invalid floating point operation" and "Error in DoDamageControl Procedure Invalid floating point operation" several times each for the first few turns; then they would disappear for the remainder of that battle.
After backing out using Task Manager and running forward again, I soon got another battle that produced those error message. I saved the game immediately and looked in the .SAC file. The ship's division consisted of that ship only. Both the division and ship names had asterisks and both showed speed 0. The ship had a "sinking" report dated the minute before, the same as the start of the battle.
The ship named was actually a CA, not a BB. Investigation of ship design files showed that the ship had been refitted 3 times, along a different path from its sisters, and that the ship type in the design file had changed from CA to BB between the first refit design file and the second (before the war).* I could find nothing else wrong in the design files and nothing in the .BCS file or the Almanac. (* The 3rd refit ran from the 1st month of the war to the 7th, which is when the errors appeared.)
Looking back in old saves I was able to verify that the ship type error in the refit design file did appear as soon as that design file did, or at least the same year.
Oh yes. I searched all of that country's (FR) ship design files without finding more errors. I did not search all design files.
Correcting the design files did not help. Backing up to before the first design file that included the error did (fortunately just 1 year).
3 wars later, against a different opponent, the same thing happened again, except that this time it was a BC being misreported as a BB.
Investigation showed that this time 3 out of 5 ships in that BC class were affected, although the error messages in the 1st battle mentioned only one. Each of that class had followed different refit paths, with the ship type error first appearing in the 2nd or 3rd refit design file (again all before the war).
Error messages and sinking the same.
This time I can't get around it by backing up because 2 of the the refit design paths that include the errors got them 7 and 8 years earlier.
I can send you the scenario save file. Not sure how useful design files would be since I have edited them to correct the ship type.
But surely the conditions will be easy to replicate.