Ashley's Forum Posts

  • Oh, I just saw TinyPNG is lossy, so it will degrade the image quality to improve the compression. C2 is cautious and defaults to lossless compression, and only uses lossy if you tell it to (e.g. set PNG-8 in the image quality dialog), so it doesn't default to trashing your artwork. Still I guess extra options for lossy compression might come in useful.

  • All the Windows Store export options are under the "Windows Store" export option. There's a new item in the list in the next dialog in r209 for Windows 10 export.

  • "native" is getting harder to define, anyway. Would WebAssembly count?

  • Construct 2 has pretty good built-in export-time optimisations already. Remember there's no point using tools like this before export, since C2 will encode the PNG itself anyway during export.

  • Hmm, the error is kind of mysterious, Chrome doesn't seem to indicate why it's not working. If it doesn't happen with other servers I'd guess it's to do with Dropbox's server configuration, but I don't know what. The only consequence would be it disables the Chrome 'Add to homescreen' banner on Android, so unless you're desperate for that, you can ignore it.

  • I think that's what happens if you host on HTTP, not HTTPS. You can ignore it though, the service worker does nothing and exists only for the "add to homescreen" banner in Chrome for Android (which requires https).

  • This is a closed bug report. Note your reports will not be investigated unless they meet the bug report requirements.

  • Zynt - this is a closed bug report, it's the wrong place to ask. Besides C2 defaults to letterbox mode which defaults to the resolution of the device. The aspect ratio is a more important decision.

  • Kyatric - I don't think they were suggesting piracy, just that they had the option of using releases older than r209. That's OK, they're still there, but in the long term they will fall a long way behind the bug fixes, browser support and new features of the later releases.

  • The free edition can still use loader layouts. So if your project takes a long time to load, you can have your own layout to show the progress, and the C2 splash will only appear briefly before the loader layout.

  • Edge actually looks like it will be a great browser, on par with Chrome. The main problem is everyone will have to update their OS to Windows 10 to get it.

  • Most objects have an AsJSON expression and "Set from JSON" action.

  • The Free edition can still export. If you're using the latest beta r209 I think there's a bug which in some cases causes it to get stuck on the splash, and should be fixed in the next beta. If that's not the problem, please file a bug in the Bugs forum following all the guidelines.

  • You mean stretching to fill the window size no matter how different it is? I cannot understand why anyone would ever want this - it looks horribly ugly since it distorts the aspect ratio, and it trashes pixel art due to ignoring integer scaling. Also the engine uses one scale value and has no support for different scales on the X and Y axis, so this would actually be pretty difficult to support. So, some difficult work to support an ugly feature...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • What if it never gets better? How can you rely on third party if that can make C2 look bad if they do something wrong?

    Well, it already is better - check yourself by running Canary. In time that will make beta, which will then make stable. Given all browser makers have been putting in a great deal of development resources in to browsers for the past few years and Chrome and Firefox in particular pushing very aggressive 6-week release cycles, I find it very difficult to take seriously the idea that anything will stay the same forever, particularly when Google say they are aware of the issue and are working to make v-sync scheduling flawless.

    Modern software development without relying on third parties is practically impossible. For example some users suggest we use Haxe instead, which is just a different third party and we could equally be hosed by problems with Haxe. (I also doubt it has as much testing and development resources going in to it as Chrome does.) Imagine if we wrote an engine depending on XNA - Microsoft ended up dropping support for that. Or Silverlight - the same just happened (they officially announced recently Edge won't support Silverlight!) All platforms have their quirks and risks. Chrome's v-sync scheduling is a bug - it's been a problem for a while, but it's just a bug like any other - and as far as I can tell it's already fixed in Canary, where according to sbperftest on my dev machine the maximum jank is just 0.1ms off v-sync.