drhayes Posted April 20, 2015 Share Posted April 20, 2015 Here's the bug in the Chromium project. Please star this issue to tell the Chromium project that fixing this bug should be a huge priority if they're going to be serious about supporting HTML5 gaming. You can see a comment from a representative from Scirra (makers of Construct 2) at the bottom. Link to comment Share on other sites More sharing options...
rich Posted April 20, 2015 Share Posted April 20, 2015 This should be sorted soon when they release their new Display Sync code into Chromium that finally sorts out all of the horrible vsync issues Chrome has. Link to comment Share on other sites More sharing options...
drhayes Posted April 20, 2015 Author Share Posted April 20, 2015 Thanks goodness 'cuz it is NOTICEABLE right now for me on 42.0.2311.90. Have you heard if/when it's going to make it into Canary? EDIT: Don't know if the fix Rich is talking about specifically landed, but I'm not seeing the issue in 44.0.2376.0 canary if anyone else is affected. Link to comment Share on other sites More sharing options...
mwatt Posted April 21, 2015 Share Posted April 21, 2015 Yeah it's bad. To get a better picture of performance during development, I have been using Canary, which seems to have less issue with this. I have heard also that plugins can cause this. Link to comment Share on other sites More sharing options...
Recommended Posts