iOS not powerful enough?

[XStar]

I have tested my app on my iPad and found that it freezes when asked to restart the frame.

This works fine on the computer, so does anyone know how I could fix this?

[ProdigyX]

The computer interpretation of the app represents what "should" happen, not what actually does happen (with the exception of the .exe runtime, there what "should" happen" does happen). In other words, what happens when you run the game on the computer might/usually isn't what happens on another platform, especially iOS/Android. Your best bet would be to go through each of your code until you find the source of the problem then tell us what the source of the problem is.

[XStar]

I've searched and searched, and this is the last bug. I have no clue what is causing this...

This is what happens: Boss is destroyed -- cause and explosion, set timer to 0, set score to 0, save score based on level, save alterable values, restart frame.

[XStar]

Oh and here's bad news: MMF2 freezes when I try to copy the frame...

(Edit: Never mind, it turns out an object was causing the problem... Sorry!)

[Konidias]

What object was causing the problem?

[XStar]

An object that created an effect right before restarting the frame.

Here, I need something new and simple to create a "transition" before restarting the frame.

Please see this: http://community.clickteam.com/showthread.php?t=73147

[Pineapple]

I had an issue with restarting a frame on IOS too. I fixed it by jumping to a blank frame that jumped back to my previous frame.

[XStar]

I think that will work perfectly, however, I need to fix one bug before being able to test that.

My app always freezes when there's too much going on, and I don't know how to scale back...

[XStar]

Let's put it this way, Pineapple is my favorite fruit! It works perfectly!

However, I still have some freezing issues, for some reason whenever there's a lot going on, on the screen, it just freezes... Anyone have any ideas on how to scale back to make it easier on the hardware?

[Anders]

I must have missed this thread.
We found a bug in the iOS runtime when it comes to restarting the frame that could explain some of the problems you have.
We should have a beta version of the iOS exporter out soon. I'm curious to hear if that version fixes your problem.