Quote:
Originally Posted by sailor_X
CTD will always happen with SH3 from time to time. If not on load than during gameplay, like using high TC with external cam on or scrolling a navigation map with mouse drag. Windows version has nothing to do with CTD u get.
Edited:
Assume there are no mod conflicts that could causes a CTD then,
it's the instability of SH3 itself (poor coding) that causes the problems with CTD most of the time.
|
I beg to differ with your statement: "CTD will always happen with SH3 from time to time." If you have an environment which is adequate to run SH3, if you have the game properly installed and patched, and if you follow proper procedures regarding saving games, activating mods, and the use of SH3 Commander, then there is no reason to expect or tolerate either random or reproducible CTDs. If you are experiencing periodic CTDs, then something is interfering with the correct performance of your installation. Whether you choose to fix it or tolerate it is up to you, but it is not due to inherent instability in SH3.
I run SH3 with GWX3.0, Commander, and about two dozen mods. I run under Win7 in hardware of middling capabilities. I DID have a problem with CTDs, severe enough to make the game unplayable. After much work, I identified numerous factors contributing to my problem. Some of them were inherent mod conflicts. More were due to my own mistakes and oversights in installing and using mods, patches, and Commander - including failure to thoroughly RTFM. And I have forty years experience as a professional systems programmer and like to think of myself as fairly conscientious in that regard!
None of my problems was due to any inherent instability in SH3. Since repairing all the self-inflicted damage, I have experienced ONE CTD - when I broke a known rule about saving games to "save a little time." No other CTDs, random or systematic, since then. While I have not personally examined the source code, I have not found any evidence of errors in the code producing CTDs. The fact that there are so many gamers who play SH3 and post on this forum and so few who post accounts of problems would seem to bear this out.
SH3 is a complex system, and when you start modding it, there are many ways you can create problems for yourself. But, I don't think it is fair to say that the SH3 code has imbedded fatal errors, or that fatal errors, such as CTDs, must be tolerated when they occur. The errors are not inherent. They can be found and fixed, if you consider it worth your time to do so.
CAVEAT: I run SH3 with GWX3.0. I have NEVER run rock-stock SH3. But GWX does not change the game engine, sh3.exe, and the game engine is where the executable code lives. Everything else is data.