Gamua / Starling-Framework

The Cross Platform Game Engine
http://www.starling-framework.org
Other
2.84k stars 819 forks source link

Bad performance, low fps on some PC in Chrome web browser #929

Closed kolobok55 closed 5 years ago

kolobok55 commented 7 years ago

We have an game in different social network wrotten with Starling, but in some cases (don't know why) in same Chrome browser version and flash player has different fps. The problem can repeated with this link app http://ycanvas.yoz.sk/maps/ On my notebook in Chrome it has 4 fps, but in Mozilla 60 fps. I have seen this problem on the forum from 2014, but did not see solutions

PrimaryFeather commented 7 years ago

When you log the output of Starling.context.driverInfo on such a device, what's your result? Such a big difference in FPS would indicate that it's running in software mode for some reason.

PrimaryFeather commented 7 years ago

I just realized that with the lastest Chrome version, hardware acceleration was disabled on my 2011 MacBook Air as well — for whatever reason, they must have put it on a blacklist.

However, that was easily changed with the instructions from this stackoverflow thread: http://apple.stackexchange.com/questions/150212/hardware-acceleration-for-flash-videos-in-google-chrome

Does that help in your case, too?

PrimaryFeather commented 7 years ago

Any news on this?

IevotechAlexanderDorokhov commented 7 years ago

Yeap, I have news: Windows 7 + Chrome PPAPI player (release & debug) = very bad performance. Scout says that Context3D.setProgram(); execution is 90% of buget... So, it is not a Starling issue.

kolobok55 commented 7 years ago

We think, that problem in chrome: in some cases disabled gpu acceleration. Watch the performance in Adobe Scout, more than 50% time lost in Starling "Render" -> Stage3d. In mobile version even with antialiasing = 16 is perfect performance.

PrimaryFeather commented 5 years ago

Since I haven't heard any news about Chrome performance issues for a while (and I can't do anything from Starling to fight this, anyway), I'll close this issue now.