I agree Aphrodite, and hope I didn't come across too harshly before. I see the reliance on third party software as a strength and a weakness with c2. The strength is it allows our one man developer coding hero to focus on the editor; the weakness is it allows our one man developer coding hero to focus on the editor.
Ashley is right to play the long game, but by dismissing the current quality of c2 desktop exports as a temporary glitch (with an unknown fix date for people who don't have the confidence to use the command prompt and manage their own export - precisely the kind of person who buys a no code game engine) it makes it appear a bit like c2 is still in development.
Or rather, we feel every third party problem - but we have control over this one so we should exercise that control. As to Ashley's inability to reproduce the problem, it might well be a system specific issue, but I imagine that any hardware with less than awesome spec will be affected (must have a 60 hz screen, I think). This test was created by someone else and it clearly shows the problem in Chrome (sorry, can't go into Node).
I didn't mean to come over unappreciative of the work done so far by Scirra, I really highly rate c2 for its unique approach to game dev... but it sometimes feels like we don't know where the wind will take us next, or when.