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.Of course, as long as the greenworks version you pick was compiled for the nw.js version you are using, you're good.
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.
Yes.Can you link me any info about that?
Can you give detailed walkthrough to get it working for it? I don't have a Mac and I want to support it.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!
@Hudell First of all, thanks for making this plugin!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.
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!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
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?