Ashley's Forum Posts

    • Post link icon

    It turns out Greenworks has to be rebuilt for every node-webkit update. The move from 0.10 to 0.11 broke Greenworks and the next update to 0.12 will break it again. Bah... this could be tricky to keep up to date.

    I think they are going to rebuild a version for 0.11 soon. Hopefully it'll also include a 64-bit Windows version too.

  • Changing opacity won't create any extra render cell work (it's not moving or Z ordering), but changing the angle counts as moving.

  • Would it even be useful to load layout XML files from Construct 2? Then everyone who wants to design levels for your game will (probably) need a C2 license, and you have to share a significant part of the source project in a ready-to-use form...

  • gumshoe2029 - the Javascript SDK allows you to include scripts which also work in preview mode, and doesn't require any modification after export.

  • As ever the answer depends on measurements. If you can measure an improvement, then yes!

    Ideally you would move any moving objects to their own layer, so the one using render cells is truly static.

  • dankhan - r191 is out now, could you give it a try and see if the issue is resolved?

  • r191 beta is out, could you confirm the issue in the original project is resolved as well?

  • r191 beta is out, could you try it out and let me know if it resolves this issue as well?

  • Closing, please follow the bug report guidelines and only post a minimal .capx with no unrelated objects or events. Please also make sure your steps to reproduce are absolutely clear; steps like "I created a sprite on the second layout" are ambiguous, since there are many sprites in the project and you didn't describe which one you chose, which makes it very difficult to be able to follow your steps and see what you are seeing.

  • Just a heads up to others in this thread - I've managed to fix a memory leak bug in C2 based off Colludium's report (thanks!). It affects all projects using Text objects, and leaks every time you preview. So hopefully this explains everyone else's cases of editor slowdown or crashes after 20mins+ of usage. When r191 is out it will be interesting if everyone can try it out and report if the issue is resolved.

  • Actually I just managed to fix that other bug - there is indeed a memory leak every time you preview a project with Text objects. That could explain this report (and a few others!). When r191 is out it's probably worth trying again to see if it's fixed.

  • Aha - think I finally got to the bottom of this. It turns out there was a small memory leak for every 'Text' object in the project every time you previewed. Your example uses nearly 1000 text objects so shows this pretty quickly, but it would in fact affect all projects using Text objects - it would just take longer. So it's a pretty serious bug! Thanks for managing to get it narrowed down to such a simple .capx, it helped a great deal in figuring out what was wrong. This should help everyone using C2 with large projects or using it for very long sessions.

    As it happens the fix also improves the editor performance when opening layouts and previewing, so in particular the example you provided should open and run a lot faster too.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Closing, please review the bug report guidelines. You have 52 events and a great many objects, so I will simply conclude that your events are wrong, as is very frequently the case with reports which do not provide a minimal .capx.

  • Are you using lots of Text objects? If so it may be related to https://www.scirra.com/forum/r190-global-layer-v-web-font-incompatibility_t120329.

    How many layouts are you opening, exactly? If you open say 50 then it's hardly surprising it would end up using ~2GB RAM. Also are you using the 64-bit version of C2?

    If you don't close the editor, but simply close the project and then re-open it, does that also improve it? (This will help identify if it's a per-project or per-editor instance issue)

    It is going to be very difficult to do anything about a report like this without a minimal .capx; we could sign the NDA etc. but as per our bug report guidelines, completed projects generally aren't actually useful for bug reports anyway. It is far more useful if you can isolate the problem in a new project with simple steps to reproduce (e.g. doing one thing over and over), a bit like the way the other bug report isolated a hang to using lots of text objects followed by repeated previews - and then there's no need to sort out NDA paperwork either.

  • I can still reproduce a problem even without any global layers or web fonts, so I think it's just to do with large numbers of text objects in the editor. I've already improved the opening time and I'm still investigating the hang after a few previews.