Yeah - that's a good work-around, but it probably should be documented somewhere so it doesn't catch people out in future, at least until it's fixed in Chrome.
Outstanding progress
Ah, yes - text objects are more demanding to render, so it might be better to render the display using a sprite font instead.
Maybe it's not telling the truth - can you add a text object fps indicator as well to compare them side by side?
This is not a bug. If you check what the font looks like you'll see that this is by design.
Develop games in your browser. Powerful, performant & highly capable.
I just saw your comment in the closed bugs section, Quicksand - you could be right that the work around in this beta is the cause of this problem. Well, the original bug not being fixed is the real cause, but you know what I mean .
The symptoms I had was first start was OK, thereafter the preview/export would start to a background process unless the User/AppData/Game folder was deleted. I thought the antivirus bug was just a false positive preventing start?
No - I don't think it's to do with antivirus.
I tried v14 rc3 a few days ago and found that the old not closing bug was back, so I created and submitted a bug report to the nw.js github here a few days ago. Version 14 rc3 appears to be unavailable now - I am hopeful that this will help fix the problem. I would appreciate more experienced eyes on this just in case there's more that can be done to help them fix this that I might have missed.
MelVin, I created and submitted a bug report to the nw.js github here a few days ago. Version 14 rc3 appears to be unavailable now - I am hopeful that this will help fix the problem.
Avoid the Steam version - you will have more control over your purchase.
You would need to create a plugin for trialplay and/or one of the advertisers that are referenced in the facebook monetization page.
Member since 26 Aug, 2013