Mathieu Anthoine Posted February 25, 2014 Share Posted February 25, 2014 Here is the two demos : With Pixi 1.4.2: http://yamago.com/site/html5/streaker/ With Pixi 1.5.1: http://yamago.com/site/html5/streaker15/ On Android Nexus 7 2013 in Chrome browser, the animations and the background are smooth with 1.4.2 (60fps) but hiccup in 1.5.1 (22fps)No problem with canvas rendering or on Desktop. Mat ? Have you some ideas about this weird behavoir ? Thanks for your help Quote Link to comment Share on other sites More sharing options...
Mat Groves Posted February 25, 2014 Share Posted February 25, 2014 Hey there! It would be interesting to see what may be causing the issue - my hunch is that maybe its because we moved from arrays to typed objects for matrix's within pixi. Is it a flat out slow down? or is it a more of an erratic frame rate? Thanks! Quote Link to comment Share on other sites More sharing options...
Mathieu Anthoine Posted February 25, 2014 Author Share Posted February 25, 2014 Hi Mat,I think it´s a bit of each, fps are an average of 22fps versus 60fps on 1.4 but there's also some variations, it isn't very stable.Ask if you want me to do some special tests.Don ´t hesitate to send me some tweaked pixi.js if you want me to check. Quote Link to comment Share on other sites More sharing options...
Mat Groves Posted February 25, 2014 Share Posted February 25, 2014 Thanks very much for the offer! Keen to get to the bottom of this one for sure, and two heads are always better than one Its a bit of an odd one really - I have been profiling the game on a htc1 and there is definitely somthing going on..Whats weirder is that the 1.5 has a 94% idol time whilst 1.4.1 has 70% idle time. Very quirky behaviour. A couple of things to try I guess that could shed some light. How does this version fair with the game? https://github.com/GoodBoyDigital/pixi.js/releases/tag/v1.5.0Also if you try changing request anim frame to setTimeout/setInterval just to test to see what happens that would be cool! Cheers! Quote Link to comment Share on other sites More sharing options...
Mathieu Anthoine Posted February 26, 2014 Author Share Posted February 26, 2014 Here are 2 new demos: With Pixi 1.5.0: http://yamago.com/site/html5/streaker150/ With Pixi 1.5.0 + setTimeout instead of requestAnimationFrame : http://yamago.com/site/html5/streaker150_timeout/ The version with setTimeout freeze totally on my Nexus and works as the other well on Desktop Hope it could help. Quote Link to comment Share on other sites More sharing options...
jcs Posted February 27, 2014 Share Posted February 27, 2014 FYI, I have the exact same issue. I only realized that it was a recent Pixi issue after reading this thread (and doing some testing), as I hadn't tried 1.4 on mobile. I've had WebGL turned off on android because the performance was so bad (but I'm getting ~60fps with canvas, so I was ignoring it for the time being) I've tried it on the Nexus 4, 5 and 7 with the same results - WebGL gets a frame-rate in the low 20s, Canvas right at 60 (once the JITter has settled, anyway) Quote Link to comment Share on other sites More sharing options...
Mat Groves Posted February 27, 2014 Share Posted February 27, 2014 Yeah its definitely a bit of a weird one! Some quirkiness going on with android webGL I think. Will aim to find out what the culprit is and share with you guys once I find out. Quote Link to comment Share on other sites More sharing options...
Mathieu Anthoine Posted February 27, 2014 Author Share Posted February 27, 2014 Great, Thank you Mat. Quote Link to comment Share on other sites More sharing options...
Jan Posted February 28, 2014 Share Posted February 28, 2014 Just wanted to update that I am also getting this issue on HTC One and Samsung S4 (an basically all the other Android phones with WebGL support). On S4 is especially bad with average of around 10FPS. Canvas flies like it should on 60 . Quote Link to comment Share on other sites More sharing options...
DesertEagle Posted February 28, 2014 Share Posted February 28, 2014 I get straight up browser crashes when I do transparency on graphics objects with current WebGL on Samsung Galaxy Note 3. Happens in both firefox and chrome, and can be replicated on samsung galaxy s3. Quote Link to comment Share on other sites More sharing options...
Mat Groves Posted March 1, 2014 Share Posted March 1, 2014 Hey guys - just updated the dev branch of pixi.js - I think the culprit may have been the default size of the webGLSpriteBatch was too large. If you could test to see if the latest dev works better that would be ace! Thanks! Quote Link to comment Share on other sites More sharing options...
Mat Groves Posted March 1, 2014 Share Posted March 1, 2014 I get straight up browser crashes when I do transparency on graphics objects with current WebGL on Samsung Galaxy Note 3. Happens in both firefox and chrome, and can be replicated on samsung galaxy s3. Hi there! Not sure what you mean by "do transparency with graphics" ? If you could provide an example I will definitely take a look for you and make sure it gets resolved. thanks! Quote Link to comment Share on other sites More sharing options...
Mathieu Anthoine Posted March 1, 2014 Author Share Posted March 1, 2014 Updated on this version : http://yamago.com/si...l5/streaker150/ It seems better even if I have the feeling that it's not as smooth as the 1.4 but it's really difficult to appreciate, the background is as smooth as the 1.4 version (it wasn't before your fix) but the main character seems to hiccup a little bit.Hard to say, maybe someone can complete the test. Good job anyway Quote Link to comment Share on other sites More sharing options...
Mat Groves Posted March 1, 2014 Share Posted March 1, 2014 Thanks for setting up a new build to test!Definitely seeing improvement now. The game runs faster now on my htc1 than the 1.4 version does - a solid 60 Would be good to see what others are getting too. Quote Link to comment Share on other sites More sharing options...
DesertEagle Posted March 1, 2014 Share Posted March 1, 2014 http://visualtimeline.elasticbeanstalk.com/g258.html Works on desktop, crashes on Mobile. There's a small chance it's due to using Scala JS, but had no issues prior to changing alpha values. Update: I forced the renderer in the newly uploaded version to be canvas. This fixes the issue. Thus, the only difference between the version that hard crashes the mobile android browsers and the one that works fine is the choice of autodetect versus canvas. I'm going to take the demo down for a bit and will put up a simplified a/b later. Thanks. Quote Link to comment Share on other sites More sharing options...
jcs Posted March 1, 2014 Share Posted March 1, 2014 back to perfect for me thanks Mat! Quote Link to comment Share on other sites More sharing options...
kid_karma Posted March 3, 2014 Share Posted March 3, 2014 My games were running at about 10fps on my Nexus 5 when using PIXI 1.5.Just tried the new Dev branch, and they're back up to 30+ fps, which is approx where they were with 1.4.2. Great job Mat! Quote Link to comment Share on other sites More sharing options...
Mat Groves Posted March 3, 2014 Share Posted March 3, 2014 My games were running at about 10fps on my Nexus 5 when using PIXI 1.5.Just tried the new Dev branch, and they're back up to 30+ fps, which is approx where they were with 1.4.2. Great job Mat! yippee! great to hear benny! 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.