Anyone noticing a massive frame rate drop when they build for xcode sim or device?
I am running at 60fps… works fine on windows and mac simulators… but if I build for device (or Xcode sim)… my frame rate drops below 10… and the app is unusable!
Note: The same app, built using graphics 1.0 daily build 1233 works fine.
Cheers
Update: Built Raycast sample app for device set to fps=60, and its pretty poor. Its fine in the Corona Sim
I’ve tested one of my physics-based apps with sprite animations @60fps.
It’s also using Particle Candy and Text Candy, and I see no noticeable frame-rate drop with Graphics 2.0 build 2004 when running on a device.
By the way…
(this goes for Graphics 1.0 and 2.0 builds)
For me, Xcode Simulator builds have serious frame rate problems, and I haven’t used them for a loooong time. The frame-rate drops get progressively worse as the size of the virtual device increases. iPad Retina for example is completely unusable.
I was told by a Corona Labs alumni that it was due to an issue with Apple. I filed a bug report with Apple (radar 11089495, 21 March 2012), but it got closed by them stating “Insufficient Information”, as I couldn’t provide them with enough detailed info about the issue.
Thanks for the info Ingemar… Do you mind telling me what ver of xcode you’re running? 5? Was there any settings you had to change when you upgraded to 5?
I am seeing a serious frame rate drop on my device… but only when I build with graphics 2.0 build.
Are you telling me you can set the frame rate to 60 for the raycasting sample app… and build for Xcode or device and see no major drop?
PS. I have used the xcode sim for testing before… it does suffer from some framerate drop… but nothing like this… and it never translated to my device.
I’m using Xcode Version 5.0 (5A1413) on OSX 10.8.5.
No special settings were done. Keep in mind that Xcode 5 will overwrite your Xcode 4 installation.
I haven’t tried the Raycasting sample though. Once I do that I’ll get back to you here…
Graphics 2.0 build 2004
I’ve got no frame-rate problems when running the Raycasting sample on an iPod Touch 3G (iOS 5.1.1), iPod Touch 5G (iOS 7) or iPad mini (iOS 7). (I changed the fps to 60 in config.lua)
Thanks ingemar… appreciate the info and testing… I’ve got a local issue it seems!
I am running 2003… so will update to 2004 and try it… cause Im not talking about a reduced framerate… Im literally talking a stuttering 5-10 fps… 
I’ll let ya know how it goes…
Thanks
ok, built the raycast sample for my iphone4/IOS7 with build 2004… at 60fps… works fine.
But my own app is still not.
Heres what I got.
An app that works fine in mac and win simulators on all builds of Corona…ie. public Graphics 1.0 1202… daily 1233… and graphics 2.0 build 2004.
If I build using graphics 1.0 builds, its fine.
If I turn on graphics compatibility 1 mode… and build with G2.0 build 2004… the framerate is about 5 on my iphone 4 IOS 7… and the app is unusable.
Anyone suggest ways to debug such a problem? I have the texturememoryused printing to the display but thats not working at the moment… so cant see if I have a memory issue in device builds with G2.0 2004.
Im stumped…
Cheers
Just a thought…
I’m just wondering if V1 compatibility mode may be logging a bunch of warnings in the device log, that maybe is slowing things down?
(Like the old days of BASIC where too many REMs would cause an application to come to a crawl 
)
The physics app of mine that I referred to above is fully converted to Graphics 2.0 (no V1 compatibility mode)
Yeah, has to be something to do with backward compatibility. But that needs to work, cause we cant go back a migrate old apps.
I might migrate some functions and test as I go to see if I can find the issue.
Love to hear about any graphics v1 apps anyone has built for device with graphics 2 builds…
Cheers
I think my problem is related to this, I have no frame rate problems (not that that I notice) except with iPad Retina
http://forums.coronalabs.com/topic/40385-performance-problems-on-ipad-retina/
But you have frame-rate problems even when you use “Graphics 2.0 syntax” (without V1 compatibility) right?
@cublah thks for the info. Yeah that sounds buggy.
I am going to migrate to graphics 2 where I can… Ie. anchor points etc.
I might also remove some functionality to see if anything particular is causing the performance to drop.
I just load my level… Transition to cam position and then do nothing. And my framerate sits below 10. My enterframe listener is not doing much until i touch a button so other than that its a couple of collision listeners
I didn’t use V1 compatibility, I went straight for Graphics 2.0
I’m just glad other people are seeing a problem too it means I’m not going mad :), I will use V1 until something is resolved
I only had a couple of instances of setreferencepoint… so removed those and turned off graphicscompatibility… app runs fine in G2.0 sim… but still crap on device.
Works fine if built with G1.0 builds… so I dont think I need to optimise my code… its fairly ok as far as I can see. Its a wip prototype so not too much going on at the moment either.
I was working on a completely new project for today and used graphics 2.0 syntax only. If someone would like to test it with his/her device then I can send you over the code. At this moment everything is based on Corona-made vector graphics.