Crash on resized lots at 7PM -- any ideas?
nil:
So, new CAS sims are more advised to run on empty blank lots and get saved first to be older sims before getting evacuated out of the blank lot and moved into a built lot, especially a shrunken lot?
Just wonder.
2 years ago, I downloaded a set of custom windows which crashed my game copy completely dead including both the custom folder and the game files. I lost my favourite sims at the time and lots. (No, they don't work any more even with a new game copy or a new custom folder.)
Since then, I don't download windows from those I can't know a bit from.
As for whether walls at the edge is a major cause, I think we need shrunken blank lots and wall at various different locations to help make a point on it.
But in my base game copy, all lots of plainly "wall at the edges" by LE/LA127B didn't get a crash at all. So, I conclude it's at least not a sufficient cause itself.
dizzy:
Quote from: Doc Doofus on 2007 November 13, 03:44:25
The game's Simantic code interpreter is a virtual machine, written in C++. Interpreters tend to be more robust than native-code programs when it comes to things like hanging pointers and uninitialized variables. They do crash, but usually with more grace and little damage.
Simantics is not your average interpreter. There is almost no type checking done (outside of an Expression primitive), scope and privacy are completely user implemented, and your only clue to when you pass a bad Id to something like GSC or a Dialog is the Windows Error dialog.
Inge:
Ooh Dizzy, I see you're sporting a proud pair of bonfires there :)
Doc Doofus:
Well, none of us can really know how well or poorly Simantics was implemented, because we don't have source and neither of us worked on it. I'm simply making a general observation about interpreters and virtual machines. I've implemented a lot of interpreters, mostly for AI friendly languages like Lisp and Prolog and Logo, which are all very similar, and more basic procedural languages like Basic in its many flavors, and a couple of new languages of my own weird design that were used for proprietary in-house systems. One of the unique things about interpreters is that they (generally) never have direct access to any machine memory, even through a pointer, because all pointers and variable bindings are managed by the machine. The machine usually has its own memory management and garbage collection system. That's why, for instance, when you crash a Java program, you will get a nasty message from the Java machine, but not from the OS. I take you at you word that Simantics doesn't have the quality robust error-checking that a language like Java has, but they still (VERY likely) have the similarity that memory addressing is indirect and layered.
This is all just to make a bullshit speculative argument that if the virtual machine itself is crashing, it's probably TOO catastrophic to do much damage.
dizzy:
It pretty much goes without saying, and even in Lua (which is pretty low-level for a script language) you do not access memory directly. I can make Lua crash also, but only the Sims 2 implementation. You see, that's the common element.
Navigation
[0] Message Index
[*] Previous page