Ashley's Forum Posts

  • We're aware the build service has had some issues with reliability in the past few weeks. We apologise for the inconvenience and we're keen to identify the problem and ensure it is fixed.

    Unfortunately the type of problem is very difficult to diagnose - as you may know from our bug report guidelines, it's important to have reliable steps to reproduce a problem in order to investigate it. We do not have any steps to reproduce the issue with the build service, and the problem appears to happen unpredictably after long periods of time, often taking several days or weeks before it occurs. Investigating a problem often involves trying dozens of potential solutions. Combined with the long duration before the problem occurs, this means investigating the problem may be a long term process.

    Nonetheless we're aware of the importance of the build service to many customers and so we will be taking steps to diagnose and resolve the problem. Part of this will be running diagnostics and maintenance on the build server. We are planning to do some work Wednesday December 1st (tomorrow) from 11:00 to 18:00 UTC. The build service may be fully unavailable, or only partially available, during this time. Once again we apologise for the inconvenience, but this work is likely a necessary step to ensuring the reliability of the build service.

    In the mean time if you need an alternative to the build service, you can run your own Cordova builds locally with the Cordova CLI, as documented in the tutorial Building mobile apps locally with Cordova CLI. Thanks for your patience.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It worked at the time of my last post, but it seems it stopped working again overnight. I've now rebooted it and it should be working again.

    I apologise for the inconvenience, but it's very difficult figuring out what could be going wrong here. I will take some time out tomorrow to run some diagnostics and maintenance and try to figure out what's going on.

    Please only post in English as per the Forum & Community guidelines.

  • I just tried a build and it worked fine.

  • — - Instant Games are a different service to Playable Ads. They have different requirements.

    1mrpaul1 - you'll have to contact Facebook about issues with their service, their restrictions, or their test tool. It's all under their control, and there's nothing we can do about it. As far as I'm aware, Construct complies with the restrictions stated.

  • Construct games require WebGL, and can run on WebGL 1 (it does not require WebGL 2, but will use it if available).

    WebGL 1 is virtually universally supported now - including in the Android WebView used in Android apps - so it should not be an issue. Even WebGL 2 is very widely supported now, especially since it's supported on iOS 15+ now.

  • Construct does not impose a limit. It will be whatever size the browser or system supports.

  • It looks like a bug. Please file it on our tracker following all the guidelines, as we need that information to be able to help.

  • Exported Construct games set the favicon automatically for you. See Icons and Splash in the manual.

  • A new empty project exported to HTML5 with advanced minification is just 210kb zipped. Even uncompressed it's about 500kb. Anything above that is the content of your project, which is up to you, not Construct.

    The technical restrictions on single-file Facebook Playable Ads are strange and contradictory. They set a maximum file size, and then also impose rules that cause the file size to increase, such as having to encode binary resources as text in base64. Even so, a new empty project exported as a playable ad with advanced minification is 166kb compressed, or again 500kb uncompressed.

    Facebook have been impossible to get hold of for any questions I had or for any technical support with quirks with their tooling. Do they count the compressed size? If not why not, since they seem concerned about the file size? Compressing it would be an obvious thing to do. IIRC, there was an option to use a zip of a HTML5 export; try using that if you can. Otherwise I'm afraid you will just have to work within the confines of their (partially documented and contradictory) limits. As far as I can see the engine overhead is reasonably low given how many features it has - and is certainly less than the 1.4mb you stated - so you'll just have to be careful with every single thing you add to the project.

  • It depends on the server and on the host. So it's difficult to offer any specific help with. Try contacting your host for support on the server configuration.

  • I don't think this is anything to do with the codec used, so I don't think that would help. Besides, using different formats is not always supported everywhere, which caused its own set of problems, which is why we made it use WebM Opus everywhere.

  • Use the Android exporter.

  • Text objects are drawn in to the canvas and aren't actually HTML elements, so CSS won't affect them.

  • It's not a limit for Construct, it's a limit built-in to browsers. For security reasons all sub-resource requests on the file: protocol count as cross-origin, as if they came from an entirely different website. Often that means requests fail or security restrictions block features from working.

    Some simple tests or more feature-limited engines might not have any issues, but Construct has a sophisticated engine with a wide range of features, and the browser security restrictions mean it always gets blocked. However as I said it shouldn't matter: if you want something to double-click and run, use a desktop exporter.