[UPDATED: 05.09.2017] The Big NW.js Roundup - Tips & Tricks

Discussion and feedback on Construct 2

Post » Tue Sep 12, 2017 3:35 am

Danwood wrote:I've noticed a huge performance decrease from v0.24 (affecting 0.25 too)

Anyone noticing it? Can someone confirm?


UPDATE: basically, versions 0.23.6 and previous ones, and also 0.24.0 beta1, are NOT affected by this problem. 0.23.7 and 0.24.0 onwards are. Seems like the problem is not related to chromium, but is caused by an update (maybe to Node.js?) made around 20 july...


So since im stuck with 0.24 on steam now, i guess ill have to wait and see if 0.26 is better..
B
26
S
6
G
2
Posts: 85
Reputation: 2,638

Post » Tue Sep 12, 2017 5:20 pm

@dimitriosfl ; @Danwood
Could one of you guys please provide me an example to do tests on? I'll report it to the NW.js team if their software is at fault.
ImageImageImage
B
64
S
24
G
78
Posts: 666
Reputation: 45,070

Post » Wed Sep 13, 2017 12:19 am

TheRealDannyyy wrote:@dimitriosfl ; @Danwood
Could one of you guys please provide me an example to do tests on? I'll report it to the NW.js team if their software is at fault.


Sadly i cant help coz i cant reproduce the issue.
On my pc (c2q+ati r5 230) works great. On a friends (c2d+onboard intel) stucks after 30min to 1h. On another friends (i7+nvidia980) also stucks.
B
26
S
6
G
2
Posts: 85
Reputation: 2,638

Post » Tue Sep 26, 2017 5:44 am

Possible addendum re changing the icon of the window frame (when exporting windowed mode), unless already covered somewhere that I might have missed:

change-the-node-webkit-icon_p1142409?#p1142409

In short: modify the "icon-128.png" found in the current project's /icon folder as it is used for the window icon.
B
42
S
12
G
1
Posts: 74
Reputation: 2,992

Post » Tue Oct 03, 2017 5:57 am

faulknermano wrote:Possible addendum re changing the icon of the window frame (when exporting windowed mode), unless already covered somewhere that I might have missed:

change-the-node-webkit-icon_p1142409?#p1142409

In short: modify the "icon-128.png" found in the current project's /icon folder as it is used for the window icon.


Just checked it out real quick and you are correct, seems like more recent versions of NW.js use the "icon-128.png" file and apply it automatically as the application icon when starting the application. This wasn't the case in older versions so it would be great to find out when this feature got implemented into NW.js.

By the way, it's not necessary to manually edit any icon files found inside C2's directory, editing the "icon-128.png" inside your project works fine.
Just in case for people that didn't get the "current project's /icon folder" part from your post.

Here are the steps:
  1. Click on the Project bar
  2. Click on the Files folder
  3. Click on the Icons folder
  4. Double-click to edit the "icon-128.png" file

I think I will add a <!> mentioning this, thanks for the heads up!
ImageImageImage
B
64
S
24
G
78
Posts: 666
Reputation: 45,070

Post » Tue Oct 03, 2017 7:46 am

Great thread. Thank You @TheRealDannyyy.
B
41
S
14
G
6
Posts: 154
Reputation: 5,546

Post » Wed Oct 11, 2017 5:09 am

Hi, I recently found this thread.
I'd like to share the bug I found ages ago which is about window size issue.

In short, the bug is about window size doesn't match with an intended size.
For example, if you set the size as 640 x 360 on C2, the EXPORTED(not preview mode) project give you 651x366.
The actual value may vary depending on NW.js version.

If you want to know more about it, please check this two threads:
https://www.scirra.com/forum/exported-nwjs-window-size-issue_t185331
https://github.com/nwjs/nw.js/issues/5337
I've updated what I've found a couple of time on the C2 closed bug one.

Lastly, If anybody could share some workaround beside what I found, I would appreciate it.
B
15
S
8
Posts: 12
Reputation: 1,314

Post » Wed Oct 11, 2017 7:27 am

taker7 wrote:Hi, I recently found this thread.
I'd like to share the bug I found ages ago which is about window size issue.

In short, the bug is about window size doesn't match with an intended size.
For example, if you set the size as 640 x 360 on C2, the EXPORTED(not preview mode) project give you 651x366.
The actual value may vary depending on NW.js version.

If you want to know more about it, please check this two threads:
https://www.scirra.com/forum/exported-nwjs-window-size-issue_t185331
https://github.com/nwjs/nw.js/issues/5337
I've updated what I've found a couple of time on the C2 closed bug one.

Lastly, If anybody could share some workaround beside what I found, I would appreciate it.

Thanks for sharing this in here.

It's not looking good though, the Chromium Team seems to be ignoring this bug for almost a year now, which is always a bad sign in my experience. I've responded to the Chromium thread and I'll add it to the list of Github bugs.

Are there any reliable workarounds for this?
Please include the most recently affected NW.js versions, if you tested them out already (main versions are good enough, no subversions).
ImageImageImage
B
64
S
24
G
78
Posts: 666
Reputation: 45,070

Post » Thu Oct 12, 2017 6:03 am

Thank you for leaving the comment, @TheRealDannyyy


So I investigated the issue with C2 r247, NW.js 0.25 and both win7 and win10 64bit.
Here are the exported project.

Vanilla https://drive.google.com/file/d/0B1SDO1 ... sp=sharing
Resizable https://drive.google.com/file/d/0B1SDO1 ... sp=sharing
Frameless https://drive.google.com/file/d/0B1SDO1 ... sp=sharing

Here are the result I got. An intended resolution is 640x360.

Vanilla
Win7 651x368 Win10 650x368

Resizable
win7 641x361 Win10 640x360

Frameless
win7 640x360 Win10 640x360


So actually the resizable does work with Win10 and it gives the closest result with win7.
I'd say the workaroud with nwjs 0.25 is using the resizable option, though I'd like to use with non-resizable windnow.
I wonder why this resizable option does affect the issue.
B
15
S
8
Posts: 12
Reputation: 1,314

Post » Thu Oct 12, 2017 11:20 am

taker7 wrote:Thank you for leaving the comment, @TheRealDannyyy


So I investigated the issue with C2 r247, NW.js 0.25 and both win7 and win10 64bit.
Here are the exported project.

...

So actually the resizable does work with Win10 and it gives the closest result with win7.
I'd say the workaroud with nwjs 0.25 is using the resizable option, though I'd like to use with non-resizable windnow.
I wonder why this resizable option does affect the issue.

Surething, always gotta push the Chromium Dev's a little so that they actually do something about it.
It's safe to assume that the window border is somehow at fault for this. Maybe we can find a way to workaround this issue.

Could you try out the following things on your end and share the results please (not all at once):
  1. Disable "high-DPI display" in your project settings
  2. Set the max/min window size using the NW.js Plugin (also try this with #3 if required)
  3. Manually resize the window on start of the 1st layout using the NW.js plugin

(No need to upload and share the files, just sharing your results is fine for this one.)
ImageImageImage
B
64
S
24
G
78
Posts: 666
Reputation: 45,070

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 7 guests