More Awesome Than You!

TS2: Burnination => Oops! You Broke It! => Topic started by: draranha on 2006 November 19, 20:23:03



Title: Game crashing to desktop
Post by: draranha on 2006 November 19, 20:23:03
My game is crashing apparently at random. I'm attaching a log file in case someone can tell me what's wrong here - the game, Windows XP or the hardware... I'm really not awesome...
Thanks in advance.

PS: In addition to the log file, the game is generating a .MDMP file with the same name as the error log file in the Logs directory.


Title: Re: Game crashing to desktop
Post by: J. M. Pescado on 2006 November 24, 08:33:33
Analyzing exception errors requires source code. We don't have this, so these logs are useless to us.


Title: Re: Game crashing to desktop
Post by: croiduire on 2006 November 24, 20:48:42
I was just about to post about much the same problem when I saw this thread.

I have base game, Uni and NL only.

I keep getting:
Exception code: 0xC0000005 (-1073741819) ACCESS_VIOLATION.

When loading the game gets to the Replacing Wheel Bearings screen, then after several seconds it pops up the "application has crashed" notice and the music starts skipping like a scratched 45.
Does that give any parameters of where I need to start looking for the problem?

The Sims2HCDU didn't turn up anything unusual, and neither did the Hack and Duplicate Package Scanner.


Title: Re: Game crashing to desktop
Post by: twojeffs on 2006 November 24, 21:00:50
The only way to figure out what's causing the crash is to remove all custom content, then slowly add it back in chunks until you can narrow it down to the culprit. Time consuming and a pain in the ass unless you get lucky, but it's the only way.


Title: Re: Game crashing to desktop
Post by: croiduire on 2006 November 24, 21:13:02
Thanks. That's what I'm currently doing, but I was hoping for a short-cut (ever the optimist...*grin*)

And I had a good idea that I am going to implement despite the fact it's too late to help this time. My download folder is about to get a new sub-folder for new but unplayed items. I'll sort the stuff into my numerous other organizational folders AFTER I'm sure it works...

Edit: OK, I found the offending files (I pulled stuff out in batches by creator) and I'm now wondering if there's a way to determine which of them is (are) the problem. Is there a utility that flags out of range values and other discrepancies on objects?


Title: Re: Game crashing to desktop
Post by: jsalemi on 2006 November 25, 03:12:01
Edit: OK, I found the offending files (I pulled stuff out in batches by creator) and I'm now wondering if there's a way to determine which of them is (are) the problem. Is there a utility that flags out of range values and other discrepancies on objects?

Only way I know is to continue isolating them until you narrow down which one is the problem child.  Put half of the files back into your game, and see if it crashes.  If not, the problem is in the other half, so add 1/2 of them in and repeat. If it does, start removing files one by one until the game doesn't crash anymore, and you've isolated the problem.


Title: Re: Game crashing to desktop
Post by: croiduire on 2006 November 25, 04:22:21
Given the load time that would be required if I were to test each and every object, I suspect I'll just live without that batch of pretty-shinys. However, I was more hoping for a tool or method to isolate a problem file so it could be fixed. File Cop for Sims 2, basically.


Title: Re: Game crashing to desktop
Post by: J. M. Pescado on 2006 November 25, 07:20:03
Actually, binary search works VERY fast. If you have about 60000 objects, you will isolate it in no more than 16 attempts, and assuming load time is roughly directly proportional to the amount of crap in your game, it will take about as long as loading your game once.

Just do the following:
1. Divide your content, arbitrarily, into two roughly equal halves.
2. Arbitrarily pick one of those halves and stick it in your game.
3. Does anything go wrong?
    A. If so, your problem is in this half. Repeat step 1 on current downloads.
    B. If not, your problem is in the other half. Repeat step 1 on the half you didn't load.

Assuming you have, oh, say, 60000 files, you'll pin this down in 16 loads, with a total loading time on the same order as loading the whole assload once. 60000 objects is, of course, a ludicrously unrealistic number, so you're probably looking at more like 8-10 loads. But even if you had 4 billion objects, you could sort them in 32 loads.