Ashley's Forum Posts

  • rgba does take values in a 0-100 range, where 100 corresponds to 100%. However it is not limited to this range - you can pass 255, but that corresponds to 255% red, as in 2.5x more red than you'd normally get. This may be why you are getting unexpected results when passing 255 to rgba: it works, but not like you are expecting it to.

    If you want to use a 0-255 range, then there is rgba255 and rgbex255, which work identically but take values in a 0-255 range, where 255 corresponds to 100%. Again you can pass higher values like 500, but that corresponds to boosting that channel to higher than 100%.

  • All the crash message indicates is you were using the rectangle select tool. This is why we recommend people file bug reports following all the guidelines wherever possible.

  • Crashes are automatically logged to our server and we periodically review them. It's always helpful to have a full bug report following all the guidelines where possible, since we often can't fix crashes from the message alone. Otherwise you don't need to report it anywhere.

  • Again, the only permissions the Construct engine itself requests are (currently) INTERNET and WRITE_EXTERNAL_STORAGE. Anything else will come from an addon you are using.

    Maybe we need a better way to indicate what will cause extra permissions to be requested.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I filed https://github.com/Scirra/Construct-3-bugs/issues/3306 to look in to removing the default permissions.

  • You listed three other permissions though, including accessing USB storage and sending MMS messages. Those must come from other plugins.

  • Note rgba takes values in the range 0-100, not 0-255. It's also fine to pass floats to these expressions - any rounding or clamping is done internally in the expression.

  • Just place all objects the layout could use, on to that layout. Then destroy the ones you don't need on startup. That is how Construct's memory management is designed to work, and means anything you create will be visible immediately.

  • A vanilla export shouldn't request anything more than network access (if that...). It must be addons requesting those permissions. We'd need to see the project to work out which those might be.

  • Yes, we're already aware of this. Construct exports already default to the modern WKWebView, the only remaining references to UIWebView are internal to Cordova and they're looking in to eliminating them.

  • I think this is connected to the fix for this issue (Physics not working with worker mode enabled) which was fixed back in r154, but there was still a subsequent issue that if you exported a project using Physics and with worker mode enabled, then ran the project in a browser that doesn't support worker mode (like Firefox or Safari), then it fails to start up.

    Somehow this wasn't picked up in any testing since June, but r164 now has worker mode enabled by default in a stable release for the first time which probably is why it just came up. I've got a patch to fix this and I think this warrants a .2 stable release too since it seems a likely thing that others will run in to. In the mean time you can work around this by disabling worker mode in the advanced section of project properties.

  • The debugger can't show 2D or 3D arrays, so it lists elements on the X axis and shows the Y and Z axes as a comma-separated string. That's all that's going on there.

  • Did you export this with r164? It looks like the project has worker mode enabled, but fails to load Physics in browsers that don't support worker mode (everything but Chrome right now), which I think is a bug we already fixed.

  • You do not have permission to view this post

  • It's because you are creating an object not placed on the layout. This means Construct's memory management assumes it is not used on that layout, but then you immediately create it, so it has to load its textures on-the-spot. It is created immediately, but it can't be drawn immediately because the textures are still loading.

    It's simple to solve this... just place the object on the layout instead of creating it on startup! Alternatively if you only sometimes need it, destroy it on start of layout if you don't need it, rather than creating it if you do need it.