Crash on resized lots at 7PM -- any ideas?

<< < (44/59) > >>

Inge:
Well that's ok for someone for whom every hood is potentially a fun experiment, but some people are *really* involved with their sims and would be devastated if anything happened to them.  So it was worth giving a reminder.

Zazazu:
Quote from: Inge on 2007 November 03, 22:35:29

Well that's ok for someone for whom every hood is potentially a fun experiment, but some people are *really* involved with their sims and would be devastated if anything happened to them.  So it was worth giving a reminder.

Considering the multitude of warnings given, that type of person would be a bonafide idiot if they were playing these in their main 'hood, and most likely are old hat at losing 'hoods in BFBVS.  :o

baratron:
Quote from: Inge on 2007 November 03, 20:44:35

You're surely not playing these in your real game yet are you?   I'm still in my test hood so if it craps on another lot I just vape the hood and make another test hood.   I don't advise anyone to play these for real yet!

Depends what you mean by "real game". I only have one Sims 2 game, because I don't have enough hard drive space to create dummy Windows XP accounts to make multiple, separate copies of the game.

I am testing the lots in a throwaway Neighbourhood, as I said 6 posts up from yours. However, I've just looked at the files within Neighborhoods/N00whatever, and it seems that every single Neighbourhood.package, University.package, Downtown.package and Suburb.package get rewritten each time you boot up the game :-\. In fact, the file stamps on those packages correspond to when I quit the game last night, not when I last chose a 'hood to play.

So I'm really quite worried about the potential for bugginess from the game writing to the wrong part of memory getting into the wrong Neighbourhood file, and corrupting one that I actually care about. Anything can happen to N005, but I've worked hard on N004 and don't want it corrupted.

ingeli:
You dont have to make another windows xp  account- just rename the sims2 folder in documents - for example to sims2-realgame - and then restart the game - voila, game created new sims2 folder, and that one can be used for testing. When I want to play my real game, i change the name of the new folder to sims2test, change sims2-realgame back to sims2 and go play. Very easy, just a few letters to type, no extra programs - only thing needed is the extra space for a sims2 folder in my documents. My absolute vanilla-game folder takes up 512MB (I have all expansions and I use the Clean Templates, so I dont get any extra hoods/character files and such.) The test one has the needed downloads added, atm building stuff.

Doc Doofus:
Quote from: Pbox

Did you try to see what happens when you modify the freshly re-plopped-down lot *again*? Does it work then?

Yes, I did try.  It works.  In fact, this is the most consistent thing I have found in this whole experience.  Making a lot crash is dependent upon several variables:

1. CAS-made Sim or non-CAS sim.
2. Which EP was used to make the lot.
3. Packaged or hand-built lot.

Yet, CONSISTENTLY, if I tweak the lot in build-mode from the neighborhood BEFORE moving in a Sim, ANY sim, I have experienced no problem.  Not me.  I'm using unpatched BV.  I have only experimented with your Backdoor 42 lot and with my own designed shrunken lots.

I like consistency.  Of course, your results may vary, but I hope not.


Quote from: Baratron

I'm not bothered about the lot package corruption spreading to the rest of the Neighbourhood as I've been testing everything in a throwaway 'hood. What worries me is the example of The Sims 2 trying to write into a Word document. Could someone who understands the way the game works please confirm whether it is possible for it to be confused enough to randomly open another Neighbourhood and write into that? I'm under the impression that it only opens one 'hood at a time, while the...
I'm reluctant to say never, but it is EXTREMELY unlikely to ever happen that a document in another program could be corrupted by an array index problem.  Those kinds of problems were actually commonplace before virtual memory architecture, which was, uh, years ago.  Since the Word program has a separate memory space, it would take something far, far more catastrophic than a Sims 2 crash to do that.  (Sez Doof who once used to T.A. college Operating Systems)

If you're nervous dancing with the devil in the pale moonlight, maybe you should find something safer to do.  I hear Minesweeper is fun. ;D

Navigation

[0] Message Index

[#] Next page

[*] Previous page