As of today, can game salad support IOS 7? My game always crash on IOS 7 in my iPad. Don't know why...
Thanks
KC
Comments
tatiangMember, Sous Chef, PRO, Senior Sous-ChefPosts: 11,949
edited March 2014
Absolutely, yes. If your game is crashing on a device but not on your computer, it could be due to a variety of reasons. An iPad has a different processor and amount of RAM compared to a laptop or desktop computer. It's why we always recommend testing on an actual device to understand the true performance of an app.
It's time to start simplifying your project file by turning rules off and/or removing actors or scenes until you find what is not working (make a separate back up file first!).
Sometimes in scene 1 and sometimes in scene 3. I cannot go to the next level.
Which case cause less memory, Global variable or scene variable?..
tatiangMember, Sous Chef, PRO, Senior Sous-ChefPosts: 11,949
Personally, I wouldn't have started with the images. Rules and specifically behavior expressions are often the problem. That's why I suggested you turn off rules or remove actors from the scene.
When I have a problem like this, I save a separate version of the file and delete about 80% of the actors from the first scene, or I re-arrange the scenes and see if that particular scene was causing the crash. Once I have a bunch of actors removed, if it works then I know it was one of those actors. If it still crashes then I've ruled out 80% of the actors (yay!) and can start to remove the rest one by one until I find the cause. It's painstaking but it's how debugging works.
tatiangMember, Sous Chef, PRO, Senior Sous-ChefPosts: 11,949
@spidey906 said:
Sometimes in scene 1 and sometimes in scene 3. I cannot go to the next level.
Which case cause less memory, Global variable or scene variable?..
Again, I think you're looking in the wrong place. I'm not trying to give you a hard time but if you try what I suggested I think you'll solve the problem. Attributes (aka variables) aren't really going to affect memory that much. And yes, images might but again my guess is that you have an expression that's invalid (e.g. trying to retrieve data from table row zero) or a rule that's infinitely looping, or something along those lines.
Comments
Absolutely, yes. If your game is crashing on a device but not on your computer, it could be due to a variety of reasons. An iPad has a different processor and amount of RAM compared to a laptop or desktop computer. It's why we always recommend testing on an actual device to understand the true performance of an app.
It's time to start simplifying your project file by turning rules off and/or removing actors or scenes until you find what is not working (make a separate back up file first!).
Do I have to destroy all the actor before going to the next scene? Thanks..
No you don't have to destroy all of the actors. How long into the game does it crash?
I made a test with no images and only one actor and it crashed.
It might be because of the GameSalad Ad Network.
Sometimes in scene 1 and sometimes in scene 3. I cannot go to the next level.
Which case cause less memory, Global variable or scene variable?..
Personally, I wouldn't have started with the images. Rules and specifically behavior expressions are often the problem. That's why I suggested you turn off rules or remove actors from the scene.
When I have a problem like this, I save a separate version of the file and delete about 80% of the actors from the first scene, or I re-arrange the scenes and see if that particular scene was causing the crash. Once I have a bunch of actors removed, if it works then I know it was one of those actors. If it still crashes then I've ruled out 80% of the actors (yay!) and can start to remove the rest one by one until I find the cause. It's painstaking but it's how debugging works.
Again, I think you're looking in the wrong place. I'm not trying to give you a hard time but if you try what I suggested I think you'll solve the problem. Attributes (aka variables) aren't really going to affect memory that much. And yes, images might but again my guess is that you have an expression that's invalid (e.g. trying to retrieve data from table row zero) or a rule that's infinitely looping, or something along those lines.
Thanks tatiang. I later found out the cause of crash is I use the constrain a variable to self.timer
Glad you found it and thanks for letting us know!
GN that was my issue, now as a Pro when i turn off the GN everything runs fine!