Of course, as long as the greenworks version you pick was compiled for the nw.js version you are using, you're good.
OrangeGreenworks - Steam Integration with Achievements and Time Log
● ARCHIVED · READ-ONLY
-
-
Of course, as long as the greenworks version you pick was compiled for the nw.js version you are using, you're good.
Thanks, I wouldn't ask otherwise but the version you're suggesting causes fully unreadable errors and such which were fixed in later NW JS releases. -
Can you link me any info about that?Thanks, I wouldn't ask otherwise but the version you're suggesting causes fully unreadable errors and such which were fixed in later NW JS releases.
-
Can you link me any info about that?
Yes.
[0814/200210.364:ERROR:process_info.cc(625)] range at 0x4492306e00000000, size 0x20b fully unreadable
NW JS developer told to use
https://dl.nwjs.io/live-build/06-08-2017/nw23-2bad83e-ca7d50f-ef801be-1ac5823/v0.23.1/ -
Hey Hudell! Just letting you know that I got it working on the Mac successfully. Thanks for the great plugin and all of your assistance here in the thread!
-
Hey Hudell! Just letting you know that I got it working on the Mac successfully. Thanks for the great plugin and all of your assistance here in the thread!
Can you give detailed walkthrough to get it working for it? I don't have a Mac and I want to support it. -
I just got it working too. What I did was copy the lib folder (with greenworks-osx64.node) and greenworks.js to Game.app\Contents\Resources\app.nw
Then throw in the following files into the lib folder from the sdk:
steam_api.dll
steam_api.lib
libsteam_apidylib (from osx32 folder)
libsdkencryptedappticket.dylib (from osx32 folder)
Also copied and overwrote everything from nw.js. -
Mac version crashing with 0x02000148 error.
-
Hello. I don't understand something: when downloading nw.js. How do I know which version should I use (x32 or x64)? Should I just go with x32 for all OS or should I make a build for each version and upload separately to Steam?
-
I personally just went with x32, which also runs on 64bit systems.
-
After I applied everything in the tutorial, when I initiate the game the screen and everything in it shows up "blurry" o.o I have to press "F3" key to make it go back to normal. Any way to make it permanent? I don't know why that happens :I
-
I had the same issue. Looks like it's due to some kind of window resolution bug (maybe the new version is slightly bigger).
Plugins that auto-modify window resolution (like yanfly's core) can correct it. -
I'm having yet another issue >.> The OrangeGreenworks.getAchievement('ACHIEVEMENT_NAME') command doesn't seem to be working correctly for me. It doesn't register my already obtained achievements. Could it be because the game is unreleased state? (it activates achievements fine so it isn't a plugin setup error).
-
My own game runs slower on newer versions of nw.js too. If you only use achievements (no steam cloud, stats or things like that) you can use an older version of the OrangeGreenworks that didn't need the newer nw.js.
@Hudell First of all, thanks for making this plugin!
I don't plan for stats, steam cloud or anything like that, I just want stable, functioning achievements.
In that case, what is the most recent version of all the files that I should use to avoid running slower? 0.7 of Greenworks & nw.js v0.17.3 & SDK 1.37)?
Sorry for my confusion, but I'm a little turned around after reading the instructions and this thread. :confused: Hoping to get it sorted out and working in the next few days for both Mac & Windows! :oops: Thanks again!
EDIT: I wrote the wrong versions of the files at first. -
This is the original version of the plugin: https://raw.githubusercontent.com/H...3974fa00ac4e8477fe46cc094/OrangeGreenworks.js
To use it you need to rename the default Game.exe to nw.exe and use greenworks v0.5 -
This is the original version of the plugin: https://raw.githubusercontent.com/H...3974fa00ac4e8477fe46cc094/OrangeGreenworks.js
To use it you need to rename the default Game.exe to nw.exe and use greenworks v0.5
But do all versions from then on out slow things down? I thought it was just the really recent ones, and that there might be a mid-period one that is an improvement over the original but doesn't slow things down yet. Sorry for such a nitpicky question! -
I haven't checked all of them.
-
Thank you! And do I need to rename the default game.exe if I use greenworks 0.7?I haven't checked all of them.
-
The older versions of nw.js had a bug in that it couldn't load native libraries if the nw.exe file was renamed (and the Game.exe is just a renamed nw.exe). I think they fixed it in nw.js 0.13Thank you! And do I need to rename the default game.exe if I use greenworks 0.7?
-
Hey,
I'm trying to get this working, but have encountered something strange. When I try to start my game (it does show it playing in my Steam profile fine), it launches a black box, but never actually starts up the game. I'm using the Windows 32-bit one (i'm on Windows 10) and have verified that i'm using the proper build and all and followed the instructions to the letter. What can cause this?
The libs folder has these in it:
greenworks-win32.node
sdkencryptedappticket.dll
sdkencryptedappticket.lib
steam_api.dll
steam_api.lib
Thanks!
Edit: Oh, it appears SRD's GameUpgrade is the culprit. Grr. Well, I guess i'll use an older version, since all I use is basic Achievements anyway.