2 replies to this topic

[RCTeagle]

Wow, I haven't yelled that in these forums in a long time.

Okay, guys...how ya' doing?

Good, glad to hear it.

Here's the thing....and please go easy on me if this has been addressed somewhere already. I'm a tiny blind man who can't find it even though I used the search function.....

I have a friend....yes, it really is a friend, and not me....who is having major problems trying to save his progress while playing RCT3 Platinum. Every time he tries to save, the game crashes and he gets the usual "RCT3Plus.exe has encoutered a problem and needs to close" error message. I've never had the problem....at least I don't remember if I have....but anyway, I'm not sure what to tell him other than the usual "how much RAM do you have" and "You might have to update your video drivers" stuff, etc. Any ideas on how he can fix this? Is there a patch? I don't have Platinum, so I don't know.

Anyway, just thought maybe one of your expert RCT3 fans would have something encouraging for me, so I could pass it on to him.

Anyway, that's all. Hope you guys are well.

Edited by RCTeagle, 23 July 2008 - 11:47 PM.

[Sambo]

Hey - glad to hear from you Eagle!. I don't have Platinum, but I have encountered people with problems such as you describe. Yes, RAM is a factor. If there is more work on a park done than available RAM to store it, it will apparently dump it into Virtual Memory on the hard drive. I have been told that is where a problem like this can happen.

When someone has for example a GB of memory, and 600MB is dedicated to background tasks (all those little things we have running in the background we really don't need - often without us even knowing it) and the main RCT3Plus.exe is running in memory, and we have made many, many changes - enough that it needs to dump into VM - normally it goes OK. However when our memory allocation drops because some background function kicks in just as the overflow is going into VM, there is a memory error that manifests with a need to close error.

...Or that is how it was explained to me.

There is no solution I am aware of other than more memory, and save FREQUENTLY. The saving can be done incrementally after say - 15minutes of work - pause, then save with a version name and number change. For example My park 1, My park 2, My park 3. Or... Funland A, Funland B, Fundland C.

Then there is never more than a few minutes work lost, and past revisions to go back to to rebuild.

...just my $0.02

[RCTeagle]

Yeah, I kinda figured it was something related to RAM, or maybe his video drivers. I do remember the game is a resource hog. That's pretty much why I put it away for a while. I'll pass your words on to him.

Anyhooo....thanks, my friend. Good to see you're still keeping the site going. Take care....I'll pop in every once in a while.