[Bug] No more soft scrolling

[JoKa]

I updated to the latest official MMF Build, so I guess I also have the latest iOS Beta?

I noticed that my platformer no longer scrolls smoothly. It used to run fine in standard display mode, now I tried all display options, but nothing helps.

[Anders]

Is this in the PC runtime or when you export it and run it on your iOS device?

[JoKa]

I only have this problem on my iOS devices, I'd say the PC runtime is not affected.

[Anders]

Any chance I can test it?
Which device are you testing on?

[JoKa]

I'm testing on iPod 3GS with iOS 5.1 and iPad 2 with iOS 6.

On the pad the game runs absolutely smooth (60FPS) and also on the old iPod, though the overall speed goes down to 30 FPS. Please check this version.

I've extracted a single frame with the current MMF version and send it via email. Nothing was changed in the code, but now it's quite choppy on iPad and choppy+even slower on iPod.

[JoKa]

This problem still exists with Build 257.20

I noticed this Xcode message which appears continously while scrolling, since it's triggered all the time it could have something to do with the performance drop:
2013-06-19 14:46:23.770 PvsYGold[18605:707] -[UIPickerView setFrame:]: invalid height value 81.0 pinned to 162.0

Not sure if it already appeared in the bug free version of the game made with the previous official MMF version, but I guess I would have noticed it.

[AyreGuitar]

JoKa - if I remember correctly that 'invalid height' error is to do with the List object. Not sure why it keeps happening though - it usually just happens once when created. Perhaps you're constantly creating/destroying a List object, or it's scrolling too?

[JoKa]

Thank you so much, that was a great hint, solved the problem!

@Andos: seems the List Object causes a massive slowdown when the frame is scrolling. I had one List in each level for testing and didn't remove it before releasing the game. It was invisible, empty and had no related code. Disabling Follow Frame also makes no difference, fortunately I could simply remove it. I assume it shouldn't cause such trouble, the problem didn't exist in the previous MMF Build.