![]() |
Quote:
|
I wouldn't know...never liked it from day one, especially after seeing it on one of my kids laptops.
|
Quote:
Quote:
Quote:
|
Now the CTD:s has kept me from playing for a very long time now. Seems I will try this out anyway:salute:. Good Job!!!
(Played SHIV with TM2.0 instead and it has been very stable compared to SHIII/GWX). /Gozo |
I'm sure this has been suggested already but lately I've found that when the game crashes or a save doesn't want to load, exiting the game, doing a rollback for SH3C and then rebooting the computer and starting up and loading the save again usually works. It's tedious but seems to work for me.
I'm using XP btw. |
Just my $0.02... but if it's a save game issue, why wouldn't you change the folder where your save games are saved (ie, C:\...\My Docs\SH3) to no longer being "Read Only"? I can't really see what changing the main install directory would accomplish if the CTDs are all related to loading save games... :hmmm:
Will definately give a try it myself however... anything to be rid of the random CTDs from loading saves :shifty: |
Quote:
And if you forum people do decide to try this change, please do inform us on the results. So far I only know of me and MissingName who seem to have changed the read-only attributes and gotten no save game CTD's after that. |
I've made the change as well and have deliberately saved 6 or 7 times over the last 2 weeks in situations which would have previously crashed the game without a single crash.
It is working fine for me. |
Quote:
|
Quote:
We had completed our 4th patrol, went through the in-port procedure and started our 5th patrol without incident. I saved outside the port as a matter of course. We made it to our assigned patrol area and submerged to 25 meters. No sound contacts. I saved at this point and shut down both game and computer. This AM, I started the computer. Started the game in Commander as usual, and CTD after loading. Both saves crashed. Here's the interesting bit. When I had started the 5th patrol yesterday, the calendar in the briefing room had the correct date of 23 February. I noticed the loading screen was displaying December's news. Since the patrol start date was 23 February, I thought it strange that January's news was not displayed. The game had played normally afterward. Could it simply have been a date discrepancy causing the crash? Unfortunately, restarting the patrol in port deleted the corrupt saves. If it happens again, I'll certainly check that option out. |
Quote:
|
Ok, it happened again this morning. This save should have been clean. I was at the corner of No and Where, no contacts within listening distance and on the surface.
There was no date discrepancy as may have been the problem yesterday. Here's the only common thread. Both crashed patrols started pierside even though I have the Start at Sea mod enabled. This last one was a result of not giving commander a chance to roll back after the crash. Ok, my bad. The earlier one I assumed was normal behavior when I didn't exit the game after the previous patrol. I just reloaded torpedos and headed back out to sea. To my surprise, the patrol started pierside. Question: Is it normal for those with the Start at Sea mod to start the second patrol at pierside if they do not exit the game between patrols? |
As far as I am aware you need to start a patrol via SH3 Commander for the function to work.
|
Thanks you, sir!
|
All times are GMT -5. The time now is 03:49 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.