A workaround is turning off subpixel antialising.

I found similar artifacts in the font rendering in this issue.

https://github.com/electron/libchromiumcontent/issues/384

The libchromiumcontent issue links to this one, which describes why this happens:

https://bugs.chromium.org/p/skia/issues/detail?id=6663

With a recent change, FreeType no longer adds LCD padding by default, but only when this is necessary. This changes the bitmap offset and size.

Maybe a solution could be to update the bundled version of Chromium/NW.js?

I am experiencing the same issue on Ubuntu 18.04, also with Nvidia GPU and nvidia driver.

This is very nice to know, tedivm. I will go on writing spacious code as usual then... Thanks for your help

Hi, am new to screeps and have a question regarding code style.

Normally I try to optimize for readability, splitting up things in many small functions and modules, and trying to make each part easy to comprehend.

My running code is just a prototype to get to know game and up the GCL, but I have started on writing something more robust.

Having read about the new game loop architecture and the CPU buffer, I am still somewhat concerned how careful I should be to keep the LOC count down.

I have read about the extra overhead when require()'ing many smaller modules. I will bundle things with webpack, but I guess there will still be some overhead.

Have any of you run into CPU trouble during initialization, even with the buffer?

Should I take care not to get the code base to big, at the expense of readability?

Note: I am not talking about performance in the loop, only time used for parsing the source code when the game state is cleared once in a while.