Ashley's Forum Posts

  • I think the "sad face" icon means the GPU driver crashed, or your game used too much memory and crashed. Check the memory usage is reasonable and try updating your graphics drivers.

  • As noted, you can't pathfind over an unlimited area, as doing so would require an infinite amount of memory.

    You could set the layout size to the largest you'd need to use, and then implement custom scrolling boundaries within that to simulate using a smaller layout.

  • Export with the NW.js option and make sure one of the Linux platforms is selected. It exports more files than the ones you stated.

  • If preview does not load, press F12 and check the browser console for any error messages. It's difficult to help without that information.

  • Is there any way to debug on these phones to identify the problem?

    Only Google can identify this kind of problem. As I said before, if you run in to a performance problem that only affects the APK and not the browser, please file an issue with Google at crbug.com with details about the device.

  • Yes, all functions are global. It's easy to check: just create a project, add a second event sheet, add a function, and see if you can call it in the other event sheet. You can. I noticed the manual entry does not specifically state that though, so I added a note to point that out.

    But no, being global does not mean it has to be checked every tick. Like triggers, they only run when they are called.

  • I think this could prove very complicated, since you could accidentally make thousands of expressions invalid in your project, if you did a find-replace that produced invalid syntax. There would have to be some way to prevent that, and that may in turn prove sufficiently limiting that the feature doesn't do what you want it to any more.

    Find-replace is also notoriously error prone - for example if you do a naive text-based find and replace for "text" with "label", and buried somewhere in thousands of events you have some dialog shown in game saying something like "In the right context we could...", that will also update to "In the right conlabel we could...". Now you've mangled a bunch of your game's dialogue in hard-to-find ways that will only show up after hours of playtesting. This is such a common problem that whenever I want to do find-replace myself in Construct's code, I actually just do a find, and manually update all the results so I don't end up making that type of mistake. So I would suggest a similar approach in Construct is wise - and you can already do it that way.

    For the most part, if you rename something in the editor, like an object name, it automatically updates all its references in the rest of the project. So it kind of exists in that form already.

  • You do not have permission to view this post

  • I just checked and it seems to be working fine for me. Maybe check your Internet connection is working.

  • 700mb is a very large memory requirement for a mobile game. I would guess the app is crashing due to running out of memory. See Remember not to waste your memory.

  • We are unlikely to do this as it might draw new customers away from Construct 3. Construct 2 also uses commercial libraries that would make it difficult to open source.

  • You will need to use the postMessage() API to communicate with an iframe.

  • If you run in to a performance problem that only affects the APK and not the browser, please file an issue with Google at crbug.com with details about the device.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I'm not familiar with the Unity tool, but you can repeat mesh distorted images with Tiled Background.

  • The last few tests I did on a Pixel 3 appeared to run perfectly smoothly.

    Once again, I think the only good way to investigate this and find out what's really going on, is to file an issue at crbug.com with details about the specific device. Any jank/webview-specific performance issues are beyond our control, so only Google can investigate and fix them, and the more issues are filed about this, the higher they will prioritise it.