Questions on some behaviours
Cap
Member Posts: 225
Hi,
I have done pretty much every tutorial on GameSalad, but still I have some questions. This time on behaviours:
a, Let's say I completed a level and want to join a new level. I'd probably use Change Scene for this. Do I first have to destroy every actor of the first scene before I go to the next one (to take them out of the memory), or is that done automatically? Do I have to use something like Reset Scene for this?
b, I recently played a game done with GameSalad and noticed that it took quite a while until the game started and the GS splash went away. Is that because images, music and stuff can be preloaded? If so, how can I do it?
c, If I will have about 50 actors in a scene, should I spawn them all at once at the beginning and hide them until I need 'em, or should I spawn them the moment I actually use them?
d, I heard the constrain attribute should be used with care. Are there other attributes that shouldn't be used too much?
e, Highscores and other data are probably saved and loaded with the Save and Load Attributes, aren't they? Are there any code examples available?
Thanks for answers!
I have done pretty much every tutorial on GameSalad, but still I have some questions. This time on behaviours:
a, Let's say I completed a level and want to join a new level. I'd probably use Change Scene for this. Do I first have to destroy every actor of the first scene before I go to the next one (to take them out of the memory), or is that done automatically? Do I have to use something like Reset Scene for this?
b, I recently played a game done with GameSalad and noticed that it took quite a while until the game started and the GS splash went away. Is that because images, music and stuff can be preloaded? If so, how can I do it?
c, If I will have about 50 actors in a scene, should I spawn them all at once at the beginning and hide them until I need 'em, or should I spawn them the moment I actually use them?
d, I heard the constrain attribute should be used with care. Are there other attributes that shouldn't be used too much?
e, Highscores and other data are probably saved and loaded with the Save and Load Attributes, aren't they? Are there any code examples available?
Thanks for answers!
Comments
b.) It is done automatically.
c.) depends on the Actors and where they are Rule-heavy or not. You should definitely test on a device - especially a 3G. I was never able to get more than 20 moving actors on a 3G. Spawning actors can cause a noticeable stutter. Which is why some people hide/show them instead of destroy/spawn them.
d.) Timers, Constrains, and too many actors moving around at once. You should test with the GS Viewer app on a device so you can see the framerate. Test on a variety of devices.
e.) I have seen demos posted on the forums. I don't have specific links.