Screen flickers

Bugs will be moved here once resolved.

Post » Sat Nov 12, 2016 8:39 pm

So it looks like it's Win10 (or Win8+) related issue as no one on Win7 is able to reproduce the issue.
ImageImageImage
B
27
S
16
G
79
Posts: 1,013
Reputation: 44,245

Post » Sat Nov 12, 2016 8:49 pm

Please provide your OS information, I would like to make sure that this is not a bug caused by buggy drivers and/or Win10.
We have to somehow identify the cause of this bug and then hope that Ashley or the NWjs team will fix it.

---

The bug is not occuring on my end, I'm using:
OS: Win7 (64bit)
NWjs: v0.18.5 & v0.18.6
Last edited by TheRealDannyyy on Tue Nov 15, 2016 12:50 am, edited 1 time in total.
ImageImageImage
B
63
S
23
G
78
Posts: 658
Reputation: 44,929

Post » Sat Nov 12, 2016 11:05 pm

Just an update.

Two people from C2 Discord channel (https://discord.gg/YfMsC5D) tested the capx as well.

The first person with Win 10 could see the flickering, the second person with Win 8.1 could not see the flickering. So again it looks like Win 10 issue.
ImageImageImage
B
27
S
16
G
79
Posts: 1,013
Reputation: 44,245

Post » Sun Nov 13, 2016 12:20 am

BackendFreak wrote:Just an update.

Two people from C2 Discord channel (https://discord.gg/YfMsC5D) tested the capx as well.

The first person with Win 10 could see the flickering, the second person with Win 8.1 could not see the flickering. So again it looks like Win 10 issue.



you forgot to mention win8.1 also has no problem recording the screen gameplay. :P
B
76
S
22
G
69
Posts: 1,353
Reputation: 43,833

Post » Sun Nov 13, 2016 12:23 am

gamecorpstudio wrote:you forgot to mention win8.1 also has no problem recording the screen gameplay. :P


Yeah but that's off topic. Recording issue post is here. We will have to do some more tests there as well.
ImageImageImage
B
27
S
16
G
79
Posts: 1,013
Reputation: 44,245

Post » Sun Nov 13, 2016 10:19 am

Deleted
Last edited by Je Fawk on Sun Nov 13, 2016 10:37 am, edited 1 time in total.
Black Bobby The Hole Greenlit with 303 votes.
B
36
S
8
G
1
Posts: 164
Reputation: 3,031

Post » Sun Nov 13, 2016 10:35 am

I asked for help with testing on Construct 2 Facebook group (https://www.facebook.com/groups/constru ... 876321205/).

One person says he has this issue on Windows 7 Ultimate. So it turns out it's not OS dependent.
ImageImageImage
B
27
S
16
G
79
Posts: 1,013
Reputation: 44,245

Post » Mon Nov 14, 2016 4:54 am

BackendFreak wrote:... One person says he has this issue on Windows 7 Ultimate. So it turns out it's not OS dependent.

I've got an idea about the NWjs issues and how we could determine if it's really NWjs/C2 or crappy drivers that are at fault here.

Since Armaldio got that Electron exporting to work, how about him or someone else that already tested out the "new" exporting method, export your example from this bug report using Electron and then test out if the issues are still occurring. I think that way we be at least 90% sure that it's NWjs's or C2's fault and not the fault of drivers that almost always get blamed on first.

I've posted this here because I felt like people that are not in our Discord should also know about our progress in finding a fix for these issues.
ImageImageImage
B
63
S
23
G
78
Posts: 658
Reputation: 44,929

Post » Mon Nov 14, 2016 5:44 pm

I've only sporadically been able to see the flicker, I can't reproduce it reliably, but I think I've seen it happen. It seems to only happen in fullscreen mode in NW.js, not in windowed mode, and not in fullscreen mode in Chrome. Can you confirm this is the case for you too?

If it's specific to NW.js there's not a lot I can do - I'd recommend reporting it directly to NW.js. One tip though: tests are better when they don't need user input, just replace the mouse click event with every 0.05 seconds or something like that.
Scirra Founder
B
397
S
236
G
88
Posts: 24,408
Reputation: 194,506

Post » Mon Nov 14, 2016 8:35 pm

Ashley wrote:I've only sporadically been able to see the flicker, I can't reproduce it reliably, but I think I've seen it happen.

So you knew the bug is there. This issue is there already for around 8 months. I believe it wasn't reported earlier because C2 community is very small and not many people update NW.js to the newest version each time it comes out. Also not many people actually make desktop games (mobile dev are majority I guess) and over that, it doesn't happen on every machine. And of course, most people don't care/bother to make a report.
So because C2 community is small it looks like it doesn't happen that often. But it does happen. And now imagine that someone makes a successful game which gets thousands of downloads on Steam. Customer review section would turn red for sure. So I just wanted to highlight that for whatever reason it is, your product is not able to provide a well working desktop app at the moment with the latest NW.js version (I mean the one which is able do be downloaded from Scirra's site). And until this is fixed by whatever party I suggest to announce NW.js 0.13.2 as recommended version for Construct 2 - just in case someone makes a great game and bring a huge sh*t storm on C2. So that's just my suggestion. Of course you will do whatever you find right.

Ashley wrote:It seems to only happen in fullscreen mode in NW.js, not in windowed mode, and not in fullscreen mode in Chrome. Can you confirm this is the case for you too?

Yes. We already mentioned that few times on the post related to this issue. It only happens in fullscreen mode in NW.js 0.14.x and up.

Ashley wrote:If it's specific to NW.js there's not a lot I can do - I'd recommend reporting it directly to NW.js. One tip though: tests are better when they don't need user input, just replace the mouse click event with every 0.05 seconds or something like that.


I've edited the bug report (first post here) and added automated capx.
This capx has only two events:
Image

Another thing I noticed is the dependence between the sound trigger interval and the sound's duration. The sound in the capx is 0.253s long. If we loop it to be triggered with 0.3s or higher interval then the flickering issue occurs.
However if we set Every X second condition to 0.1s for instance then the flickering does not occur. Also when we simply trigger this sound as looped, the flickering does not occur.

I don't know what's inside the Audio plugin, but I'm guessing that there's a - let's call it - "silence" trigger after the particular sound stops playing. It must be something common of Audio->stop(tag) function and when the sound has ended.

So it's not Audio->play(tag) which causing this flickering, but the end/stop of playing the sound.
ImageImageImage
B
27
S
16
G
79
Posts: 1,013
Reputation: 44,245

PreviousNext

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 1 guest