I hawe a model of character. 3300 faces and when in game i moving cursor ower character logick brics starting eating a tons of memory
But “mouse over” brick setup not even on a this object!
Ewery “mouse ower” in game for some reason starting to eat memory when cursor over character o_O
hire is blend example
LolCardGame2313.blend (2.17 MB)
When you add a Mouse Over sensor to any object, the game engine constantly checks to see what object the mouse is over. When an object has many faces, it takes the game engine longer to determine which object the mouse is over. Change the physics type on your character to “No Collision” and you will see that the game no longer slows down when you move over the character.
If you need to use collision detection on your character, make a much simpler collision mesh (perhaps 300 faces), and use it as the physics mesh. You can do this by using the “Edit Object” Actuator and choosing “Replace Mesh” with “Phys” selected.
Also, you should avoid using many Mouse Over sensors. Instead, use one Mouse Over Any sensor with a Python script. Your game will run much faster this way.
Edit:
You can see that many Mouse Over sensors will slow your game down quickly. Your example blend has 10 objects with Mouse Over. Moving the mouse over the character causes 42% Logic use on my machine. When I remove Mouse Over from 9 object (so only 1 object still has the sensor) it only causes 4% Logic use. So you can see that the Mouse Over sensor is very inefficient. Each Mouse Over sensor is evaluated independently, instead of checking once and sharing the information between all 10 sensors.
Thanks blendenzo!