Experimental Greenworks plugin

    Ashley sorry to annoy you but are there any news on this?

    It turns out Greenworks has to be rebuilt for every node-webkit update. The move from 0.10 to 0.11 broke Greenworks and the next update to 0.12 will break it again. Bah... this could be tricky to keep up to date.

    I think they are going to rebuild a version for 0.11 soon. Hopefully it'll also include a 64-bit Windows version too.

    Ashley I see, thanks for the reply!

    I've updated the original post with a new link to a version of the plugin based on Greenworks 0.4.0, which supports node-webkit 0.11.x and also has 64-bit OSX and Windows support and a couple of extra features. I've also amended the steps to get the Windows builds working to cover 64-bit support. Let me know if it works for you.

    Ashley thanks Ashley!! I just saw the post, gonna try it out now.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    Ashley it's working perfectly, thanks!

    By the way, I'm not sure if it has been mentioned on this thread but you can fix the Steam overlay not showing up on Node-Webkit by adding the argument "--in-process-gpu" to the package.json file. Now pretty much everything works, even screenshots and streams.

    Since NW 11 stutter/janks, I've been using NW 10.5, I presume the process as described by Ashley in OP is identical (with Greenworks v3 alpha)?

    Edit: Hmm, It works fine with the v3 but with Greenworks v4, it crashes on startup, with error saying its missing the greenworks file. So I guess v4 is only specific to nw11 (I misread the "add support for nw11")...

    Got the overlay to work in Greenworks v3 with NW 10.5 by using the --in-process-GPU flag, adding it to the "package-win.json" as well as "package.json".

    Working smoothly.

    I have a user tell me this issue, does anyone know what's wrong?

    [quote:32v7fjns]Uncaught node.js

    Error: Access is denied.

    C: \ Users \ LG-PC \ AppData \ Local \ Temp \ nw8468_6777 \ greenworks-win32.node

    at Error (native)

    at Module.load (module.js: 354: 32)

    at Function.Module._load (module.js: 310: 12)

    at Module.require (module.js: 362: 17)

    at require (module.js: 378: 17)

    . at Object <anonymous> (C: \ Users \ LG-PC \ AppData \ Local \ Temp \ nw8468_6777 \ greenworks.js: 13: 18)

    at Module._compile (module.js: 454: 26)

    at Object.Module._extensions..js (module.js: 472: 10)

    at Module.load (module.js: 354: 32)

    at Function.Module._load (module.js: 310: 12)

    I have a user tell me this issue, does anyone know what's wrong?

    [quote:sm4d0lzy]Uncaught node.js

    Error: Access is denied.

    C: \ Users \ LG-PC \ AppData \ Local \ Temp \ nw8468_6777 \ greenworks-win32.node

    at Error (native)

    at Module.load (module.js: 354: 32)

    at Function.Module._load (module.js: 310: 12)

    at Module.require (module.js: 362: 17)

    at require (module.js: 378: 17)

    . at Object <anonymous> (C: \ Users \ LG-PC \ AppData \ Local \ Temp \ nw8468_6777 \ greenworks.js: 13: 18)

    at Module._compile (module.js: 454: 26)

    at Object.Module._extensions..js (module.js: 472: 10)

    at Module.load (module.js: 354: 32)

    at Function.Module._load (module.js: 310: 12)

    Does it work fine for you though?

    I got that same message when I used the wrong Greenworks version for my NW. Version 3 is for NW 10.x (10.5) and 4 is for 11.x. Also add the steam api file into the package.nw and rename your executable into nw.exe, after I did those things, it works fine.

    Yes it works for most people, I dont know why that user is having an issue.

    Seems to be a rare occurrence, a user also reported the exact:

    http://steamcommunity.com/app/338830/di ... 940828803/

    Uncaught node.js Error

    Error: Access is denied.

    C:\Users\user\AppData\Local\Temp\nw6404_17767\greenworks-win32.node

    at Error (native)

    at Module.load (module.js:354:32)

    at Function.Module._load (module.js:310:12)

    at Module.require (module.js:362:17)

    at require (module.js:378:17)

    at Object.<anonymous> (C:\Users\Louis\AppData\Local\Temp\nw6404_17767\greenworks.js:13:18)

    at Module._compile (module.js:454:26)

    at Object.Module._extensions..js (module.js:472:10)

    at Module.load (module.js:354:32)

    at Function.Module._load (module.js:310:12)

    I am experiencing this problem myself first hand now:

    Uncaught node.js Error

    Error: The specified module could not be found.

    C:\Users\admin\AppData\Local\Temp\nw7108_10511\greenworks-win64.node

    at Error (native)

    at Module.load (module.js:354:32)

    at Function.Module._load (module.js:310:12)

    at Module.require (module.js:362:17)

    at require (module.js:378:17)

    at Object.<anonymous> (C:\Users\admin\AppData\Local\Temp\nw7108_10511\greenworks.js:12:18)

    at Module._compile (module.js:454:26)

    at Object.Module._extensions..js (module.js:472:10)

    at Module.load (module.js:354:32)

    at Function.Module._load (module.js:310:12)

    //Edit: This error only occurs when the .exe isn't named nw.exe

    //Edit: This error only occurs when the .exe isn't named nw.exe

    The instructions in the original post specifically call this out as a requirement:

    [quote:32oad47m]4. Make sure the EXE file is called nw.exe. For some reason it doesn't work if the executable file has a different name.

    > //Edit: This error only occurs when the .exe isn't named nw.exe

    >

    The instructions in the original post specifically call this out as a requirement:

    [quote:mtf61kwc]4. Make sure the EXE file is called nw.exe. For some reason it doesn't work if the executable file has a different name.

    It also happens when its named to nw.exe so it isn't the problem. It seems to be a rare issue as so far only a single player complaint about getting that crash error.

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