I know NW 10 is only an RC yet, but still, it seems the text object in general needs an overhaul.
Since not only this problem, seems to be one (Performance problem on mobiles).
But now to the problem, the problem persists since Chromium 35+ that means Node-Webkit 10 (RC1) too.
When the text in the text object changes, it either disappears/get invisible or get's "Blocky"
Example further down.
Note: The problem only exists when using WebGL renderer
As — already noted, the problems only exists when using WebGL.
When using Canvas2D the problems are non-existent.
[quote:tzh4ao5i]it seems the problem only occurs with webgl, not with canvas2d
Description of Capx
Launch it with either chrome or the most recent NW (10 RC1) with WebGL renderer, see the text being "Blocky" or maybe disappearing.
Launch it then with Canvas2D and see that there is no problem whatsoever.
A random btw note: The freezing problem in Node-Webkit can be resolved by adding the chromium argument: "--disable-threaded-compositing" as fluffrabbit noted.
So yes, it really fixes it. Already added it to my json file in the exporter folder in C2 Please make that change for r174 (If not Roger fixes this in general).
Steps to Reproduce Bug and use the Capx
- Launch it with either Chrome 35+ or NW 10 Using WebGL
- Watch the text being buggy.
Or it get's invisible, sadly i couldn't reproduce that.
It should appear like this:
- Chrome: (YES)
- FireFox: (NO)
- Internet Explorer: (NO IDEA)
Operating System and Service Pack
Windows 8.1 64bit
Construct 2 Version ID