Weird Crash --- can't find any sort of solution.

<< < (13/14) > >>

Juleru:
Quote from: Motoki on 2009 August 09, 19:48:37


As we've said several times, awesomemod does not work with the unpatched game. Done. Period. End of story. Thank you drive thru.


Oh, ok.
Which patch do i have to get? 1.4 or does it work with 1.2?

J. M. Pescado:
1.3/1.4 is the currently supported patch. (There were no script changes from 1.3 to 1.4).

chazzhay:
Okay so apparently I also am having the CTD problem when selecting a save to load. The only thing is it wasn't doing it yesterday, and I haven't changed anything. The only thing I may have done is update Awesomemod! I am patched up to 1.4. >:(

Dr. Zoidberg:
Quote from: chazzhay on 2009 August 21, 15:27:43

Okay so apparently I also am having the CTD problem when selecting a save to load. The only thing is it wasn't doing it yesterday, and I haven't changed anything. The only thing I may have done is update Awesomemod! I am patched up to 1.4. >:(

I'm also having this problem. Just did a fresh install (having uninstalled the game awhile back) and put in the latest version of AwesomeMod . No dice. I saw this thread and installed Patch 1.3, and I'm still having the same issue. I'm not sure what to do.

earthshoes:
Before I go any further, I want to thank Pescado for the auto save feature. Without it, I would have uninstalled this turkey yesterday and been done with this entire EA fiasco. The auto save feature makes the CTDs bearable. At least until something changes or I figure out what the hell I'm doing to contribute to the problem.  I'm inclined to think it's my computer at this point. I have a Celeron Processor (yes, I know, I know. But the price was right at the time). It's only a few months old and I have plenty RAM and a compatible video card with adequate board memory. The game generally plays smoothly, without lags, the graphics look great, and, until this started, I had no real problems with it other than the rare error 13 code and the now rectified 1am freeze.  Everything is patched and all drivers are updated.

That said, since it's begun crashing semi-regularly, I've (finally) noticed a trend. The last several times the game CTDed the characters were in the park in Sunset Valley.  I've been tracking my CPU temperature and it doesn't appear to be any warmer after the crash than it was before. I'm using the 3booter and the fpslimter and last night I turned on Vsync just to be on the safe side.  After emptying all the cache files I played for a blissful couple of hours without a snag. This morning it ran smoothly during the thirty minutes or so I had to play it in. This afternoon it crashed just ten minutes into the play--minutes after I sent a character to the park.   

I'm just reaching here because I'm only just now beginning to understand some of this. Could this have something to do with the frame rate?  The park is a big place with a lot of activity--running water, cars passing, sims running around, etc. If I slow down my frame rate (and I'll have to look up how to do that)--do you suppose it will help?

Navigation

[0] Message Index

[#] Next page

[*] Previous page