Crash on resized lots at 7PM -- any ideas?
pbox:
Thanks Zazazu =)
I just had an idea about the CAS sims (that all the crashes have been happening with CAS sims so far) .. from what Mootilda says here about memory possibly being corrupted, qutoe: "If I am correct and the problem is that some objects are off-the-lot, then the game could easily corrupt other things by just accessing whatever happens to be in these off-the-lot memory locations. (..) The one thing that mitigates this somewhat is that I believe that the game only loads one lot at a time. However, if you save multiple lots during one run of the game, then all of those lots can be affected"
-- maybe it's not so much the fact that they're CAS sims, but the fact that they're NEW (= made in the same gameplay session) that makes them crash? The game has just saved them somewhere, and then during/after the shrinking it meddles with that same somewhere? Still doesn't really explain the night thing, but .. roofs do block light, and if it's saved roof code where sim code should be (or the other way around?), I can see how something would go wrong at that point.
(Mind that it's rather late in this timezone again and I'm all decaffeinated, so no warranties on the logicalness of the above)
baratron:
I downloaded & unzipped lot03+04+05+05_post-play.zip. I played:
lot 6 until 10:00 on Wednesday
lot 5 until 14:46 on Tuesday
lot 4 until 14:00 on Tuesday
In each case I moved in a freshly-made CAS sim & added basic objects needed for the first few days. I began each test by toggling Day/Night mode a few times, then proceeded to play through the day normally, without using the Insimenator to advance the hour. I can tell you that a game with no hacks is freaking unplayable - the sims are so unbelievably moronic! None of the "pre-crashed" lots crashed in my game (Sims 2 + Uni + NL + OFB + Pets), with no Downloads and groups.cache removed before beginning test.
I haven't tested lot 3, and I haven't tested the files in lot03+04+05+05_post-shrink.zip to see whether they will crash my game or not. (After all, if the "pre-crash" lots do nothing, then it wouldn't be a surprise that the "post-crash" lots were safe!). But it is officially Too Late in this timezone for me to want to try any more considering I have work tomorrow morning. I'll test the rest tomorrow sometime.
Doc Doofus:
Pescado:
But the walls can't be put up against the edges of the lot for a REASON!
Pbox:
Pffft .. if we only did things we "can" do, according to EA, we'd all still be playing with vanilla Maxian games.
I feel like I've heard this dialogue before. Don't they always say things like that in horror movies just before the hockey mask guy impales them?
dizzy:
Okay, my curiosity is satisfied. What I'm getting here is what's called an Access Violation error. It's caused by something giving a negative index. The code simply loads a dword blindly out of a table with said index without bounds checking, and kaboom. So, there you go. You can't do this.
Emma:
Quote from: Doc Doofus on 2007 November 03, 03:20:35
Pescado:
But the walls can't be put up against the edges of the lot for a REASON!
Pbox:
Pffft .. if we only did things we "can" do, according to EA, we'd all still be playing with vanilla Maxian games.
I feel like I've heard this dialogue before. Don't they always say things like that in horror movies just before the hockey mask guy impales them?
:D
Quote from: dizzy on 2007 November 03, 04:55:50
Okay, my curiosity is satisfied. What I'm getting here is what's called an Access Violation error. It's caused by something giving a negative index. The code simply loads a dword blindly out of a table with said index without bounds checking, and kaboom. So, there you go. You can't do this.
So shrinking lots so that the walls are on the boundary is not safe to do?
Navigation
[0] Message Index
[#] Next page
[*] Previous page