Technical Problems (CTDs, Bug Reports, etc.)

[Molon Labe]

From Neal's FAQ:

Troubleshooting: If the game crashes on you, it might leave a dump file (.dmp) in the "My Documents/Sonalysts Combat Simulations/DW ACTUV directory. If you get one, we'd appreciate it if you could send it to "computergames(at)sonalysts.com". That would help with debugging efforts.

In the same directory, there is a "dangerouswaters.ini" file. It's a standard .txt file, so you can look at it and edit it with Notepad or Wordpad. This has most of the options from the options screen in-game, and if you're having trouble getting the program to run, or it minimizes itself, you can find in the [Graphics] section the "RunInWindow" entry. Change it to "Yes". This will sometimes allow the program to run. If you mess the file up somehow, you can delete the file and run the game. The game will rebuild the default file.

I'm sure I'm not the only one so I've generalized the thread topic so others can post here too.... maybe it'll get stickied.

1. I've had 2 CTDs on Maximum Effort at mission end. One when the cutscene was being loaded, the other when I clicked 'show truth' in the replay. In both cases, the CTD prevented the mission log from being created and prevented the data upload to DARPA. No error/crash message was provided. EDIT: I found the dmp files and emailed those.

2. aTMA is generating erroneus solutions in high-contact-density environments, a holdover from DW. This is more problematic in DW because we do not have access to the raw data for a manual solution. The situation this is occurring in is as follows: A valid track is maintained, and then broken off. Target changes course. Target is reacquired at its new location and course. aTMA plots the new solution in the position of the read reckon for the previous course----even though the new location has been discovered.

3. In some cases, aTMA is not reporting a detected SSK. The green track light will illuminate when contact is made, but the contact is never displayed on the NAV map. This occurred for me in the 2nd mission.