Ashley's Forum Posts

  • Closing as fixed as per OP's post

  • The breakpoints feature should already support running events step-by-step. The problem with triggers is it's really hard to support them in browsers. It would be easy if we could "hang" the browser (just suspend execution) while you've hit a breakpoint, but browsers are specifically designed to make it difficult for pages to do that for obvious usability reasons. So the problem amounts to saving and restoring the entire JS execution stack. That's a really tough problem! We've simply skipped the future, but I would like to support it if we can figure out a way to do that.

    Showing the currently picked objects would be interesting, but I'm not sure what the UI would look like for that... how would you keep that clear & intuitive when there are potentially hundreds of instances being filtered from multiple object types?

  • Closing as does not follow the bug report requirements.

  • Try removing any third party plugins, or checking any you have are up-to-date.

  • johnsmith - note the non-webview Cocoon platforms have been deprecated for a long time now so have not been supported for some time. I don't know if that's what you're using?

    Anyways, it turns out there's another obscure property we can rely on to detect WKWebView. Apparently Cordova detects it the same way, so if iOS 11 breaks it, it will break all Cordova apps, not just our own Hopefully that is good enough for the future. So the next build actually brings back the "enable WKWebView" and "use new Intel XDK project format" options. I still strongly recommend using WKWebView where possible, since it is significantly faster!

  • Ashley - I understand that HTTPS will be necessary for hosting, but do you foresee an issue in the future with using getusermedia during the C2 development cycle itself(as we're just previewing on localhost)?

    Browsers actually treat localhost as a "secure context" as well as HTTPS, so all features should still work there.

    With preview-over-wifi it gets a bit tricker, since if you are previewing over an address like http://192.168.0.1:50000, that is neither HTTPS nor localhost so secure-only features like user media won't work. You can work around this in Chrome for Android by setting up port forwarding, which means you can visit a localhost URL on the device (therefore qualifying as a secure context) which is really just redirecting to the LAN address.

    • Post link icon

    If it's on the Scirra Arcade maybe we could help, but if it's just someone else's random game I would say just try to ignore it and move on, otherwise you might be another victim of the Streisand effect.

  • Events run at 60 FPS, so trying to make sense of a list which changes every 16ms, or trying to watch for the briefest of flickers as something highlights for 16ms only, seems to be a pretty difficult way to review what is running. Also it's probably more complicated to define "which events ran this tick" than you think - triggers can fire outside of the normal tick cycle, functions can run the same events multiple times, etc.

  • Closing as not a bug. crossdomain.xml has nothing to do with the CORS standard. The request should succeed if hosted on the same origin, but won't work in preview mode unless you specify the Access-Control-Allow-Origin HTTP header.

    • Post link icon

    I don't recall ever calling it a mere re-skin. We are rebuilding the entire editor from scratch.

    We'll have more news when we're ready to announce it. Until then sorry, you'll just have to be patient!

  • Features like this require HTTPS (if not already then certainly in the near future) so if you're not already on HTTPS, consider that the problem.

    Otherwise note that if you ever click "deny", sometimes the browser remembers that and auto-denies all future requests from the same origin. To get the prompt to show again you have to go and change the browser settings for the site.

  • SparklingAir - please file a new bug following all the guidelines, this report was fixed and subsequently closed.

  • I did look in to this and could not find anything wrong. If you want further investigation please try to find a more reliable way to reproduce the problem, or more clearly describe the exact steps and timing (perhaps a video would help), and file a new bug since this report is now closed.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • cristiart - please file a bug following all the guidelines so we can investigate.

  • Debuggers always have a performance impact - to truly test without the overhead of the debugger, you have to make measurements in non-debug (normal) preview mode.