Ashley's Forum Posts

  • An easier way to test ahead would be to install Chrome Canary and try previewing your game in that. It uses the same browser engine, auto-updates daily and you could set it as your "custom" preview browser. Note it breaks from time to time though since it doesn't get as much testing - the dev and beta channels are a little further behind but better tested.

  • Please file a new bug report following all the guidelines, or I cannot do anything about this. Apple's development cycle is so slow you'd be lucky to see a fix by iOS 10 in autumn. It's probably better for us to try and work around it (yet again). I did a lot of testing before the r227 release though - there shouldn't be any obvious problems (I hope)!

  • You've got to understand, while I am sure you mean well, to an engineer that kind of comment is not helpful. You need to follow the bug report guidelines, always, for everything, no matter what. A lot of our own bug guidelines also apply to other bug trackers. For example if you don't provide a demo showing the problem happening, there is nothing for an engineer to investigate. Like most software projects we get a huge number of false reports (50-60% of all our own bug reports aren't real bugs) so if you post a comment like that, all you'll get is a reply asking for an example showing it happening. I also still cannot look in to this any more myself for the same reason.

  • The new WKWebView export is designed for the new Intel XDK project format. I don't know if it works with the old format, but if you enable WKWebView, you must include all three of these plugins for it to work:

    cordova-plugin-wkwebview-engine

    cordova-plugin-file

    cordova-plugin-httpd

    If you disable WKWebView, you should not need any of them. If you use the new Intel XDK project format, or PhoneGap Build, those plugins are specified automatically.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The HSL effects should work fine if everything is opaque. Dealing with alpha in HSL mode can be very tricky but if you're not using that then the results should be correct. If you think anything is wrong please file a bug report. There is nothing in this thread I can investigate, and last I checked it worked OK.

  • This is straightforward to do with events, I don't see why it needs its own specific feature? You could just put all your input events in a group, and disable the group. Or check a global variable like you're already doing.

  • The original issue reported in this thread was identified as a Chrome bug, which was since fixed. If you are still having trouble, check Chrome is up to date, and if you're using something like the XDK you may need to wait a little longer for the Chrome update to propagate to the XDK.

    Since this is a closed bug report, if you still have trouble which you think is not related to the Chrome issue here, please file a new report following all the guidelines.

  • in all these time we could just had an APPLE PORT for CONSTRUCT 2.

    Why can't we just launch a rocket to Mars?! It's been ages and we have rockets and people, so why can't we just go there now?!

  • Closing as not a bug.

  • Please make sure you are using the latest stable release r227 - we fixed a bunch of bugs to do with audio already.

    If you still have trouble, please file a bug in the Bugs forum following all the guidelines, or it will not be investigated.

  • That's our code to work around WKWebView limitations. It should only be used if you enable WKWebView when exporting from C2, and then it should automatically add the CorHttpd plugin to the project (at least in the new Intel XDK project format...). It should work if you either turn off WKWebView or add the CorHttpd plugin.

  • Unless you can actually provide benchmarks that indicate a measurable difference, this is basically a waste of time. I don't see any real measurements proving there is an improvement, and I don't believe there is any technical reason for there to be any improvement either. Minification radically alters the code so much that the original formatting doesn't matter much, coding styles don't usually affect functionality, and I don't know what you mean by "compiling stability" or "reducing errors", the current code is still standards-compliant Javascript so will be parsed, compiled and executed more or less identically regardless of whether there are extra/missing semicolons, parentheses, etc.

  • Enable some of the backup options.

  • The .capx isn't helpful, we need the original .wav file that you are importing. Can you provide that?

  • Closing as not a bug, you are using the wrong expressions. To center something in the viewport, use (ViewportLeft("layer") + ViewportRight("layer")) / 2, (ViewportTop("layer") + ViewportBottom("layer")) / 2.