Minimal capx are very effective to find bugs, but sadly they do not show the problem at its maximum for jerkyness, input lag or missed cols problems.
I know a full game(*) is absolutely useless for debug purpose, but sometimes I wish the Chrome team could see what it looks like on a full game project. The more things on screen, the more you can see the problems. For example, when I was using a previous Chrome version, my game wasn't just flawed, but really unplayable. And the same goes for Airscape. The minimum capx looked pretty ok in comparaison.
Anyway, I'm still in absolute love with C2, but the situation is so frustrating!
you can craft awesome games with C2, but if the framerate reaches 50 fps, your game will look like crap for sure.
The only solution for a few months is to make less impressive effects and hope for weak hardwares to run the game at a rock solid 60fps.
And forget about livestream / youtubers to like your game. And people watching them to decide if they'll buy it or not.
This time we can't use the "hey, let's bug Ashley with this! I'm sure he'll fix this in a week" magic card, we all know you can't do nothing for these issues.
I deeply hope this situation won't last for more weeks or months, I couldn't imagine to make another professional game this way.
(*) full game = more lively than sbperftest, which is alreeady great and has many sprites and particles, but no fullscreen scrolling backgrounds with parrallax layers or transparent elements for example. While screens become bigger and bigger (some are already getting 4k laptops for christmas), the GPU related problems will only be more important to handle.