Continuous crash issue.

WOLFENSTEIN

I've got a problem with an app I'm testing on my iPhone, I'll give you a bit of history with ways I've attempted to solve it.

The app launches, but then as I attempt to play the 'game' portion of the app, which I assume would be the most processor / ram heavy portion of the app it crashes out, I found an optimization guide and re-sized every image as best as I could, deleted all artwork that wasn't being used and it still crashes upon opening.

So I decided to try something a little more radical, I decided to use that re-sized artwork and build my app on a new project from the ground up, presently it has three screens.

It opens fine onto the welcome page. A background image with two invisible actors hovering over buttons drawn onto the background. One takes you to an instructions page, (which works fine). And the other takes you to the game. At this stage the 'game' only has three actors, the player controlled actor, a background, and a moving floor wrapping around the screen, yet it's still crashing when I attempt to open this part on the iPhone?

What could be causing this? I am genuinely out of ideas. (Also I wouldn't know how to paste a crash report without copying a wall of text from xCode).

jonmulcahy

you can use Instruments to check the ram usage of your app, that might help you see if you are crashing for memory issues.

but it could also be a bad rule. the creator and iOS viewer are more forgiving than a native app. If your rule is missing an attribute it will cause the entire app to crash. I have a feeling this is the more likely cause.

delete actors one at a time in that scene and see if it works. if it does, delete rules one at a time until you find the bad one.

WOLFENSTEIN

I followed your advice and did a few tests taking a few elements out, adding them back in, testing here and there, I found out what was making my app crash, I don't freakin' believe it either.. It's the ground.

I'm not sure what is making it crash, it's the only actor that does it. (everything else is enabled and it works). It has one behaviour and one rule. The behaviour is move at a speed of 200, in direction 180. (wraps around X). The rule is change attribute, so if the player collides with the ground it kills the player (changes attribute alive to no, which alters the players ability to move in the players backstage). Several other actors all use the same rule of on collide change attribute. It's quite confusing.

Hopscotch

@Wolf, can you post a screenshot of the rules?

WOLFENSTEIN

Hopscotch

@Wolf, make sure that the "yes" in the Change Attribute behaviour is not being interpreted as an attribute.

Open the expression editor and enter "yes" with quotes. Don't just enter it in the field.

WOLFENSTEIN

I'm sorry I'm not entirely sure what you mean by expressions editor, I wasn't exaggerating when I said I was awfully new to this program. - I opened up the second box on the attribute thing, and changed it to "yes", and when it crashes it interrupts the crash sound effect, and delays the scene change by a good few seconds. Is that normal?

Hopscotch

@Wolf, so it does change to the next scene?

Then the problem may be on the next scene.

WOLFENSTEIN

It was meant to change to the next scene, I don't think the problem is there. It's always crashed on the screen where the 'ground' actor was, every time that's worked I've not had any issues with the game over screen. I'm going to play around with it a bit and see.

Hopscotch

WOLF said:
I opened up the second box on the attribute thing

Just to clarify, yes, that is what I meant with the expression editor.

WOLFENSTEIN

The app is finished and working, time to upload to the app store! >:D

How I fixed it was quite simple really, I took the move function out of the ground, and turned it invisible, (also added a few things like change scene etc). I created a new actor with the ground texture and set that to only move, so it appears the player collides with the ground, when really it's the invisible actor behind it, this solved my crash issue, it might help anyone else having a similar problem.

Hopscotch

Congratz @Wolf. Now you have time to fix your avatar problem