@nick_sherman, when you put Windows 10 on that Window’s netbook, it’s going to slow down too. This is the nature of OS upgrades.
Rob
@nick_sherman, when you put Windows 10 on that Window’s netbook, it’s going to slow down too. This is the nature of OS upgrades.
Rob
Thx for your fast reply. I now have tried everything to speed up my system but it still isn’t enough to get the Corona simulator back to it’s original speed.
I noticed it’s mostly the physics effects which are slow, like something falling using gravity. Is there a possible technical explanation for this with Yosemite?
Daniela
UPDATE: I have figured out how to speed up the simulator now and here is what you can do if things are to slow:
Do not use the "zoomed in’ view of the simulator window because it is much slower in the big size. The smaller version is showing and calculating faster and things are working fine. I don’t know if this is because of the Yosemite update or if the Corona team has some influence to speed up the zoomed in simulator… maybe Rob can check it?
Thx again for all your help!
Daniela
What Mac are you running the Simulator on?
To answer this, the best thing to do is to go to the Apple menu in the top left corner of the screen and choose About This Mac. Post a screenshot of the window that appears as I’m interesting in why things might be slower though it’s almost certainly Yosemite (hopefully future updates will speed things up). Personally I find Yosemite snappier than 10.8.5
Be sure to obscure your serial number before posting the screenshot! Alternatively, PM it to me so it’s not out in the open.
Hello,
I have the same problem since the update to version 10.10. The simulator is much more slower. (I use the last daily build).
I also noticed some display bugs with particles of Particle designer, but only on certain devices (Borderless IPAD1 / IPAD 2, for example).
My Mac: MacBook Pro / 2.3GHz Intel Core i7 / 2.3 GHz Intel Core i7 / NVIDIA GeForce GT 650M 1024 MB
I work with 2D/ 3D software (Photoshop, Zbrush, Modo) that works with the same speed as before, no slowdown at all.
Thx for your help !
Same problem with me; all apps run normally or even faster with Yosemite; the OS itself runs way smoother; etc., but the Corona simulator lags like anything. I have an older Mac mini, but, like I said, everything else seems to be running fine. Could it be Java? I noticed before I could run the Corona Simulator on Yosemite, it required me to download “Java SE Legacy” or something.
The forum software won’t let me post my image for some reason, so here it is on DropBox:
https://www.dropbox.com/s/r3vewfurkgwnmkj/about.png?dl=0
I am running the new mac pro, 32 gig, d700 (video editing machine) and Corona also runs slower, it actually stutters now sometimes. The screen recordings I did with iShowU were always pretty stable. Now they you can see a performance dip.
Take Corona out of the equation. Is anything else running slower?
Nope, everything is running fine. But most things, are not as taxing as corona.
My video editing software is optimized for open cl, My 3d software for open GL. So the d700 cards can handle that without a hitch.
Audio also seems to stutter now sometimes.
I’m having a similar issue, building a prototype a couple of moving images on the screen. When I was using an older build of Corona it ran smooth (after upgrading to Yosemite), now I’m running latest corona build and it’s slow, very slow.
I’m seeing something similar here too. It’s definitely not Yosemite and it’s very simple to check.
Just try running the same project using build 2511 alongside with a previous build (for example 2398). The older build runs incredibly faster then the last one.
Here’s build 2398 & 2511 running the same project at 60fps
[media]http://youtu.be/U1ULyrn7ecA[/media]
FIY, the code is just something like this
[lua]
local circ=display.newCircle(0,0,50)
function repeatfunc(evt)
circ.x=math.sin(evt.count/10)*100+display.contentWidth/2
circ.y=math.cos(evt.count/10)*100+display.contentHeight/2
end
timer.performWithDelay( 1, repeatfunc,-1)
[/lua]
Ok, so I just did some tests and I’ve noticed that:
A ) 2511 has similar performance to 2398 (or other previous builds) WHEN there are few applications consuming resources
B ) With multiple apps running/consuming more resources (for example Chrome with a lot of tabs open), 2511 has much worse performance than 2398 (that keep running smoothly)
I just realized that starting with build 2511 the performance in simulator is especially worse if the project files are on a network drive / folder in OS X. Copying the files to the machine the simulator is running on speeds things up a lot. And this doesn’t only affect loading times but also general performance while running a scene.
Kind regards
Tobias
What release are you comparing 2511 to? I can’t think why you’d see a difference as that area of the code hasn’t changed.
Also, what kind of network drive? What version of OS X? Have you changed that recently?
Hi Perry,
build 2511 was the first release I recognized this. The release I used before was 2393a - I can check tomorrow if switching back comes with more performance. I currently don’t have a fps counter, so it is quite subjective.
Network drive is an Apple 1 GB Time Capsule - I am currently using OS X 10.9.5. I upgraded the system around the same time and my MacBook Pro seems to be slower in general, so this, as said before in this thread, could also have influenced the overall performance.
I have a composer scene with some particle effects in it. If I open the project folder on the network drive, the animations are significant slower compared to the same project running from a folder on my local machine. Switching from scene to scene is also slower - I think because of the loading time, but I can’t see why a running, loaded scene performance is influenced.
Kind regards,
Tobias
The behavior with earlier releases is similar. Perhaps it is a little bit faster, but there are different device skins, so it is not easy to compare. The slowdown using network folders is yet interesting.
My MacBook Pro (late 2010 model) practically crawled to a halt when going from 10.9 to Yosemite, making Corona unusable for development for me. In all honesty, EVERYTHING was dog slow. Even opening system preferences or about my mac took 10 seconds.
Upgrading my ram from 4GB to 8GB fixed all issues. It’s a shame that Apple can not even make their base OS run flawlessly in 4GB of ram, but hey, it was fixable for 150 dollars for me so no biggie. I would suggest all others here to have at least 8GB ram.
Any updates yet on the slow performance of the new 2511 simulator??
Any plans on improving this?
We’ve had some trouble reproducing this but today we made some progress on that and we are looking into it.
Engineering has addressed this in today’s daily build. People on OS-X 10.9 do not have this issue, it’s a 10.10 bug. It has its history in the early bugs that we were seeing in the 10.10 betas and mixing native.* objects with OpenGL. Anyway, that bug is still somewhat a problem in 10.10.
If your app does not use native.*, your CPU usage should return to previous levels. If you use native.* objects, your CPU usage will still be elevated, but not as bad. We’ve filed a new bug with Apple regarding this.
Rob