![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#16 | |
Watch
![]() Join Date: Mar 2007
Posts: 22
Downloads: 0
Uploads: 0
|
![]() Quote:
|
|
![]() |
![]() |
![]() |
#17 |
Ace of the deep .
|
![]()
I had that problem with SH3 as well .
|
![]() |
![]() |
![]() |
#18 |
Sparky
![]() Join Date: Apr 2007
Location: Bucharest, Romania
Posts: 153
Downloads: 24
Uploads: 0
|
![]()
@ Major Johnson - thank you. Yes, I'm aware of that tip - I've been playing games for 25 years now, so I do know quite a few tips and tricks to optimize my rig and/or to make a game more stable. Tried that, even though I don't have fps issues on my Dual core /w 2 GB RAM rig. What did help with the random ctd's in my case was setting the sh4.exe affinity to one core instead of two.
I still think it's a problem specific to SH4, because I'm playing some other games that are known to be bigger memory eaters / problem makers than SH$ (Oblivion, Gothic 3) and those work smoothly on my rig. Anyway, bottom line for the incident described - I tried loading all saves from the patrol in question, and for every one of them when attempting to dock I got a CTD. I got to the autosaves (onleavingbase and oneneteringbase), loade, started a patrol and immediately ended it - boom, CTD. After loading a save game from the patrol just previous to this buggy one, and finishing it again, all went well. So it would seem that the game screwed up writing some files after ending my last patrol. I don't know why it happened, I have no explanation for it (nor for the copy protection acting up afterwards like it did), and anyway I see from the forum that I've been quite blessed with a relatively trouble-free gaming experience. So I'm not giving up on SH4 ![]()
__________________
________________________ Semper ubi sub ubi ubique. |
![]() |
![]() |
![]() |
|
|