Quote:
Originally Posted by brett25
now you will have to go back to the point before the ship sinks
|
Ok, I was wondering about this. There is a methodology issue here. If you go back to the point before the ship sinks, then there is no conclusive proof that SH3 Commander is the problem.
During one particular mission, I kept having CTD's upon loading. I would engage a convoy sink a bunch of ships, get way out of range, and save the game. Upon loading, I got a CTD. This sequence occurred during three different saves. Two of the times, it was the "same" convoy, then the third was a different convoy. Each time I went to the save prior to engaging the convoy, so "before a ship sank." After the third, I wound up engaging another convoy and doing the same thing, but this time, after returning to the game, it loaded up just fine. I used SH3 Commander throughout the entire process.
To put it simply, you are introducing way too many factors into your control sample in order to truly verify that SH3 Commander is actually the problem.
Unfortunately, your methodology does not support SH3 Commander being the culprit, and I actually find it highly unlikely that this is the case.