I can confirm 1.8 is way faster than 1.7.2 and the bugfix from 1.7.2 are NOT included in 1.8.
So either they fixed the performance problems in 1.8 or they are directly related to bugs fixed in 1.7.2.
Hi @jrosich,
thanks for the info! It’s good to know that v1.8 works fine (at leats the performance is fixed)! 
Maybe 1.8.1 will contain the bugfixes from 1.7.2…
Best regards,
Zsolt
Actually I found a bug related to tilemaps. getTiles() function doesn’t work on iOS. It triggers an error. Not sure if already happens on Android too, but Android works fine and my iOS build is broken. Already reported it on github. I guess if you dont work with tilemaps, its ok.
Thanks for reporting the bug. I feel that there are too many bugs in every release… 
There should be some kind of quality testing BEFORE releasing a new version.
it’s a small team of devs and they probably can’t test all user case scenarios on their own
I also found some performance issues with particle effects that went away when i deleted the ParticleSystem node in my scene and then added it back in
@jare
1.7.2 still has performance issues. See my post above… webGL framerate has been halved. Canvas is performing better sometimes. Do you know why is that?
Edit: im talking about Web. Android/iOS is fine.
do you have particle systems in your project?
I encountered an issue where particles were drastically impacting performance and all I had to do was remove the node, then add it back in
I’ve read your post. No particles yet in my project. Im leaving the beautify work by the end of the production.
Have you tried to profile the game using dev tools (chrome/opera) ? Use the Performance and Memory tabs to record some snapshots and take a look at which method calls are impacting the most and what is prolonging frame times.
Thanks for the feedback. We will check it later.
The version is the same.
Could be related to antialias setting, we are removing it in new versions, you can refer to this PR
How can I set antialias off before game starts?
I will try that, Thx!
See setAntiAliasTexParameters and setAliasTexParameters here:
http://www.cocos2d-x.org/docs/creator-api/en/classes/Texture2D.html
You will find examples in the “cocos-creator/engine” sources on the github.
Ive checked that and I see no examples on where to switch on/off antialias. And both functions you sent me have this text:
Deprecated use update function with filter options instead
And I dont know what it means with user filter options instead. Is there any doc about this @slackmoehrle?
Oops, are they deprecated?! Sorry, I’m still using setAntiAliasTexParameters to enable anti aliasing for my tilemaps… I think I’m going to update my code…
I can find out.