Crash on resized lots at 7PM -- any ideas?
Zazazu:
Perhaps utilizing some of the same methods in which the new BV rocks are able to be placed on lots?
I've taken my lots off my thread at MTS2. Some silly bum said they were going to use them for their new 'hood, showing the complete inability of people to read warnings.
pbox:
dizzy,
overlapping lots is already possible (by sticking two lots next to each other and expanding one of them) -- but the flickering is unbearable in-game. Unfortunately.
(Not sure if you know what I mean -- it's the same kind of flickering that occurs when you put e.g. a fence and a hedge next to each other and look at the lot impostor when moving the camera, or when you moveobject two meshes into one that almost match but not quite .. or when walls and halfwalls meet, etc.)
Doc Doofus:
I went back to testing on Backdoor 42 again... and decided that this might not actually be the best lot to use as a test case. While tinkering with it, I finally took a closer look at that backyard car driveway, which I had just assumed it was a non-issue because nobody else was bringing it up.
I'm not so sure now. When you grab at it with the hand tool, you can see a lot of squares that are going off the lot. Was this placed on the lot BEFORE the shrinking process?
I also tried to remove the parts of the foundation and walls on the edges for another test. Unfortunately, you can't do that because it's impossible to remove foundation at the edge.
What I think might be a better testing situation with fewer variables would be a lot that has no custom items on it, no foundation, no driveway, fewer advanced tricks. I can make a lot like that for myself, but the lots I build ALWAYS work for me. This new test lot would have to be made by somebody who can make one that crashes. I would gladly test such a lot, if I knew it crashed under the usual circumstances.
Quote from: pbox
Unless I am totally misunderstanding what dizzy said: the problem we're facing is not that it's crashing. The problem is that the game is trying to write stuff where it shouldn't, or read stuff that doesn't exist, and the only thing stopping it at the moment is the OS. This is REGARDLESS of whether or not you see any crashes.
...
Right now, I don't see what we could learn from more in-game testing. Because if he's right, the goal is not to prevent crashes -- the goal is to prevent things going wrong like this in the first place. And you can't see that from within the game.
Well, I assume he is right, and that there's a register being blown somewhere with uninitialized data. However, I think we all guessed that there had to be some reason EA took those precious two-extra squares away from us, and that they weren't just trying to dicks. It would seem very likely just on the face of it that there may be an important problem associated with using those squares that EA never bothered to code for because it couldn't happen without a third party tool like LE.
However, part of the fun of hacking anything has to do with finding the boundary conditions (software-wise) of what can and can't be done. I have experienced several crashes now, but none of them were corruptive. MORE IMPORTANTLY, to me, I never experienced any visible on-going corruption during the game, which would be the really frightening prospect.
Total crash to desktop -- fine. Little glitches that accumulate and destroy the game database -- not so fine. The bug in the Ottomas family is an example of the latter. Two different types of problems, and this seems to be much more benign, really. I haven't heard of anybody else having a catastrophic failure. In a way, I'm kind of hoping for one.
It would be cool. Sort of like the way watching the comet hit Yucatan 65 millions years ago would have been cool. Sure, you're a goner but before you croak, you're like, "Whoa, dude, do you see what I..."
pbox:
Quote from: Doc Doofus on 2007 November 04, 07:40:35
What I think might be a better testing situation with fewer variables would be a lot that has no custom items on it, no foundation, no driveway, fewer advanced tricks.
I did that two days ago. Which was what dizzy replied upon. You don't need to bother testing those anymore .. they very clearly are broken.
Quote from: Doc Doofus on 2007 November 04, 07:40:35
I have experienced several crashes now, but none of them were corruptive.
How do you know that?
Doc Doofus:
Quote from: pbox
Quote from: Doc Doofus on Today at 00:40:35
I have experienced several crashes now, but none of them were corruptive.
How do you know that?
I suppose you never really do until you see evidence of it, which could happen quite a ways down the line. But I have been playing with these for several nights now and I have seen no suggestions of on-going corruption. And I'm going to continue playing it for the foreseeable future, so I'll report back if anything unusual comes up.
Have you had reports of any corruption? You have been posting these on the net for a while now (I haven't been following the MTS2 thread) so you would know if anybody has experienced that.
Navigation
[0] Message Index
[#] Next page
[*] Previous page