Closed rufreakde closed 3 months ago
Checked on my entity:
Collider test = Entity.GetComponent<Collider>();
Collider test1 = Entity.GetComponent<BoxCollider>();
Collider test2 = Entity.GetComponent<CircleCollider>();
Collider test3 = Entity.GetComponent<PolygonCollider>();
var test4 = Entity.GetComponent<ColliderTriggerHelper>();
all are null
Okay after some look through the example ninja code I realized the example code has memory leaks.
So I removed the Mover component
which I dont need as I do not have physics or collision.
No Memory leak since then :)
PS: for anyone who has memory leaks with NEY or MONGAME here is a good easy tutorial to check stuff out: https://www.youtube.com/watch?v=9QPgfJPaGvY
Hi all, I am trying Nez for the first time and just took the ninja example threw away a lot of stuff I dont need like triggers/collisions/projectiles.
And have now an entity without the trigger interface (so no collider I guess). Flying around the scene but I noticed the memory allocation to rise.
After some dotnet memory analysis I saw the following:
So the culprit is found but I really don't know why this happens. It always happens when I move my sprite around the scene. If it just stays in position and plays its idle animation no memory leak.
I enabled the debug view but only see yellow lines (sprite borders) no red lines (colliders)
Any idea how this happens?