Quote:
Originally Posted by maillemaker
This is a common issue. I personally suspect it is a problem with loading too much information on load - the software is running out of memory or something.
The rule of thumb for SH3 saving is this:
Don't save while submerged.
Don't save within render range of other ships.
Steve
|
Yes, I know the visual effect that you are referring to. But I have never seen a suggestion that the CTDs were reduced or eliminated by using a more capable machine. The problem doesn't seen to be associated with processor, memory, GPU or OS. And I have gotten the same visual effect by accidentally omitting key parameters in the menu_1024_768.ini file, and even by not having an active sound card. It might be a "stack overflow" in the reloading routine, but why didn't they fix it when they used the same code for SH4?
There are other rules. too. I've broken some with impunity. I save submerged whenever I need to, and have experienced no problems. (Man falls off 10-story building. As he passes his friends on the fifth floor, he calls out: "OK so far!") If you save near an active port then reload, the AI ships in the port will "go ballistic", crash into things, and sink. Then, if you save again and reload, that second save can CTD.