It would be nice is there was a "resetWorld" feature that would clean up all the old objects and listeners, and start with a fresh new instance of the world.

Couldn't you just drop the old and dirty world, and create a new brave world?
I'm after the delete and destroy approach

Well, it isn't as obvious as it sounds. Someone has to tweak the classes to destroy the containing clip and the Singleton _inst.

These aren't exposed in the current version.

I worked out some hacks, but I'm hesitant to post them to the repository, because they are probably not cleaning up completely. My brave new world seems considerably slower than the old dirty one.

Hi Bruce,
Are you talking about the 1.2 ?

Is the Worl3D.getInstance().getRootNode().destroy() not working as you expect?

Thanks for the information. I hadn't tried that. I'll let you know if it works.

Does that put it in a state where I have to set the rootGroup again and invoke World3D.render?

In other words, what state is the world left in when you destroy the rootNode?

I've been unable to destroy individual objects in the world the way I was able to do in 1.1, so that is why I was looking for a way to destroy the entire world.


Bruce

I have the same problem. The 'World3D.getInstance().getRootNode().destroy()' did not work. I'm even looping through all the childs in the rootgroup and both destroy and remove them. Afterwards I destroy and remove the root group.

Still, Everytime I create a new world is twice as slow as the previous one..

In Sandy 1.2, I think it is getRootGroup() not getRootNode();

such as:

World3D.getInstance().getRootGroup().destroy();

I haven't tried it yet but that should work better than getRootNode!

the strangest thing.. I've made the whole 3d world as an external swf, so that I can unload it when I have to build a new world.. but the problem remains!

it's not a texture thing, because I removed all textures as a test ofcourse

I've tried to port to 1.2, but then things didn't work and I wasn't able to get it to work. Got all kinds of errors for ClipScreen class also..

running out of options :s

Well, if you're trying to port to 1.2, you shouldn't be too fast.
There are FAQ's about that under "Sandy 1.2 issues".
Among other things discussed is the fact that ClipScreen is no longer used in 1.2.

For the original problem, I haven't got a clue ( so far )

I'm a lot further now. Best practice for this problem (at least in Sandy 1.1) seems not to cleanup the world, but just stop rendering it, make the clipscreen invisible and make it visible and start rendering again when needed.

I just ran into another funny thing while re-applying textures to an object (both via faces and setskin). The textures are not correct when reapplyed to the object, so I had to remove the object and place a new one.

Sounds strange. Would you have any code to demo the problem?

Well, whaddayouknow? I tried to recode this bug.. but couldn't! The problem was solved because I had to rewrite the routine, so I thought to quickly put the bug back in and paste the code here.. I must have made a mistake with the texture indexes I use.. (I created a TextureManager that loads all jpegs upfront and holds an object with id's. On creating the Object3D's I also create an array which holds references to those objects and their positions, translations, etc. and the id's of the appropriate textures in the TextureManager)

As soon as this project is done I'll put some sources up here. Can't do that at the moment, for the website it's for is not live yet and I think our (big and paying) customer wouldn't appreciate ;-)

by the way, your extensive tutorials gave me a very good kickstart to understanding Sandy. So thanks a lot for that!

Well, for once a really lucky programmer, who cannot find a way to reintroduce a bug
Thanks for your kind words!

Looking forward to see the final results.
good luck!

it's finaly live for netherlands! Sandy is awaiting behind the round button!
www.eamostwanted.nl

I must say I'm very impressed with the great performance Sandy delivers. Even on a mac! ;-)

Quite an impressive site design too
Thanks!

Really good !!

It is fast here, on a MAC too Good one!