Ashley's Forum Posts

  • It's up to GameJolt to support PWAs. You'll need to contact them about it.

    Alternatively if you put a HTML5 export on your own web host, providing it is a secure (HTTPS) host, it will automatically be a PWA.

  • The latest releases have a new sub-layers feature which lets you do this efficiently. You can put all the layers you want an effect on as sub-layers of one layer, then put the effect on that one layer.

  • It's built as a universal app, so it's meant to include both the x86 code for older Macs and ARM code for the M1 Macs. However we only recently got an M1 Mac and I just checked it, and it looks like it doesn't work. I don't know why that would be - I'll have to look in to it.

    Construct 2 was taken off sale in July 2020 and fully retired in July 2021. It is no longer possible to purchase it. Upgrade to Construct 3 instead.

    Closing thread as "the illegal thing" appear to be references to software piracy, discussion of which is obviously not allowed (as per the Forum & Community guidelines).

  • You just need to provide the required id parameter, e.g. new SDK.PluginProperty("object", "my-object-param-id").

  • The instructions in the original post should work for any platform NW.js supports: Windows, Mac and Linux. However I would advise to use Construct in the browser wherever possible, as it has almost all the features of the desktop build, and is more reliable.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • - Watermark in Build

    - Limitation of screen resolution (game resolution)

    In an education setting I doubt either of these would provide any incentive at all to purchase the software, so we'd lose loads of sales, and possibly go out of business.

    - Limit storage space size for assets

    You could probably make the same arguments about why limiting the size of assets restricts teaching uses.

    The whole point of the free edition limits is they are meant to be slightly painful so that the incentive is there to purchase a plan, as we need sales to stay in business.

  • Does it still happen in the latest beta release? If so please file an issue.

  • Go back to a recent backup.

    If you can reproduce what caused the problem in the first place, please file an issue following all the guidelines.

  • If you want a quick way to debug the current layout, the Shift + F5 keyboard shortcut does that.

  • Just visit editor.construct.net in a browser. If you don't log in or use an access code, you just get the free edition as a guest.

  • Someone else just posted about how much you can do with just 50 events. I think there is indeed quite a lot of scope to do things within that limit. You can certainly make interesting mini-games and such.

    Something I've noticed from around a decade working in commercial software is no matter what the free limits are, someone will come along and argue there should be more available for free. We have to run as a business though. If we give too much away free and nobody buys the software, we'd go out of business, and then the software wouldn't exist at all. You can throw around some big changes to the whole business plan, but I can assure you many of them would also totally ruin us. We have our own unique market and niche and we've put a great deal of thought in to it already, and I'm pretty happy with where we've ended up.

  • error dns probe finished nxdomain

    This sounds like a problem with the configuration of your domain name. That is nothing to do with Construct - you'll need to take it up with the domain registrar or the web host.

  • I had everything that moves down the screen under an "Every Tick". I just had to change that to "Every 0.016 seconds" to simulate the same speed at any refresh rate.

    I would advise against doing that - very small times in 'Every X seconds' can still actually be framerate-dependent, as noted in the manual. For example if the game dips to 30 FPS on a slower machine, "Every 0.016 seconds" will actually be running every 0.033 seconds, and hence the game slows down in a framerate-dependent way. Also at higher framerates like 120 FPS, you'll have a janky appearance from moving things at a lower framerate than the game is actually rendering at.

    The correct solution is, as before, to use dt. There is probably some movement happening in "Every tick" that isn't using dt and ought to be using it.

  • It probably just means you're not using delta-time correctly. You can take the stock games in Construct like Kiwi Story and run them in unlimited framerate mode, and they work exactly the same. Here Kiwi Story can run at 2500FPS+ and it's pretty much indistinguishable from 60 FPS.