Experimental Greenworks plugin

    do you recommend NW 10.5 for archivements, or for additional reasons? I'm using NW 12.2 and looks like its working fine.

    Also, does 0.4 work also for NW 10.5, or just 11?

    Danwood > NW 10.5 for achievements support, using Greenworks 0.3. You may have to add the --in process gpu- chrome arg so the notifications are correctly displayed on windows and linux)

    Aurel as far as you know, are there also other advantages in using NW 10.5 instead of 12? Also, how can i add the -in process gpu- chrome arg?

    PS: i'm a huge fan of your work and i'm developing a large project as well

    (Thanks for the kind words!)

    Once exported, you can edit your package.json with notepad.

    You'll find some " --enable gamepad" and other things in it.

    Adding lines like --ignore gpu blacklist" or "in-process-gpu" (look for other threads about this, you'll find many of them) will help your game to run alright on many configurations.

    Most of these tags don't work anymore on latest NW, that's why many of us are still using nw 10.5. It has bugs, but they're known, which helps a lot when using google to fix stuff.

    I need som help. It has been mentioned before but I can't find a solution.

    I have followed the steps and tried every version of the greenworks plugin and I always get this error when I try to run the game and on some versions it only crashes on launch.

    Uncaught node.js Error

    Error: Cannot find module './lib/greenworks-win32'

    at Function.Module._resolveFilename (module.js:336:15)

    at Function.Module._load (module.js:273:25)

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

    at require (module.js:378:17)

    at Object.<anonymous> (C:\Users\Linus\AppData\Local\Temp\nw9492_10344\greenworks.js:14: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)

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

    I'm using NW 10.5 if that has anything to do with it? And yes I have renamed the exe to nw.exe

    Thank you in advance

    UPDATE:

    Reinstalled construct and everything and even tried the latest node webkit and now the game launches with greenwork plugin but I only get black screen. What to do? Did you ever solve this Aurel

    Guys, for those that are using 10.5 NW, and greenworks 0.3, it wont work with the latest steam_api.dll

    I used one from 2014 to make it work.

    lwgames Thank you! This was the problem. The new SDK doesn't work with greenworks atm. So by using an older SDK it worked like a charm! No more errors or black screens. Finally I can upload my game.

    Ashley This should be updated on the first post so more people won't get stuck on this step for ages

    Jesus Christ I wish we can stop going back to using all these old SDKs and work arounds constantly.

    Are we stuck on 10.5 NW (with hacks to get it to work!) forever? Any day steam may do an API update and we're screwed.

    It needs to be said, this should be the priority Scirra!

    Hi, I'm sitting here with the game and downloaded both steam APK and the older version of greenworks. I'm a bit confused at the step that's bolded:

    [quote:20k41dsz]1. Rename package.nw to package.zip

    2. Copy steam_api.dll from Steamworks SDK in to package.zip. Note you must be using the latest version of the Steamworks SDK (currently 1.31).

    3. Rename package.zip back to package.nw

    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.

    5. Create a text file named steam_appid.txt in the same folder as nw.exe. This should contain nothing but your app ID on Steam. If you don't have one yet, for testing it seems to work if you just enter 123456, but it won't work unless that file exists and has a number in it.

    6. Repeat steps 1-5 for the win64 version, except this time copying steam_api64.dll from the Steamworks SDK.

    7. Make sure Steam is also running and signed in.

    8. Start the app and test if it works.

    After renaming package.zip to package.nw, what does it mean by EXE file? I'm looking for an executable file, but I'm not seeing it. Is it talking about your game with C2s Node Webkit icon or something else? Do I need to actually rename the game to "nw.exe" just as typed?

    Thanks!

    After renaming package.zip to package.nw, what does it mean by EXE file? I'm looking for an executable file, but I'm not seeing it. Is it talking about your game with C2s Node Webkit icon or something else? Do I need to actually rename the game to "nw.exe" just as typed?

    Thanks!

    Windows hide known filetypes by default. It's the file you run to run the game, usually your game's name. You have to go to folder options and turn off the "hide known filetypes" option.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    Hm, for me, the win32 game instantly crashes (nw.exe has stopped working) upon start when the greenworks object is included.

    I followed all the steps and checked twice. Might be caused by the fact that I am using the latest SDK right now?

    Pretty sad, I cannot access any previous sdk versions.

    (Win7)

    dhoeke Yep the old SDK is the cause of that. But if you include an older one like the one here it will work <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

    https://dl.dropboxusercontent.com/u/100 ... am_api.dll

    Thanks guys, I'll try this after work in a few hours. I'm literally at the last stages of getting the game on Steam.

    Anonnymitet

    Thank you so very much!!

    Now the application won't crash any longer. However, Steam won't show up within it... I guess that's probably because I'm using 123456 instead of the real app ID.

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