Thanks for the report, megatronx but the bug still exists.

I've done your suggestion several times in course of 2 years too. I tried with a clean installed OS before but got the same result.

This post is NOT about the bug report so I keep it short but here is a pic showing the remain problem.

This's done with Win7 64bit, C2 265 and NW.js 0.35.0. If you run with win10, the issue becomes more noticeable.

For further details, please read links I provided. AGAIN, it's a chromium or NW.js bug.

Using C2 or not, other people using NW.js have experienced the same issue.

My questions came from that there might be a workaround about the bug in a C2 code or exporting stage.

Because Previews give us a better result, could C2 give us the same in exported projects, couldn't it?

Was there a critical change about resolution or High DPI between NW.js 0.13.0 alpha 5 and after?

If other software using NW.js/chromium with the bug don't have the problem, maybe the software have some workaround?

Scirra can answer about my first question so I'd like to hear from them.

Thank you TheRealDannyyy

I tested your capx with r249 and NW.js 0.26.

The result is exactly same as I've posted.

If the window isn't resizable, it gives me a way off resolution.

(Browser)651x366 (NW.js)640x360

(Browser)491x278 (NW.js)480x270

If it's resizable, the resolution is close enough.

(Browser)641x361 (NW.js)640x360

(Browser)481x271 (NW.js)480x270

Then I turned on your workaround and the result is

(Browser)638x359 (NW.js)638x358

(Browser)478x269 (NW.js)478x268

An interesting thing to me is that "browser resolution" is off from "NW.js resolution", which gives correct numbers.

I've checked with the dev kit with my test and that is giving Browser resolution and that is what actually shown on screen I believe.

For now, we can use the workarounds.

Let's hope Chromium Dev fix this the bug.

And again, thank you for all of this.

I'm more an "artist" type. No idea what github and Chrominum are to be honest.

So it was hard for me to do all this stuff and I felt nobody look into the bug even after my report.

I'm really glad I found this thread and hope those info are helpful people who encounter the same issue.

TheRealDannyyy

Sorry for the late reply, I finally got around to do what you suggested: uninstal NW.js and "reset" the manifest files.

I also uninstalled and reinstalled C2. Just in case I deleted 3rd party plugins and behaviors too.

To be clear, I tested with r247, NW.js 0.26 downloaded from Scirra's page and win7/10 64bit on desktop PC.

I still got the same result. I did that with both win7 and 10 again.

Did "manually uninstall NW.js" mean:

Control Panel, Programs, Programs and Features, select NW.js and click uninstall?

That's what I did and if that's not what you meant, could you tell me how to manually uninstall NW.js?

Also I was wondering if you could upload your capx and exported file like I did last time so that

I could try them out. Sorry for keeping bothering you.

If anybody tries the test and share what you get here, I'd appreciate it.

TheRealDannyyy

Unfortunately, I still got the same result.

Just in case, I uninstalled old nw.js and then installed the new one.

I made a new fresh project and tested what you wrote before with win7 and 10.

Here are the exported file and Capx. I used r247 and nwjs26. The resizable option is unchecked.

Exported file https://drive.google.com/file/d/0B1SDO1 ... sp=sharing Capx https://drive.google.com/file/d/0B1SDO1 ... sp=sharing

I'm curious there are other people cannot reproduce the issue or not.

If that's the case, there might be something wrong on my end.

Sure, here is the capx.

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

The posts about the bug here can be a reference point for people struggling from it.

I hope either we find a workaround or the chrominum team fixes the bug.

I did the tests with nwjs 0.25 both Win7 and 10, resizable and non-resizable.

1. I got the same result.

2. Win10 and non-resizable gave me "652x370". The rests are the same.

3. I got the same result.

2+3. Win10 and non-resizable gave me "652x370" again. The rests are the same.

The same result refers to the post I did above.

So it affects somewhat win10 to set window size through the plugin.

To be clear, I did "System:set canvas size to NWjs.WindowWidth x NWjs.WindowHeight" as the manual setting.

If that's not what you meant, please let me know.

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.

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.

Problem Description

NW.js "set title" doesn't work.

Attach a Capx

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

Description of Capx

It only follows "Steps to Reproduce Bug" below.

Steps to Reproduce Bug

• Create new project
• Insert "NW.js"
• Add event: System: Onstart of layout
• Add action: NWjs: Set window title to "changed title"

Observed Result

Window title is showing an original "Name" which is "New project".

Expected Result

Window title should show "changed title"

Affected Browsers

• Preview NW.js: (YES)
• Exported NW.js(YES)
• Browsers(N/A)

Operating System and Service Pack

WIndows10 64bit

Construct 2 Version ID

r247(64-bit)

NW.js Version ID

NW.js v0.25.0

NW.js v0.13.0 beta5

I added NW.js version section since it's relevant.

It's useful if I want to keep project names in English but showing Japanese or any other language on window title.

I do not know NW.js set title affects web browsers or not so I put N/A.

When I export a C2 project as NW.js with "Minify script", the game is broken and shows only a black screen.

If I DO NOT use "Minify script", it just works fine.

C2 Spine plugin has the same exact issue so I don't know this is just how it works with FFD function plugins.

But I found a related post by Ashley on this matter.

https://www.scirra.com/forum/plugin-developers-please-test-with-the-minifier_t63774

I'd appreciate if you read through it.

mattar128

I have the same issue.

For some reason, when a game's screen resolution is changed, other normal sprites pop up.