Experimental Greenworks plugin

Discussion and feedback on Construct 2

Post » Tue Feb 02, 2016 12:10 am

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?
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,616

Post » Tue Feb 02, 2016 12:13 am

@silverforce r221 and NW.JS0.13.0-beta5
Image Image
B
26
S
15
G
143
Posts: 881
Reputation: 74,560

Post » Tue Feb 02, 2016 12:37 am

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. :(
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,616

Post » Tue Feb 02, 2016 12:53 am

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
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,616

Post » Tue Feb 02, 2016 11:23 am

Yess!! Finally a update for the new nw beta :D
Will try this out at home later today, hopefully it works fine and I'll have no worries of launching the game on steam in april :)
Website Twitter Indie Developer
B
20
S
6
G
4
Posts: 206
Reputation: 2,954

Post » Tue Feb 02, 2016 8:22 pm

Impossible to run preview with any plugin events in the project, including after the plugin is removed.

The solution to fix that (for others having the same issue) is to remove all events that reference the plugin, THEN remove the plugin.
B
89
S
47
G
25
Posts: 535
Reputation: 21,827

Post » Tue Feb 02, 2016 11:54 pm

Silverforce wrote: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. :(


Hey, I made a fix for the nw.exe not closing: nwjs-not-completely-closing-when-exiting-app_t166669?start=60
B
11
S
3
Posts: 135
Reputation: 1,309

Post » Wed Feb 03, 2016 12:50 am

AlexFrancois wrote:Hey, I made a fix for the nw.exe not closing: nwjs-not-completely-closing-when-exiting-app_t166669?start=60


More hacks and workarounds!! :lol:

Either way, GreenWorks is still not working so we'll wait and see.
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,616

Post » Wed Feb 03, 2016 10:58 am

Can I confirm this isn't safe to use on 221 with 13 beta 5 ?
B
11
S
3
Posts: 135
Reputation: 1,309

Post » Wed Feb 03, 2016 11:47 am

It worked fine for me with NW.js 0.13.0-beta5, that's what the plugin was built for. Trying it with an earlier version might have corrupted the app data folder - try renaming the project and starting fresh with the right setup.
Scirra Founder
B
403
S
238
G
89
Posts: 24,648
Reputation: 196,133

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 5 guests