Toby R's Forum Posts

  • Are you able to open the dev-tools and look inside the console for me? (NWjs plugin action > Execute on start of layout)

    I'm using a nightly build and it doesn't work for me for some odd reason, this could possibly mean that the new version has fixed this issue.

    Please share the content of the console, error/warning or whatever messages it lists you there.

    Just some initial info's on start. Nothing new in the console while it flickers.

  • I could not reproduce, I though it had something to do with one of the NWjs processes but I somehow doubt it now.

    Either way, I've noticed that one of the three processes is slowly but steadily increasing in memory use.

    This might have an impact on low-end devices but I'm not sure, I will keep on trying to reproduce it on my end.

    EDIT: Do you guys use dual-screen setups or one single screen?

    Dual-screen here, but the second machine I tested it on was purely on the laptop so one screen.

  • Hey newt, I'm opening a new topic to not changing the subject here.

    Could you elaborate what's wrong with inverted conditions? I never had any problems with it.

  • I've made a CAPX with this bug. Tested on two machines and reported as bug:

  • Problem Description

    There's a topic related to this issue which describes the problem (viewtopic.php?f=146&t=181268).

    Screen is sometimes flickering when there's an Audio action.

    Video of the problem which I made some time ago:

    Subscribe to Construct videos now

    This bug occurs only in fullscreen with NWjs 0.14.x and higher.

    Attach a Capx

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

    (There is another capx attached at the bottom of this post)

    Description of Capx

    I've added some background image so the flickering can be easily noticed. The capx itself is just a Audio->Play(tag) / Audio->Stop(tag) switch after each LMB click.

    Steps to Reproduce Bug

    • Run the project in fullscreen
    • Keep clicking LMB untill you see flickering (usually it takes less than a minute of fast clicking to notice)

    Observed Result

    Screen flickers from time to time

    Expected Result

    Not to flicker

    Affected Browsers

    • Chrome: (NO)
    • FireFox: (NO)
    • Internet Explorer: (NO)
    • NWjs version 0.14.x and higher: (YES)

    Operating System and Service Pack

    Tested on two machines:

    == Machine 1

    Windows 10

    GPU: nVidia Geeforce GT 635m

    CPU: Intel i7

    == Machine 2

    Windows 10

    GPU: Intel(R) HD Graphics

    CPU: Intel(R) Celeron(R) CPU N2840 2.16 GHz

    Construct 2 Version ID

    r239 (this issue orruced in previous C2 versions as well)

    EDIT

    Here is fully automated CAPX: https://drive.google.com/file/d/0BwT_0lczDpc9UHNHdWJJYjF4bjA/view?usp=sharing

    You just need to run it and wait.

  • It's not our problem if a screen recorder doesn't work. It's obviously a bug in the screen recorder app. I don't know what else to say. It's unreasonable to expect us to fix problems in other people's software.

    Imagine if I made a microphone that could record most things, but not the sound of birds singing. Obviously I need to fix the microphone. It is crazy to suggest the birds are singing wrong.

    Ashley, with all respect but comparisons like this one are wrong. You cannot compare a program to a bird. You know that. You cannot change the way an animal is giving a sound but you can change pretty much everything in the software.

    You can go with other comparison like: A customer orders a burger in McDonalds and they give him a burger with rotten cheese inside. So he tells them that the cheese is rotten and McDonalds replies "Sorry, but we didn't make the cheese, we get it from Gouda, so please talk to Gouda. The burger itself is ok".

    Obviously the customer will never go talk to Gouda, he will probably never buy in McDonalds again and will keep telling his friends that McDonald has rotten cheese in burgers. That's how customers see it.

    But again... comparisons are bad. We are talking here about software. I don't know if it's C2 or NWjs fault or screen recorders fault, but I believe it is in your business to not ignore this issue.

    If you say it's a screen recorder issue then I believe you as you know much more about C2 and all related soft than me. I have no reason not to believe you, but still I'd like to ask you to take care of the problem.

    C2 community is outstanding and people here greatly support this game engine. You know that raw C2 would not be that attractive as it is with all the plugins made by the community etc. but there are things which community shouldn't (IMO) and probably can't solve.

    Imagine if an ordinary developer write to the creators of some well known screen recorder. They see completely unknown developer (a unit) who has a recording problem with his indie game. They would most probably think that he is some newbie who can't handle the game engine correctly and send him back to game engine support as from their perspective, their software works well with all well known game engines for years now.

    But If you would make an official email as the creator of the game engine who has big technical knowledge and is able to give them all the technical info they need, then it would surely sound more serious to them.

    There's really not many popular screen recorders out there. I believe there's less than 10 which are popular and probably not more than 20 which are at least easy to find. So it's up to 20 emails.

    And a word about my case as an example.

    Within last 14 days I received requests from 69 youtubers who were willing to record a gameplay of my recently released game. Till today I have only 7 gameplay videos made by them. All those youtubers who managed to record it told me that they really struggeled to figure out how to do it. So there were only several stubborn guys. All the rest of those 69 were not that stubborn and they dumped it and took another game.

    And just to clarify. Those were not 69 scams. Those were real youtubers validated by KeyMailer.co system where you need to prove that you own a particular youtube channel.

    So I just wanted to highlight how serious this issue is.

    And BTW, even if NWjs fix the "--single-process" option, it won't solve the problem with desktop apps completely as latest NWjs is still causing screen flickering (there's a separate topic for that), so for now the only safe to use NWjs is 0.13.2 where "--single-process" doesn't work.

    If you decide to take care of this issue and you decide that you will contact those companies. I can help you to make a list of those recording softwares or help in any other needed way, just let me know.

    Thanks

  • Do you guys preload all sounds or are they playing (+loading in) for the first time?

    Sounds are preloaded at start of the game.

  • Just an update on this. I'm currently on r239 and NWjs 0.18.1, so the same setup I tested earlier and had no flickering. Now I just turned off and on music in my game (not in the code) few times and now it's flickering again pretty often when the sound is triggered in my game (but not everytime). Usually when my object hits an obstacle. Switching on/off music in my game is simply Audio->Stop(tag)/Audio->Play(tag).

    Just an additional thought: I noticed I could cause the flickering to happen more frequently when I spammed my jump button on the keyboard (W). It wouldn't really happen when I was just walking. For reference, my game is just a platformer and this was with the platformer behavior.

    I presume there's a sound triggered while you jump in your game?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • what NW.js version did you try with?

    I tried with 0.18.5 added manually as Scirra version is not there yet.

  • I tried manually with "--single-process" but still couldn't launch the game.

  • NWjs 0.18.5 is available (https://nwjs.io/blog/v0.18.5/). Looks like they've fixed the single-process bug (and gamepad). Haven't tested yet.

  • Okay now I'm really confused.

    I tried with NWjs 0.15 and I had no flickering any more as well.

    So I thought maybe it's something in the project. I use SVN as I work in team, so I reverted my project to the exact same state as when I was reporting this issue here. And still no flickering.

    Then I decided to make an exactly same setup as before so I reverted C2 to r234 and still no flickering O.o.

    I'm out of ideas now. It looks like it is related to something absolutely external. Windows version? Graphic drivers? Maybe Chromium 50+ is not compatibile with some drivers which has been recently updated?

    No idea, but tomorrow I will have an access to the second machine I had this flickering issue, so I'll test it there as well. But if it's related to the machine itself (I mean not to C2 or NWjs) then I guess it's still better to use 0.13.2 for a while now as this version is working well everywhere while 0.18 might work well only on PCs with latest Win, graphic drivers (or whatever it is) updates.

  • Anyway, do you have the link to the report for me? I'd like to check it out by myself.

    Yeah it's actually mentioned a bit up in this thread, but here you go: https://github.com/nwjs/nw.js/issues/4947

  • I think you got a game on Steam right (congrats btw), might want to check out their reviews.

    The more different setups we test this on, the better we can identify and hopefully find a fix for this bug.

    Thanks. I've released it with NWjs 0.13.2, so there will most probably be no feedback regarding this flickering. I'm busy with other things now, but once I'm done I'll try to replicate it and simplify capx as much as possible. We'll see if we can identify the issue. I think it is purely NWjs issue. There's no flickering when you test in Chrome. But I'm not an expert and as NWjs team ignored this issue stating it's not their fault, then maybe it's not. They know more than me. And it's also weird that it's related to the Audio plugin. I'll update the capx when I'm done.

    I'm still getting the flickering even after the most recent updates.

    Hmm... I'll surely give it some more tests. Thanks.

  • I'm very excited to announce that Ultimate Solid got featured on Steam!

    It's a first time our game got featured. I guess we should open a champagne and celebrate our "Achievement Unlocked"