World stop issues(list will be updated when issues occur)

[sfunk]

This list has been provided to me by X. these are problems he knows that will cause world stop or error issues. So try to avoid doing these things

-Setting the extrusion property of a 3d text object to zero causes the world to lose the ability to load properly

-Working with the Magician object or Ninja object at all causes object deformity and world stop

-Deleting a referenced object, removing its references, then leaving those references unchanged from <None> causes world stoppage

-Referencing any null property (e.g. the length of the first object in an empty list) = world stop

-Divide by zero or try to solve any other irrational equation = world stop

-Load too many objects or an object too complex for Alice to handle = DirectDraw error

-Deleting an object then undoing and redoing the deletion sometimes results in a phantom object which appears normal and can be manipulated, but doesn't appear on the item tree. if this occurs, immediately close Alice and continue form you last backup, as Alice will no longer save.

-Certain poorly constructed models can trigger a red-screen-of-death for Alice, meaning work cannot be saved. This is rare, however.

-Running processor intensive background applications slows Alice down and can crash it.

-Alice has a very serious memory leak, meaning the longer it runs, the more power it takes to continue running. Restarting the program every half hour or so is recommended, as is saving every fifteen minutes.

-Some copies/updates of Alice cannot handle sound and will stop upon the scheduled playing of one.

-Some copies of Alice will load the startup splash, then immediately close. Simply double click the Startup icon again to open Alice if this occurs.

-Sometimes, Alice will freeze at the startup splash. If this happens, end the Alice.exe process in Task Manager

[DensetsuNoKaboom]

For me dividing by zero just results in an answer of infinity.

[ElectricKirby]

Originally Posted by sfunk

-Working with the Magician object or Ninja object at all causes object deformity and world stop

I noticed that the magician acted weird when I tried to use Orient to on it... that's why I took him out of my game that I'm working on. Now I have to swap out the ninja too?! =(

Also, Alice has trouble working if you set the extrusion of a 3D text to a high number, like 100+

[sfunk]

well this is just pretty much a check list to see if your world stops or crashes, so if you can use the object go ahead and use it.

[x2495iiii]

Clarification on the ninja:

It can be used, but not posed. Capturing a pose is fine, but asking it to set a pose at any time will cause it to twist its arms and enlarge its eyes. It's actually pretty funny, up until the errors start piling on.

The magician is shot to pieces, though, so don't use him. He looks like a leatherface ripoff, anyway, and his hat is wrong for magician, so I just use a guy in a tux from the he-builder and give him the magician hat object from the objects folder if I need a magician in any of my worlds.

[ElectricKirby]

Originally Posted by x2495iiii

Clarification on the ninja:

It can be used, but not posed. Capturing a pose is fine, but asking it to set a pose at any time will cause it to twist its arms and enlarge its eyes. It's actually pretty funny, up until the errors start piling on.

The magician is shot to pieces, though, so don't use him. He looks like a leatherface ripoff, anyway, and his hat is wrong for magician, so I just use a guy in a tux from the he-builder and give him the magician hat object from the objects folder if I need a magician in any of my worlds.

Well, now I need to swap out my ninja then.... My game utilizes poses.... =(

[x2495iiii]

Yeah, sorry about that. You could do one of two things if you really needed a ninja:

1) Take a character model roughly the same size as the ninja and scale him so that he fits completely inside of the ninja model. Vehicle the ninja's respective subparts to the inner model's corresponding subparts, then set the inner model's poses when you need the ninja to move. Plausible, but impractical and unwieldy.

2) Re-texture a model to color it all black except for an eye slot, making it look like the character is wearing a ninja suit. Considerably easier, but you need to know how to re-texture.

[arty-fishL]

Originally Posted by sfunk

This list has been provided to me by X. these are problems he knows that will cause world stop or error issues. So try to avoid doing these things

-Setting the extrusion property of a 3d text object to zero causes the world to lose the ability to load properly

never experienced this, it loads fine

-Working with the Magician object or Ninja object at all causes object deformity and world stop

Yes object deformity on poses (but no world stop), as X clarified

-Deleting a referenced object, removing its references, then leaving those references unchanged from <None> causes world stoppage

Null pointer error

-Referencing any null property (e.g. the length of the first object in an empty list) = world stop

Null pointer error

-Divide by zero or try to solve any other irrational equation = world stop

0/0 = NaN x/0 = infinity (x<>0)

-Load too many objects or an object too complex for Alice to handle = DirectDraw error

Untested (I dont have any models like that and I've had many objects with an error, but I just dismiss it and it works fine)

-Deleting an object then undoing and redoing the deletion sometimes results in a phantom object which appears normal and can be manipulated, but doesn't appear on the item tree. if this occurs, immediately close Alice and continue form you last backup, as Alice will no longer save.

Not experienced this, have experienced "phantom" objects, but it always saves fine and plays fine.

-Certain poorly constructed models can trigger a red-screen-of-death for Alice, meaning work cannot be saved. This is rare, however.

Not experienced this, but its rare

-Running processor intensive background applications slows Alice down and can crash it.

I usually find this causes Alice to take over and the other applications freeze or lag much more than Alice. Making Alice do processor intensive stuff in the extreme crashes Alice for me.

-Alice has a very serious memory leak, meaning the longer it runs, the more power it takes to continue running. Restarting the program every half hour or so is recommended, as is saving every fifteen minutes.

Yes for me, but not really a big memory leak, it can last for hours and hours (I don't really need to restart it every half hour).

-Some copies/updates of Alice cannot handle sound and will stop upon the scheduled playing of one.

I usually get an error on the first play and it continues playing without sound, but if I restart the world it plays fine with sound

-Some copies of Alice will load the startup splash, then immediately close. Simply double click the Startup icon again to open Alice if this occurs.

I've only experienced this when I mess around with stuff that happens on startup of Alice.

-Sometimes, Alice will freeze at the startup splash. If this happens, end the Alice.exe process in Task Manager

I've only experienced this when I mess around with stuff that happens on startup of Alice.

replies in bold and colour

[sfunk]

Well some people may never experience this stuff or it might not cause a crash, maybe just an error, but this is just a reference point for those who ran into trouble with their worlds and need a check system

[x2495iiii]

Originally Posted by arty-fishL

never experienced this, it loads fine

Remember my first youtube video? When making the text for the computer in that video, I set the extrusion to zero. I accidentally closed Alice, then tried to load the world and got that an "Unable to load world" error. This is the one that I asked the Alice team personally to fix. Not sure if they fixed it in an update, but it definitely used to be an error.

Yes object deformity on poses (but no world stop), as X clarified

I've gotten stops from the magician and when trying to fix the deformed ninja.

Null pointer error

Which, depending on how it happens, often means it messes everything up.

0/0 = NaN x/0 = infinity (x<>0)

This one used to be a poor man's game ending function. People would divide by zero at the end of the game to get you to restart if you wanted.

Untested (I dont have any models like that and I've had many objects with an error, but I just dismiss it and it works fine)

Tested (by me) when converting. Dismissing the error works occasionally for objects under 50k polygons, but for me, it leads to an infinite amount of identical errors saying that Alice has failed to draw the scene, until you click Give Up or just close Alice. may be computer dependent, but since Alice uses the heavily outdated DirectX 7, I doubt it.

Not experienced this, have experienced "phantom" objects, but it always saves fine and plays fine.

I've only had one or two run-ins, but every one has ended in a red screen when i try to save.

Yes for me, but not really a big memory leak, it can last for hours and hours (I don't really need to restart it every half hour).

Meh, you could probably get away with going longer at a time, I just put that as a guesswork number that I knew wouldn't be too long. You think an hour would be better?

I usually get an error on the first play and it continues playing without sound, but if I restart the world it plays fine with sound

That's happened to me too, but then so has the error. I've noticed Alice is inconsistent and unpredictable at times.

I've only experienced this when I mess around with stuff that happens on startup of Alice.

Which, with the Custom Startup Splash tutorial, many users will be doing.

Responses not in bold.