ok. im tired of this. my game is only 90 kb, and when i preview, it breaks and crashes. why? its only 90 kb!
Comments
gyroscopeI am here.Member, Sous Chef, PROPosts: 6,598
@GM_Pandagames One possibility: check all your Change Scene behaviours, are they firing before other stuff has yet to finish? (Timers, interpolates, etc). If so, put a Timer After so many seconds to allow those other behaviours to finish before changing scene.
i think it might be me making an atribute 500. how would i an put an actor all over the scene? im trying to spawn with atribute spawndown is 16 because i need 16 spawns and it says every .5 sec if game.spawndown is greater than 0 spawn actor spawner (which is the same actor) except i have a test actor that shows game.spawndown and it goes like this: 16, 15, 13, 9, 1, 0 how can i fix this?
tatiangMember, Sous Chef, PRO, Senior Sous-ChefPosts: 11,949
It's easy to crash an app when you're using recursive spawning (an actor that spawns itself). Are you doing that intentionally to speed up the process? It sounds like you're trying to place tiles or something along those lines (e.g. 100 actors by 100 actors).
Have you considered using a moving spawner instead? That is, use a move or interpolate behavior and have it spawn an actor every so many x pixels or every so many seconds. Then just place a spawner at the start of each row and remove all the recursive spawning behaviors.
Comments
@GM_Pandagames One possibility: check all your Change Scene behaviours, are they firing before other stuff has yet to finish? (Timers, interpolates, etc). If so, put a Timer After so many seconds to allow those other behaviours to finish before changing scene.
16, 15, 13, 9, 1, 0 how can i fix this?
Have you considered using a moving spawner instead? That is, use a move or interpolate behavior and have it spawn an actor every so many x pixels or every so many seconds.
Then just place a spawner at the start of each row and remove all the recursive spawning behaviors.