Sandy AS3 3.1.1 release
March 28th, 2009 by kiroukou :: General, Project, Releases, en :: RSS 2.0We are happy to announce a new version of our engine, tagged as a 3.1.1 since this release comes with some improvemens and bugfixes withotu any API change. [Edit] A 3.1.2 release in sync with the 3.1.2 haXe version is now available under download.
We are really recommanding to make the upgrade, since there’s a better memory management with the addition of a smart reference counting system. Basically this system allows material ressources to be disposed automatically as soon as no polygon reference it. You don’t have to care about that manually, Sandy does it for you. If you need to keep the material alive for some reasons, just set the property of the material autoDispose to false.
We also added more examples to help users to get started with the library. In this examples you can learn the best practises and rapidly give a try to the feature you need while preparing a project.
Here is the change log: (Access complete changes list)
-
fix of a bug with visible property and cache system
-
change in the skybox class and orientation of the roof texture
-
addition of a dispose method to materials
-
advanced reference counting system on material which makes the dispose method to be called as soon as no more polygon use it (if the autoDispose property of Material is set to true which is the default value)
-
fix memory leak when clipping was enabled
-
improvement of Mode7
-
fix sorting issue with clipping and useSingleContainer = true modes
-
minor improvements
Now you can go to the download page and get that new power into your Sandy3D apps !
Bonjour,
Je suis en train de refaire des tests de performance, et je n’arrive pas à voir d’où vient mon problème, malgré la suppresion de l’instance sur la scène et la suppresion de l’instance :
if ( currentPrimitive != null && currentPrimitive.parent != null ) {
group.removeChildByName(currentPrimitiveName);
currentPrimitive = null;
}
il reste toujours des références à mon objet, qui n’est donc pas supprimé, il reste en mémoire, mes instances sont donc cumulés, et la mémoire plafonne rapidement…
L’élément n’existe plus quand je fais un getChildByName, et à une valeur null..
Pourriez-vous me dire comment régler ce problème ?
Merci
Bonjour,
peux tu m’envoyer les sources de ce benchmark afin que je puisse trouver la raison à ce problème le plus rapidement possible.
kiroukou sur gmail
[EDIT] Attention, le remove supprime l’objet de la display list, mais l’objet existe toujours. Il faut bien penser à appeler le destroy sur l’objet, après avoir fait le removeByName.
Merci!
Thomas
this is unreadable
do not forget to call destroy after calling removeByName, or the object will remain in memory..
]
[EDIT Thomas/kiroukou