Cannot launch program

[SolarB]

I get the error: "timed out waiting for app to launch" when testing on device after it hangs on launch screen.

It will load in simulator 5.0 and 5.1 (but not 6.0), but will not run properly (important objects disappear).

I'm using the ForEach extension with nested loops and I believe it might have something to do with that (though I may be wrong).


Also, anyone know why .mfa file size is so big?

Thanks for your help!


MFA and XCode project:

http://dl.dropbox.com/u/22580256/detectors.zip

http://dl.dropbox.com/u/22580256/detectors_iOS.zip



Target: 4.3

Tested on iPhone 3GS, XCode 4.5, Mountain Lion.

[SolarB]

Update:

I tried copying and pasting everything to a new project. Now it will run past the launch screen (sometimes) but it's still not functioning like it's supposed to (one detector works, framerate is awful).

I would be most grateful for any insight.

Cheers!

[Francois]

The compression of images is not really good in mfa files. THis will be corrected for the next version.
Are you displaying very large images? Slowing down can be explained by low memory conditions : the system generates memory warning message very often, which forces a global cleanup of the application.

[SolarB]

Thanks Francois, I'm not too worried about framerate at the moment but there seem to be other issues in the ForEach extension. If you look in my example file all objects function correctly under Windows runtime but in iOS only one object seems to be functioning.

[Anders]

The timed-out error isn't related to the iOS Exporter.
Clean your XCode project, delete the app on your devic, close down XCode completely (right click it on the dock and close it from there) - and then try again. Also try disconnect the device USB cable and reconnect it if you have problems. Last resort is to reboot both your Mac and your device.

Your ForEach bug is unrelated to the above but sounds like a bug nontheless.
I'm not really sure what is supposed to happen in your MFA file, I only see the flashing indicators change size - and an occasional active object diamond at the screen edges.

[SolarB]

Thanks for the reply Andos, project compiles and runs. The ForEach problem is my major issue now.

In the app, actives are randomly scattered outside of the frame. Each detector counts the number of actives that it sees and adjusts its width and opacity based on the quantity and distance of the actives in its view. The actives are off screen, but in the actual game the player (not in the example) can choose to move toward the closest one/largest cluster. This example is a (very) reduced version for test purposes and so the screen does not scroll.

Attached is another method of doing the same thing, this time without the nested loops which I initially thought were the problem. I thought I had a workaround but it turns out it's just as buggy without nested loops. Again, the detectors do not function like they do in the Windows runtime. Something is not happening for Top, Left and Bottom and they do not behave as they should, and again I'm led to believe that ForEach is the culprit. I can't isolate the problem any further, it's strange and definitely beyond me - if you can, please compile to Xcode and notice the difference btw the Win and iOS runtimes.


http://dl.dropbox.com/u/22580256/detectors2.zip


Thanks again.

[Anders]

I found the cause of the ForEach bug (it was the qualifiers as I suspected):

You start the ForEach loop in the same event as you set the "Quantity" value to 0.
MMF2's action order can be somewhat confusing (and is something I hope will change for MMF3)

A quick workaround for you:
Split up the event into two:

Every 00"-50:
Set Quantity of <Detector> to 0

Every 00"-50:
Start ForEach loop "count"

I will have a look at the ForEach PC sourcecode to see how that issue is avoided there.