Thread: [TEC] Reason of CTD and bugs
View Single Post
Old 09-04-17, 04:50 AM   #2
propbeanie
CTD - it's not just a job
 
propbeanie's Avatar
 
Join Date: May 2016
Location: One hour from Music City USA!
Posts: 9,749
Downloads: 439
Uploads: 2


Default

I do not know what you are referring to when you say 'so I need to mix it', but if you are taking bits of one mod and mixing in bits of another mod, that could well be a major problem that would cause a CTD. Most modders, and Lurker with RSRDC & OM probably being at the top of the list, take the time to test their mods under multiple situations to find problems. So much so, that they will partially dis-assemble their mod and the game to only have certain aspects active, to eliminate potential influences on their test results. I'm talking weeks and months worth of testing things. I would not expect that OM, or TMO or RSRDC or GFO etc etc etc to be causing very many issues, other than what were already in the game, such as bad game dates that only affect one out of thousands of plays. But you put parts that are not designed to work together, active in the same game, and you could well have problems.

The main problem with SH4, and to a certain extant SH3, when it comes to the Save games, is corruption in the Save folder. Most of the time though, it is a self-inflicted wound, which many times actually 'cross-contaminates' the game itself, ruining your game install, as well as any mods you have activated. If you are like a lot of us Silent Hunter players, you do not play the game with just one mod installed. You are always looking for that 'mix' as you say, that will make the game all that much better. But what happens, is if you Save the game and have Mod A activated, and then play the game later, but have Mod B activated and restore that previous Save, the Save data will contaminate what you already have. It may well look like the game is functioning as intended, but in the background, you are getting all sorts of mixed up bits of data. Then you save again, maybe activate Mod C the next time you go to play, and it will not load the Save at all. Now you go back to Mod B, and it now crashes completely. So you load Mod A again, and it also will not work. In desperation, you unload all the mods, and try to run Stock, and even it will not work now... All because of trying to load a Save from a different mod than what you had been running when you Saved. Even seemingly insignificant changes in the game can cause the issue. In my opinion, that is the main cause behind game crashes. It would have been nice if there would have been an error catching routine on Save loading, but there isn't. Coming in 2nd place may be bad mod activations when the folder structure in the MODS folder isn't correct. That's my 2 cents worth of opinion, in a 10 dollar space of the thread... |;^) - verbosity rules!
__________________

"...and bollocks to the naysayer/s" - Jimbuna

Last edited by propbeanie; 09-04-17 at 09:03 AM. Reason: lah-dee-dah = who cares about the order the words appear?
propbeanie is offline   Reply With Quote