Export to NW.js problems - Breaks everything that works

Discussion and feedback on Construct 2

Post » Mon Apr 27, 2015 3:14 pm

Try using the latest from Scirra, and turning off minification.
@Ashley confirmed bug
Image ImageImage
B
169
S
50
G
169
Posts: 8,285
Reputation: 108,214

Post » Mon Apr 27, 2015 3:40 pm

@K3yshadow did it ever work without bugs in Node?

Since Node is just a paired down version of Chrome I wouldn't think it's the export. And since you tested with earlier versions of Node/C2 and you are still getting the bug it seem highly unlikely it's Node. Only saying that because this issue would have come up in the past 6 months with something as basic as OnOverlap

Could it be a performance issue? How is the FPS and cpu_utilisation?

I would try to snippet the code that is not working or behaving buggy and put that in it's own project. Then export to Node and see if you can reproduce it. If so, then you'll have something to submit to Ashley
B
97
S
32
G
15
Posts: 1,196
Reputation: 16,174

Post » Tue Apr 28, 2015 5:32 pm

So who wants to do the bug report?
Image ImageImage
B
169
S
50
G
169
Posts: 8,285
Reputation: 108,214

Post » Tue Apr 28, 2015 6:21 pm

I thought it was common knowledge that things work a little differently on export. So technically we've all been doing the bug report. For a long time.
Image
B
243
S
30
G
13
Posts: 1,787
Reputation: 18,770

Post » Tue Apr 28, 2015 6:47 pm

Well this is an identifiable bug.
Minification is breaking the current build.
I don't know if its the op's issue, since there's no word back yet.
Image ImageImage
B
169
S
50
G
169
Posts: 8,285
Reputation: 108,214

Post » Tue Apr 28, 2015 7:02 pm

For reference, I'm not using minification and it is still breaking my game when I export.
I haven't had the time to mess with it more but I will try to investigate further later this week.
B
42
S
23
G
18
Posts: 153
Reputation: 12,473

Post » Tue Apr 28, 2015 9:03 pm

Jayjay wrote:NW v10.5 is only version that works decently with our game, but we also found that we need to use Construct 2 r192 (anything newer or older breaks our game)


I don't know how it breaks your guys games, I'm using r203 and NW.js 0.12.1Alpha and my game works absolutely fine.
The moderators are corrupt and ban for no reason, especially that condescending neckbeard asshole Kyatric. The forums are filled with fanboys.
Banned User
B
22
S
7
G
1
Posts: 558
Reputation: 2,925

Post » Wed Apr 29, 2015 6:29 pm

Hey guys I just wanted to give an update.

So basically over the past couple of days I've been testing it and here are my results:

- The game using NW v10.5 currently works fine on the majority of computers. As far as I can tell, I've got it down to 0 bugs running on these machines, however working code had to be moved around to fix the random export bugs. I also had to eliminate all code using Overlapping at offset. Overlapping at offset appeared to be creating to many random problems in the export builds. So those have been replaced with player overlapping, trigger volumes.

- Unfortunately there appears to be one computer on the batch I tested on which flat out refuses to work with the NW exports. I have tried numerous things, including not minifying the code (which caused massive slowdowns... for some reason ><), but it just doesn't seem to want to work. This computer (when it works) appears to get stuck on one particular section which requires the player to overlap an trigger volume and left click.

- Despite this one computer which doesn't work, I'm going to go ahead and release the game. If someone gets the random game-breaking bugs that the one outlier computer gets then at least it'll give me more data so that I can attempt to fix it as right now I have no idea what is the causing the bugs. It's for this reason I can't submit a bug report, because I honestly don't have a clue where the bugs come from or why.

- It's important for me to note that this is a project with roughly 900 or events, and lots of assits. The game has been tested, A LOT, and as far as I can tell none of the random bugs that happen are due to the game's code. They seem to be attached to screen resolution (the game is running at a fixed 16:9 resolution), with each computer behaving differently (with each computer running a diff resolution from a resolution that matches the 16:9 screen resolution to completely square 1024x1024 resolutions).

SOOOOO.

My advice to those experiencing problems:

1) Try to avoid using overlapping at offset. Instead maybe use triggers, or something else which isn't as hit and miss in different resolutions.

2) Simplify your code as much as possible without breaking it. For example: If you have code which has bits disabled out, then delete the crossed out bits. Also try to make sure nothing, such as variables or various different events, crosses over.

3) Sometimes something as simple as rearranging a line of code to put it in front of it's queue, does enough to get rid of random bugs in NW.

4) Test on as many PCs as possible on as many different resolutions as possible. Something might work fine on one PC, but on another you might get game-breaking bugs, so always check them.

That's about it. I hope that helps anyone. If you have any more questions then feel free to ask. Hopefully I didn't make it to confusing... I'm pretty tried ><.

Moving forward I will probably continue to develop games using C2, however I'll just have to wait and see what the reaction is to this game and whether or not a lot more random bugs appear.
B
5
S
1
Posts: 16
Reputation: 432

Post » Wed Apr 29, 2015 6:46 pm

1) Overlapping at offset is a very important feature.

3) Events are read top-to-bottom and event order is more important than a lot of people think. Perhaps that's the real issue?

Proper bug reports should be made.
Image
B
243
S
30
G
13
Posts: 1,787
Reputation: 18,770

Post » Fri May 01, 2015 2:52 pm

Hey Tokinsom,

1) I realise that overlapping at offset is an incredibly important feature, but for me it created a lot of problems when it came to differing screen resolutions and NW.js. When someone booted up the game, I had no idea whether or not they were gonna get the bug and I believe that removing overlapping at offset helped me quite a lot when it came to containing the random bugs in the NW.js export.

2) Unfortunately these bugs weren't caused by events not being properly prioritised. By rejigging around the code I meant more like replacing code, getting rid of it completely or even in some cases moving events to certain triggers.

The bugs do appear to be random so I wouldn't even begin to know how to replicate them and unfortunately I don't have the time to do so. If they come up in a smaller project, and I can identify what's causing them, then I will most certainly report them. For now all I can offer to the community is my above post and the ways I felt I managed to solve the problems in NW.js exports.
B
5
S
1
Posts: 16
Reputation: 432

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: BadMario, jobel and 3 guests