Experimental Greenworks plugin

Discussion and feedback on Construct 2

Post » Wed Jul 13, 2016 7:13 pm

Laptop with embeded ATI cards on Ubuntu14 have a steam overlay issue (well know by Steam and ATI) else linux export works well
Image Image
B
25
S
14
G
139
Posts: 876
Reputation: 72,510

Post » Thu Jul 14, 2016 3:46 am

rasulmono wrote:There are two ways for me: 1. upload on steam Linux and Mac build without achievements and overlay 2. forget about Linux and mac players (10% of all players or so).


For myself, I'd rather not show achievements linked to the game if it only works on some computers and not on all.
B
151
S
75
G
20
Posts: 1,793
Reputation: 22,749

Post » Tue Jul 19, 2016 10:50 am

does the greenworks plugin have any way to access if a game is owned in the steam library? trying to figure out how to check serial keys for an online game id like to submit to greenlight
B
11
S
2
Posts: 30
Reputation: 717

Post » Tue Jul 19, 2016 7:26 pm

@2dgamedev , greenworks doesn't support this feature... but steam API does
Image Image
B
25
S
14
G
139
Posts: 876
Reputation: 72,510

Post » Tue Aug 02, 2016 1:45 pm

Update!

I didn't succeed in building Greenworks myself last time, but two new pre-built versions of Greenworks have become available: one for NW.js 0.14.7 (the LTS branch) using Steamworks SDK 1.37, although for some reason this one omits the 32-bit platforms, and one for NW.js 0.15.0 (the second-newest) using Steamworks SDK 1.36, which includes all the platforms. I tested both and they both worked for me, so I've updated the original post in this thread with the new versions.

I also revised the instructions on how to get it working to be clearer. It's also important to make sure you match the right NW.js version and Steamworks SDK version for the Greenworks version you are using. If any versions are different it seems to cause compatibility problems. We didn't have a NW.js-for-C2 build for 0.14.7, so I added it to make sure you can match the versions exactly.

I don't know why the 0.14.7 release omits Greenworks for 32-bit Windows and Linux, but the 0.15 version has them all, so that looks like the best candidate for the time being. I don't know why the Greenworks team don't publish more releases, and I don't know why my own builds never seem to work (I may look in to that again if it's a long time before the next update), but hopefully at some point support for NW.js 0.16+ will appear too. NW.js 0.15 is based on Chrome 51 so that's a reasonably modern version to work with for the time being.

Since it's a bit messy trying to match an exact NW.js version and Steamworks SDK version, I don't think we can realistically ship the Greenworks plugin as built-in to C2. Since NW.js can update independently of C2, having a fixed Greenworks plugin version built-in to C2 would break easily. Assuming the latest releases work OK, I think it would be better to add another table to the scirra.com/nwjs page listing all the Greenworks plugin releases available and the NW.js & Steamworks SDK versions they use, and then you can download whichever you want to work with, instead of being stuck with some fixed built-in version. So I think that would be the best we can do for officially providing the plugin.

Let me know how everything works out.
Scirra Founder
B
399
S
236
G
89
Posts: 24,530
Reputation: 195,402

Post » Wed Aug 03, 2016 8:38 am

Whether its included in C2 or not isn't as important as having it functional. So far it's working well for me, I'm using the one for NW.js 0.13, everything ok.
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,616

Post » Wed Aug 03, 2016 12:39 pm

Ashley wrote:...Assuming the latest releases work OK, I think it would be better to add another table to the scirra.com/nwjs page listing all the Greenworks plugin releases available and the NW.js & Steamworks SDK versions they use, and then you can download whichever you want to work with, instead of being stuck with some fixed built-in version. So I think that would be the best we can do for officially providing the plugin....

That would be a much better solution that we have right now. Thinking about the users who don't necessary use the forum or know about this topic, you could also add some reference into the editor (like a new faded out object) that let's users know where they can download Greenworks (just like with NW.js). Or you can make bundles with the working NW.js and Greenworks plugin versions into a separate installer and create a new export option. Just thinking out loud. :)
B
135
S
33
G
17
Posts: 1,559
Reputation: 20,732

Post » Thu Aug 04, 2016 4:15 pm

Tested NW.js 0.15.0 with Steamworks SDK 1.36, the game works and shows up as being played on Steam, but no Steam overlay. I read the thread and apparently there's still no fix for newer NW.js versions? Adding --in-process-gpu did not work unfortunately.

Edit: I got it working. It won't work if you only export, modify and run the game in any folder. You have to run it through Steam. I just went to my game's folder on Steam, deleted everything and copied the new files over and it now works.
B
125
S
43
G
41
Posts: 849
Reputation: 28,260

Post » Wed Aug 17, 2016 4:47 pm

maybe use not latest version SteamSDK/ I see in my installed games oldy version steam_api.dll (2012) for HL )))
maybe use only one version and include this version to C2?
B
25
S
12
G
1
Posts: 37
Reputation: 2,190

Post » Thu Aug 18, 2016 10:57 am

We're not allowed to distribute any Steam SDK files.
Scirra Founder
B
399
S
236
G
89
Posts: 24,530
Reputation: 195,402

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 6 guests