Node-webkit broken\incomplete WebGL\shader support

0 favourites
  • 2 posts
From the Asset Store
Comprehensive localization solution for Construct 3 projects, no addons required!
  • Link to .capx file (required!):

    Link to effect file used:

    Steps to reproduce:

    Export game as Node-webkit wrapper, or wrap exported html manually.

    Observed result:

    Flat texture without any bump mapping.

    Expected result:

    Bumpy and glossy DOOM 3 like texture.

    Browsers affected:

    Chrome: no, works as it should

    Maxthon: no, works as it should

    Firefox: partially - bump mapping works, but flashing during movement of ligth source

    Internet Explorer: this crap does not support WebGL at all

    Node-webkit: no bump at all, just a plain flat picture

    Operating system & service pack:

    Win 7 x64 sp1

    Construct 2 version:


    Extra details:

    Notticed that bump mapping effect that looks and works find in Chrome and Maxthon does not work at all in exported Node-webkit wrapper and instead texture looks just as flat as without bumpmapping.

    Tried to update Constuct 2 bundled version to latest version from site - aint worked.

    Tried to put DX9 43 dlls into Folder - aint worked.

    Tried to put arguments --enable-webgl --ignore-gpu-blacklist to package.json - aint worked.

    (full arg line, if this might help is this:

    • -disable-extensions --disable-plugins --disable-internal-flash --disable-popup-blocking --disable-software-rasterizer --enable-gamepad --enable-html5-camera --allow-file-access-from-files --enable-webgl --ignore-gpu-blacklist


    Tried however it shows cude and same results as Chrome and Maxthon browsers, so that means WebGL enabled but doesnt work right or not fully featured in Node-webkit.

    Also tried to get WebGL libs from Maxthon and Chrome and replace node-webkit shipped libs with them - aint worked as well.

    Googled a little and found more reports like this, which state that "WebGL looks ugly in node-webkit comparing to Chrome and other browsers".


    Yes, i used non default effect, but it does work like charm in chrome and Maxthon, so i think problem is not in effect but in NW, and i guess problem like this may happen with other shaders in Node-webkit.

    Also thats not exactly the problem of Construct 2, but since Node-webkit included as official exe wrapper i think you should pay attention to the fact that WebGL does not work well in Node and brakes game effects.

    Probably you should contact creators of NW and solve this problem together or move to another wrapper, maybe back to awesomium or maybe compile your own branch of node-webkit with latest chromium code?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Closing since we can't help support third party addons. It's not clear this is not a problem with the shader itself somehow relying on undefined behavior. If you can reproduce a problem with an official effect please post a new report.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)