— wow.. what a mess.. too many dependencies: C2, Chrome and NWjs

Add GreenWorks into the mix for folks who want Steam features.

Rather than Game Engine < - > Steam SDK... it's: Engine < - > NWjs/Chromium < -> Greenworks < - > Steam SDK...

I've only tested Xbox controller because I too thought that was what the default compatibility is for.

I've had no luck with the overlay thus far, but I could just be being stupid.

The overlay does not work for many NV GPUs. Even with the --in-process-GPU addition.

Strangely enough it seems to work with Intel GPU and AMD.

— can you just make a new version that blows away old saves so that it works going forward? are you just saying there's a problem with saving the "old way"? what is actually crashing on newer versions?

Newer C2 than R218 does not work with NWjs 0.13 alphas (Chromium 47). The alphas are the only NWjs that actually works with no issues. The new 0.13.0 betas are based on Chromium 48 which has introduced some bugs.

Newer C2 is designed for Chromium 48 based NWjs, ie the 0.13.0 betas, which is pointless because it's broken**.

**

Yup, me too, I am not upgrading from R218 and NWjs 0.13 alpha 7 because it just works. Older versions are crap with memory leaks. Newer versions crash.

Upgrading C2 makes it crash with the NWjs alpha.. it's a messed up situation again.

Hey, I made a fix for the nw.exe not closing:

More hacks and workarounds!!

Either way, GreenWorks is still not working so we'll wait and see.

You cannot. The new NWjs and Chromium build changed the way they handle save data, including the folder structure. [Why they did that, is beyond stupid TBH!]

It also ignores the set-path arg that works on prior NWjs.

NWJs file read/write works and it's what i did to make a custom save-system that is based on arrays and JSON text files instead.

And I reverted back to NWJs 0.13.0 alpha 7 and it now hangs black screen too, without the GreenWorks addon.

Probably the new C2 build killed it, as I was using r218.

This is not cool because 0.13.0 alpha 6 & 7 are the only functional PC export option that doesn't have memory leaks and/or performance/stutter issues.

I care about Achievements, but having the game break is worse. Ashley

Avast will actually cause C2 games with NWjs to crash or fail to start.

It false flag it and attempts to run the code in a sandbox environment.

I just tested r221 and NW 0.13.0 beta 5. Exported NWJs, same issue, black screen hang.

Going to remove GreenWorks and test.

ps. I've been using r218 with 0.13.0 alpha 7, as it's released on Steam. It works great but no Achievements.

Edit: Removed GW and tested, runs ok, saves are fine (I use a custom save system, using NWjs file read & write with JSON format arrays). But on exit (Browser Close), the nw.exe process won't close properly, remaining active. Prevents subsequent game launches.

0.13.0 beta 5 is non-usable in this state!

Bloody NWjs/Chromium, a step forward, a step back.

Btw, it hangs for my project when adding the new GreenWorks.

I'm on C2 r218, is it only for the most recent C2 build?

Plugin update Feb 1st 2016!

Thanks, and don't worry about MAC or Linux GreenWorks.

NWjs is bugged for those platforms. On MAC we get a red bar that's stuck on loading. Apparently associated with large numbers of asset loading causing a conflict. For Linux, no idea.