Game out of RAM when opening Recived Messages notebook

[GuillermoZS]

Hi, the title says everything. When I open the Captain´s log book in game at the end of the patrol, when it´s full of recived messages, it just takes a WHILE to open and sometimes it just crashes (I guess this is beacuse it´s getting out of ram and I have 2Gb...) if the patrol was specially long... Is someone else having the same problem? Any fix for this?

Thanks!

[E.Hartmann]

Not the log book but anytime I try to open the recieved message clip board in mission my screen freezes up for a good 30 seconds. I have 2GB of memory as well so not sure what the problem is.

[akdavis]

Something is wrong with it. Memory leak or something like that. I also have 2 gigs and it is slow to load and often causes CTDs.

[Gizzmoe]

It´s a known bug and AFAIK there´s no workaround.

[Ducimus]

Were talking about all the messages recievied right? yeah theres a work around. Just lower the contact reports radius in the contacts.cfg file. One of the first things the mod community did :up:

[GuillermoZS]

Were talking about all the messages recievied right? yeah theres a work around. Just lower the contact reports radius in the contacts.cfg file. One of the first things the mod community did :up:

Yeah, that can be a solution for the messagges issue. But apart of that, I´m finding the game extremelly unstable it terms of memory administration. In my case it usually crashes 5 or 6 times during patrols (I have to be saving constantly :-?), always when I´m near convoys or ports, or just reciveing contacts. It usually happens when pressing ExternalCam/Bridge button in that exact moment... I think the game still needs a lot of tweaks in this aspect.

I hope this is fixed in the next patch, becouse this makes the game near unplayable. :nope:

[Harmor]

Yup, same here. The game is very unstable and there are tons of situations when it will simply crash to desktop for no particular reason, mostly however when other ships are around. Heck, I steer clear off Destroyers ever since a few times it happened that when a DD was actually searching for me, the game would CTD. "SH 4 exe has encountered a problem and has to be shut down" is perhaps the most frequent message I get from my PC ever since I installed the game.

[boatfull]

Were talking about all the messages recievied right? yeah theres a work around. Just lower the contact reports radius in the contacts.cfg file. One of the first things the mod community did :up:


That fix should be a sticky in this forum IMO.:up:

[Gizzmoe]

Yup, same here. The game is very unstable and there are tons of situations when it will simply crash to desktop for no particular reason, mostly however when other ships are around.
For whatever reason I don´t have this problem. Make sure that your video and sound drivers are up-to-date and that no unnecessary programs are running the background and that your system is free of viruses and adware.

[BlackSpot]

Yup, same here. The game is very unstable and there are tons of situations when it will simply crash to desktop for no particular reason, mostly however when other ships are around. Heck, I steer clear off Destroyers ever since a few times it happened that when a DD was actually searching for me, the game would CTD. "SH 4 exe has encountered a problem and has to be shut down" is perhaps the most frequent message I get from my PC ever since I installed the game.

Exactly the same problem as I'm having. Have to save the campaign constantly. All drivers are up-to-date.:D
I did sent the reports to MicroSoft, I hope they get back to me on this....

[Harmor]

Yup, same here. The game is very unstable and there are tons of situations when it will simply crash to desktop for no particular reason, mostly however when other ships are around.
For whatever reason I don´t have this problem. Make sure that your video and sound drivers are up-to-date and that no unnecessary programs are running the background and that your system is free of viruses and adware.

I am using Catalyst 7.3, my audio drivers are up to date too and I got no viruses or adware on my hd. This is my system: P4 3.6 Ghz, ATI 1900 XTX (512 MB), 2 GB Ram ... I am getting no lags or stutters ingame.

[Von Hinten]

Here's a nice JSGME compatible fix for this guys: http://www.subsim.com/radioroom/showthread.php?t=108959

Works like a charm. :up:

[BlackSpot]

Here's a nice JSGME compatible fix for this guys: http://www.subsim.com/radioroom/showthread.php?t=108959

Works like a charm. :up:

Thanks. This does fix the message problems, however, it doesn't fix random CTD issues.

[Prof]

Yup, same here. The game is very unstable and there are tons of situations when it will simply crash to desktop for no particular reason, mostly however when other ships are around. Heck, I steer clear off Destroyers ever since a few times it happened that when a DD was actually searching for me, the game would CTD. "SH 4 exe has encountered a problem and has to be shut down" is perhaps the most frequent message I get from my PC ever since I installed the game.I had frequent CTDs when gaming with my new PC that I never had with my old system. I solved the problem by going into the BIOS and forcing the RAM timings and voltages to those specified by the manufacturer. Some games were more prone to CTD than others before I fixed the RAM.

[DragonRR1]

Yup, same here. The game is very unstable and there are tons of situations when it will simply crash to desktop for no particular reason, mostly however when other ships are around. Heck, I steer clear off Destroyers ever since a few times it happened that when a DD was actually searching for me, the game would CTD. "SH 4 exe has encountered a problem and has to be shut down" is perhaps the most frequent message I get from my PC ever since I installed the game.I had frequent CTDs when gaming with my new PC that I never had with my old system. I solved the problem by going into the BIOS and forcing the RAM timings and voltages to those specified by the manufacturer. Some games were more prone to CTD than others before I fixed the RAM.
I don't think that the majority of people with CTDs in SH4 have a problem with RAM settings but this is generally a very valid point. The auto detect settings for many ram types - especially DDR2 - apply a lower voltage than actually recommended by the manufacturer especially with high spec RAM (OCZ Platinum PC2 6400 for example). This can cause blue screen crashes, CTDs and even file corruption.

A lot of people complain that they don't have problems with X number of games but game Y CTDs or makes their PC reboot and therefore the game is at fault. It's quite common that game Y has just highlighted a problem which has been there all along especially when only a small number of users experience the issue.

I would strongly recommend memtest86 - http://www.memtest.org/ for anyone mildly suspicious of their hardware. RAM which has a major fault or which is very undervoltage will often show up within 5 mins or so but I've seen systems with RAM faults run Memtest for 4 or more hours before finally erroring. I tend to run Memtest on suspect systems for 24hrs.

With SH4 I have had one (repeatable) CTD where everytime I switched to an external view after finishing off a couple of freighters with the deck gun the game would CTD, usually between 2 and 10 secs after switching view. I do know that there were a couple of destroyers around at the time. I went back to base using the map view only. On the way back I experienced the massive lag with radio messages but no CTDs.