Stalintc Posted April 19, 2008 Report Share Posted April 19, 2008 Defect Name: C++ error recieved on resolve torpedo attack vs sub Build: HCE 2008.24 Repeatable: Yes Operating System: Windows Vista Ultimate x64 DB used: Stock DB Scenario used: Kodak Moment Battleset: EC2003 IOPG Long Description: An air launched torpedo in the save attached to this report is causing a C++ error during the resolution of its attack on a Kilo class submarine. The displayed error message will allow continuation of the game by clicking *ignore* Process: - Open GE - Open the attached save for EC2003 IOPG Kodak Moment - Watch the torpedo attempt to resolve its attack on the Kilo class submarine - After a few moments the game will stop and the error message will be displayed. - Note that clicking any other option than *ignore* will cause the game to CTD Expected Behaviour: Torpedo resolves its attack against the submarine and either misses or hits with interuption to the game client. Exhibited Behaviour: Torpedo resolves its attack against the submarine and gets interupted by an error before completion. Workaround: When this error is displayed during the resolution of the attack, be sure to click *ignore* or the game will crash. Notes: I am yet to test this in the current Beta, but will be doing so in the next day or two. I can see no evidence of this error being looked at or repaired in the change logs and I can find no evidence of past reports on this matter, so I expect the results to be the same. Kodak_Moment1error.zip Link to comment Share on other sites More sharing options...
TonyE Posted April 19, 2008 Report Share Posted April 19, 2008 Verified that this happens in latest build. Considering how best to deal with it... Link to comment Share on other sites More sharing options...
TonyE Posted April 19, 2008 Report Share Posted April 19, 2008 Fix coded in 2008.032, also a fix for the GE not showing DB version when loading saved games in some circumstances. Link to comment Share on other sites More sharing options...
Stalintc Posted April 20, 2008 Author Report Share Posted April 20, 2008 Tested in 2008.032 and 2008.033 and error no longer occurs. Also confirmed database version is now displayed for EC2003 scenarios after loading from a save. Link to comment Share on other sites More sharing options...
Recommended Posts