SUBSIM Radio Room Forums - View Single Post

BigWalleye · 10-06-13, 10:25 AM

BassII, I wasn't around back then (I was around, but not playing SH3!), but AFAIK there were definitely code errors in the original release. ("Don't buy anything with a version number that ends in zero.") By v1.4, maybe sooner, those seem to have been cleaned up.

"Well, a new tracking job in my hard scheduled retirement timetable has been noted"

That really was what I was getting at. The game code is OK. If you have problems, you can decide to fix them, or decide to live with them, but you get to choose. My problems were unlivable, and it took me about a month to sort them out, but I have a good installation at the moment.

You certainly seem to have plenty of hardware power. I don't think that is a problem. And your mod list is pretty small with no obvious interactions. Have you ever yanked a mod out with JSGME when it was not on top of the stack. (JSGME will prevent you from removing overwritten mods, but taking out a mod in the middle can mess up JSGME's bookkeeping.) Have you made any changes using Commander? And have you EVER changed your mod list without rolling back Commander? This last one is a real No-No!

From what I have seen around this forum, the best way to get rid of problems (especially CTDs) that have no obvious cause is to do a clean re-install. Roll back Commander. Remove all mods. Uninstall SH3. Delete all residual folders, including the Mods/ folder and the game save folders in User/. Use a registry cleaner. Then reinstall everything. Hopefully, you have saved the downloaded zips of all your mods. No need to re-download, just use the zipped files as your source. See if that doesn't give you more stable performance. This sounds like more work than it actually is. With your mod list, you should be up and playing again in about an hour.

You are absolutely right about one thing: When you add a lot of mods, and when you muck about the data files the way Commander does, there are a lot of opportunities to screw something up. Sometimes, something small and subtle and deep, deep down, that you'll hardly ever see. Only now and then.

Let me say too that JSGME and SH3 Commander are wonderful programs. I wouldn't want to have to live without them. And they have a lot of safeguards built into them. But they are also powerful programs and it is possible to misuse them. They are not idiot-proof, as this idiot can attest!

If you want to read my tale of woe, here's the thread: http://www.subsim.com/radioroom/showthread.php?t=205755 I had lots more stuff going on, and had lots of "minor" problems that added up to a BIG headache. You should have an easier time of it.

Good luck and good hunting! See you at the cabaret!

10-06-13, 10:25 AM	#18
BigWalleye Sea Lord Join Date: Jul 2012 Location: On the Eye-lond, mon! Posts: 1,987 Downloads: 465 Uploads: 0	BassII, I wasn't around back then (I was around, but not playing SH3!), but AFAIK there were definitely code errors in the original release. ("Don't buy anything with a version number that ends in zero.") By v1.4, maybe sooner, those seem to have been cleaned up. "Well, a new tracking job in my hard scheduled retirement timetable has been noted" That really was what I was getting at. The game code is OK. If you have problems, you can decide to fix them, or decide to live with them, but you get to choose. My problems were unlivable, and it took me about a month to sort them out, but I have a good installation at the moment. You certainly seem to have plenty of hardware power. I don't think that is a problem. And your mod list is pretty small with no obvious interactions. Have you ever yanked a mod out with JSGME when it was not on top of the stack. (JSGME will prevent you from removing overwritten mods, but taking out a mod in the middle can mess up JSGME's bookkeeping.) Have you made any changes using Commander? And have you EVER changed your mod list without rolling back Commander? This last one is a real No-No! From what I have seen around this forum, the best way to get rid of problems (especially CTDs) that have no obvious cause is to do a clean re-install. Roll back Commander. Remove all mods. Uninstall SH3. Delete all residual folders, including the Mods/ folder and the game save folders in User/. Use a registry cleaner. Then reinstall everything. Hopefully, you have saved the downloaded zips of all your mods. No need to re-download, just use the zipped files as your source. See if that doesn't give you more stable performance. This sounds like more work than it actually is. With your mod list, you should be up and playing again in about an hour. You are absolutely right about one thing: When you add a lot of mods, and when you muck about the data files the way Commander does, there are a lot of opportunities to screw something up. Sometimes, something small and subtle and deep, deep down, that you'll hardly ever see. Only now and then. Let me say too that JSGME and SH3 Commander are wonderful programs. I wouldn't want to have to live without them. And they have a lot of safeguards built into them. But they are also powerful programs and it is possible to misuse them. They are not idiot-proof, as this idiot can attest! If you want to read my tale of woe, here's the thread: http://www.subsim.com/radioroom/showthread.php?t=205755 I had lots more stuff going on, and had lots of "minor" problems that added up to a BIG headache. You should have an easier time of it. Good luck and good hunting! See you at the cabaret!