Ashley's Forum Posts

  • Sorry, videos are not normally any help in fixing bugs. Please see the bug report guidelines.

  • Thanks, should be fixed in the next build.

  • UI is the hardest and most time consuming thing to implement, and this kind of feature sounds like it needs special dedicated UI, where you go through a giant list of all your global variables and enable/disable them or something. Considering there's what seems to be a pretty easy workaround, I'd rather not do difficult implementation work for something this minor. Our time is probably better spent on things people want more.

    We've announced several hires on our blog now, by the way.

  • OK, should be fixed for the next build.

  • The flickering happens because shadows aren't drawn for tile areas just outside the viewport, which is fixed for the next build.

    The shadows look wrong though because you use multiple shadow light objects, and they only draw shadows, so by default all the shadows get pasted on top of each other. You need to use layering and blend modes to correctly render multiple light sources. See the demo that ships with C2 for an example.

  • Thanks, should be fixed in the next build. But it looks wrong in the editor itself as well, which you didn't mention, do you see it correctly there?

  • Sure, why not just do it on the forum?

  • It looks fine on my system, and graphics drivers are the #1 cause of crashes and glitches in the editor, so I still think it's that.

  • The features suggested here sound an awful lot more complicated than just having a function call that copies the global variables you want to keep to local variables, does a "reset all", then copies the local variables back to globals. That is pretty straightforward if you only want to preserve a small number of global variables, which I assume is the case?

  • Closing as will now follow up at https://github.com/nwjs/nw.js/issues/5477

    So you knew the bug is there. This issue is there already for around 8 months.

    I only just saw it, and the report to NW.js was only just filed, and this report is under 2 weeks old. If the NW.js issue was filed 8 months ago, then the developers would have an 8 month head start on fixing it (so it could well have been fixed by now). That's why I encourage people to report third-party issues directly where possible. It didn't really make much difference that I saw it happening and it wasn't really necessary to wait until then. Often you can cut me out of this process.

    [quote:243ppa8c]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

    Bugs happen, and sometimes they happen in third party code. There is nothing new, special or interesting about this case. In native tech, it could be that broken graphics driver completely hose your game on a whole range of graphics card models, and the vendor does not have a reasonable bug report system. This happens to the extent that AAA games launch in an unplayable state. This isn't so bad in comparison.

  • Actually it sounds like some software configuration on your system has changed.

  • Yeah, browsers let you tab in to canvas fallback content (for some reason), and then pressing enter selects a link.

    I vaguely remember reporting this some time ago, but IIRC they wouldn't fix it since it's an accessibility feature or something. You could just delete the fallback content (stuff inside the <canvas> tag) after exporting if it bothers you...

  • Closing

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Can't reproduce here on Windows 10 with an nVidia GTX 1070. Sounds like a graphics driver issue. Check your drivers are up-to-date. Closing as probably not a C2 bug.

  • 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.