Gamesalad Game Crashes Straight Away

Jordeyy

Ive tried both adhoc and Gamesalad viewer , and both of them freeze at the same point.

i start the game ok , then pick my game mode but then when i click my game mode it freezes

if this is an error with either coding or an image , how could i find where the errors coming from ?

beefy_clyro

You'll need to strip out rules one by one to find the culprit.

I would first delete actors from the scene until it loads, you then know the last one you deleted is the problem.
I would then put them all back on the scene and start taking out rule by rule of the offending actor (you should be able to simply switch them off so you can switch them back on). You should then be able to determine exactly what is causing the crash

Jordeyy

@beefy_clyro could it be alot of the images are not 72dpi

RUPAS

@Jordeyy if of course, you can try any software to force the images to 72 dpi, not sure but may be the solution, you tried to look at the performance markers? section of images exceeds 200 mb?

tatiang

Obviously, if it freezes when you click your game mode, then whatever is in that actor is a good place to start. It could be image-related or table-related or it could be the result of a bad expression (e.g. forgot a parenthesis).

While you can't use Log Debugging Statements in adhoc or iOS Viewer modes, you can make your own. Just have a DisplayText actor on the scene(s) in question and change the value every so often (e.g. "1", "2", "3", etc.) in your actor's rules. That way, when your game freezes, you'll know that it stopped after "2" or "14" or whatever and you can pinpoint where in the rules that happened.

Jordeyy

@tatiang sorry bro but i dont get what your mean ?

tatiang

It was just a suggestion you could try. beefy_clyro gave you another suggestion that will also help to find the problem. Good luck!

Jordeyy

@tatiang could you send me a more advanced answer in a pm , like exactly how to do it ?

tatiang

The idea is to display a text attribute and then change that attribute at certain points in your list of rules. So you might change it to "1" at the top of your rule list, then "2" at the middle, and then "3" at the bottom. As you play your game, you'd be watching to see if that actor displayed "1" and then "2" and then "3". If, for example, the game crashes after you saw 1, then you know the problem is in the top half of your rules. If it crashes after you saw 2, then you know the problem is in the bottom half of your rules. You could, of course, have any number of changes to that attribute. The more changes, the more finely you can determine where the problem exists.

If it still doesn't make sense, I recommend that you try beefy_clyro's advice.

Jordeyy

@tatiang no i understand now , i will try that now