RMMZ Greenworks crashing "Steam is not running" with MZ

[ninjaconor]

I'm having a weird issue getting Greenworks to work with MZ.
I am using Greenworks with Cyclone-Steam. It kept crashing when calling greenworks.initAPI(), so I changed this to call greenworks.init() as I am told this does the exact same thing but with more verbose error messages.

Now when I start the game I get the error message "Steam initialization failed. Steam is not running."
The things is, Steam is definitely running and greenworks is definitely interacting with it. In steam itself it shows me as being in my game while this error message is showing.

I have tried various versions of the Steamworks SDK. I am currently using 1.5.0.
I have tried changing my nwjs version, from 0.48.4 to 0.49.2 to 0.76.0 and have tried the greenworks files appropriate for each version as described on this site.
No combination seems to work, and this doesn't seem to be well documented online. Does anyone have any experience with this?

 

[matthewwells]

I am having exactly this same issue. Would love to hear if you have found a resolution or if anyone knows the answer.

 

[matthewwells]

@ninjaconor Is your app completely set up in Steam? I found this line in the Steam documentation for initAPI:

false indicates one of the following conditions:
...
Your App ID is not completely set up, i.e. in Release State: Unavailable, or it's missing default packages.

My app is definitely not completely set up. My build has been approved but not my store presence. Hilariously, I went down this rabbit hole because the people who approved my build said I might want to look into why my overlay doesn't work.

Additionally, I've been able to verify that literally every other part the Steamworks API I care about works correctly. I can update stats, register achievements, get my user profile, check my app ID (it's correct), etc. The init function is the only thing not functioning. I'm crossing my fingers that this will just start working when my app is approved.

 

[ninjaconor]

@ninjaconor Is your app completely set up in Steam? I found this line in the Steam documentation for initAPI:

My app is definitely not completely set up. My build has been approved but not my store presence. Hilariously, I went down this rabbit hole because the people who approved my build said I might want to look into why my overlay doesn't work.

Additionally, I've been able to verify that literally every other part the Steamworks API I care about works correctly. I can update stats, register achievements, get my user profile, check my app ID (it's correct), etc. The init function is the only thing not functioning. I'm crossing my fingers that this will just start working when my app is approved.

I think my release state is fine. I mean, I haven't actually released the game to the public yet, but it's been approved for release. I've even had a few reviewers play it with early access keys. As far as I can tell that should be enough but it apparently isn't.

 

[matthewwells]

Damn. There go my hopes that getting to a release state will magically fix this issue.

 

[matthewwells]

@ninjaconor One of the other things we both have is common is that we are using a Greenworks built for Steam SDK 1.5.0. I wonder if there's some kind of bug in the Greenworks/Steam SDK bridge in this version. I had the idea of trying to grabbing a version of greenworks built for Steam SDK 1.4.0 and NWJS 0.48.4 (I never tried changing that after reading your post). Unless you've already tried this? I'll be able to try this out myself on Saturday.

 

[matthewwells]

Make that 1.4.3. I also just checked and there appear to be two versions of 1.5.0, one that was built 7 months ago, and one that was built 25 days ago. I've been using the one that was built 25 days ago. I take it from the date of your initial post that you've been using the one from 7 months ago, the one with the v0.6.0 release tag?

 

[matthewwells]

@ninjaconor I've confirmed that this is a problem with the v0.7.0 version of Greenworks. I downloaded the v0.6.0 matching NW.js 0.48.4 and changed only my greenworks-win64.node file. This version of Greenworks also v1.5 Steamworks SDK, so no changes were required to those files. In local testing, the initialization error disappeared and the isSteamRunning method started returning true. No overlay, locally, but from my research, that's to be expected. After uploading a build to Steam and running my game through the Steam client, the overlay began working.