I just downloaded the latest SDK 2015.2646 as I had not updated for a while. Now when I run projects that are in App Stores the simulator is just hanging. It is jerky and runs so slowly it is unusable.
Please tell me that you have a solution in the pipeline…
Update on this - uninstalled the SDK and reinstalled latest version - same problem. Selected an older Daily Build - I went for 2015.2555 (just picked it an random to be honest) and it is back working great,
Matt,
Can you tell us a little bit about the hardware you’re running this on? There might be something new in the later builds that is reacting badly to your setup (or setups like yours):
Thanks,
Ed
PS - Did you notice any warnings in the console when you launched Corona?
PPS - When you say ‘App Stores’ you mean running the examples that come with the SDK right?
PPPS - For reference, I’m running Corona SDK 2015.2646 on my machine fine with this setup:
No warnings, no errors, just ran terrible - really slow.
When I say “App Stores” I mean previously submitted projects which are currently on Play Store etc. I used these projects as I new they worked!
My set-up is: -
Windows 7 Pro - 32 bit (!)
Intel i5 2.4 GHZ
Ram - 3GB 
NVIDIA GeForce GT 330M
Samsung Solid State Hard Disk (which is awesome)
We made some changes in the Windows simulator in build 2585. Can you try that version and see if you are having problems with it? Build 2583 is the build before the change, so if 2585 is not working, does 2583 work?
Do any of the Corona samples fail to run correctly or is it only your own projects?
We have fully tested the released version of the Corona Simulator on all Windows OS (including Windows 7) and have not seen any problems nor have we had any users report any problems like this, so this may point to something in your system that is not working correctly.
-Tom
2585 is working OK.
Will try a later one - see if I can find the build!
OK, the build where it all goes wrong for me is 2631. 2630 works a treat, 2631 does not work for me.
I note from the release notes for 2631 there is Windows: Maintenance…
Any ideas what this work could be? Anything that could effect my Windows 7 spec (32 bit machine etc)?
Thanks for narrowing down the build number that’s failing. We need to know what is failing to work correctly. Can you run the Corona samples and tell us which ones are not working correctly (specially the sprite animation samples). What APIs is your apps using that you feel are running slow?
If we know of a specific set of APIs that are working poorly or what Corona Sample app is showing the problem, that would help pin point what is happening.
Thanks,
Tom
Hi Tom
Bad news I am afraid. Most of the samples appear to be running very poorly. Horse Animation is shocking as it Jungle Scene. Tried Compass and that just did not load. Bullet is very jerky.
Really odd - seems to be anything graphical (which is almost everything!). Slide View project would not load at all. Status Bar hardly loads - very, very slow and jerky. Hello Physics is the same.
Nightmare really - what work was done in 2631 then? I am going to un-install this one and get back 2630…
Just a thought Tom, this is not a 32 bit issue? Have you any test bed Windows 7 machines which run on 32 bit architecture like mine?
I’ve been doing regular testing in some x86 environments – as far back as Windows XP. No issues with performance that I’ve found. I tried to reproduce it, but comparing 2630 and 2631 side by side on all the environments I could yielded nothing of use. Both ran fine.
Is there any further information about your machine that you can provide? We don’t have any access to your particular hardware. Make sure you are using the latest drivers from nVidia.
Nothing special Tom. It is a bog standard Dell Lap-top. Bought off the shelf. Runs lots of other software, loads of Microsoft stuff, Photoshop, Office etc. Are you not able to allude to what work was done in build 2631?
OK, hold the phone guys, just updated my nVidia drivers and we are back on! Latest version is now working!
Interesting that something in that build was not compatible with my old nVidia driver. Anyway, all sorted now so take the defcon level back down to normal levels.
Thanks for your help and suggestions guys… I was starting to get a panic on!!
Alright – we did touch on some OpenGL stuff, but we didn’t do anything that should be causing massive performance issues. We probably hit a bug in the old driver, which has since been fixed on their end.
Glad to hear everything is back to normal for you.
Update on this - uninstalled the SDK and reinstalled latest version - same problem. Selected an older Daily Build - I went for 2015.2555 (just picked it an random to be honest) and it is back working great,
Matt,
Can you tell us a little bit about the hardware you’re running this on? There might be something new in the later builds that is reacting badly to your setup (or setups like yours):
Thanks,
Ed
PS - Did you notice any warnings in the console when you launched Corona?
PPS - When you say ‘App Stores’ you mean running the examples that come with the SDK right?
PPPS - For reference, I’m running Corona SDK 2015.2646 on my machine fine with this setup:
No warnings, no errors, just ran terrible - really slow.
When I say “App Stores” I mean previously submitted projects which are currently on Play Store etc. I used these projects as I new they worked!
My set-up is: -
Windows 7 Pro - 32 bit (!)
Intel i5 2.4 GHZ
Ram - 3GB
NVIDIA GeForce GT 330M
Samsung Solid State Hard Disk (which is awesome)
We made some changes in the Windows simulator in build 2585. Can you try that version and see if you are having problems with it? Build 2583 is the build before the change, so if 2585 is not working, does 2583 work?
Do any of the Corona samples fail to run correctly or is it only your own projects?
We have fully tested the released version of the Corona Simulator on all Windows OS (including Windows 7) and have not seen any problems nor have we had any users report any problems like this, so this may point to something in your system that is not working correctly.
-Tom
2585 is working OK.
Will try a later one - see if I can find the build!
OK, the build where it all goes wrong for me is 2631. 2630 works a treat, 2631 does not work for me.
I note from the release notes for 2631 there is Windows: Maintenance…
Any ideas what this work could be? Anything that could effect my Windows 7 spec (32 bit machine etc)?