Crash on resized lots at 7PM -- any ideas?
Zazazu:
...and if so, what about one space from? The difference between having houses 4 spaces apart and having houses 2 spaces apart is considerable.
Doc Doofus:
I have been placing objects outside the boundaries for a long time. Who hasn't?
Haven't you ever tried to set up a home bowling alley? They take up an enormous amount of space, but if you use the moveobjects on cheat, you can put them right on the very edge of your backyard so that they extend about six squares out into imposter-land. Looks pretty cool. And it works just fine. I've been doing that since Nightlife came out.
I haven't tried doing it on a shrunken row-house, but I suppose you could, using the same principle, lay a bowling alley right into your neighbor's bathroom.
Emma:
Quote from: Doc Doofus on 2007 November 03, 07:32:46
Haven't you ever tried to set up a home bowling alley? They take up an enormous amount of space, but if you use the moveobjects on cheat, you can put them right on the very edge of your backyard so that they extend about six squares out into imposter-land. Looks pretty cool. And it works just fine. I've been doing that since Nightlife came out.
I haven't ever tried that, but I will now :D
dizzy:
Quote from: Emma on 2007 November 03, 06:33:59
So shrinking lots so that the walls are on the boundary is not safe to do?
I'm saying it's probably unsafe. If the index (-192 in my case) is coming from the lot data itself, you may be able to do something about it, but this value changes in different instances of the crashing. In some cases, it's the multiplier (81 in this instance) overflowing (the value 19496 in one of pbox's logs). In either case, it's the same EIP, so this suggests to me that the errant value is being calculated. In other words, the bad offset is probably not coming straight out of the lot file, but rather as a result of a miscalculation because of the walls and their situation.
If you are not getting the error, it is not safe to assume that this miscalculation isn't occurring. In fact, you may well be corrupting valuable data (highly likely, considering the visible corruption of shadows and such at the outset).
In my experience, one errant bit can cause a program to crash, so how much more damage if we're talking 32 errant bits?
Emma:
So by downloading a shrunken lot and adding it to your game you may be corrupting your game data files?
[edit] What about if you are shrinking pre-existing lots,and never moving them or putting them in the lot bin-does that have the same potentially damaging effect?
Navigation
[0] Message Index
[#] Next page
[*] Previous page