Ashley's Forum Posts

  • In many cases we don't need all those fancy features from the text inputs.

    You should ask your players, or watch some people trying to interact with your own controls. Everyday computer users expect all those features to work, and will be annoyed if they don't.

  • I'd add that there's nothing Construct-specific about the network requests. When you use AJAX, the browser makes network requests the same way as any other page. However if you are making a cross-domain request that may have various implications, but those are all the same as if you were making cross-domain requests with any other web pages.

  • I don't understand why C3 doesn't pop-up message something like 'Hey, I saved this, but there is a huge problem with X that you need to fix now or the file will never open again'

    I'm afraid it's basically impossible to do that. It's entirely possible that Construct is saving perfectly valid data, and then it gets corrupted by a disk failure, a networking problem during upload, and so on. There are lots of ways corruption can happen which aren't Construct's fault.

    Construct also can't tell you if your hard drive is about to fail, if Windows is about to fail, if the building is about to burn down, if a flood is about to happen, if you're about to be hit by ransomware, or if your laptop is about to be stolen. So even if it was able to show some kind of warning, it doesn't mean your work is safe. You have to have regular off-site backups for that.

  • As noted in this blog post, text inputs are actually highly complex. I would strongly advise that you do not try to recreate one yourself. Instead you can customise the appearance of a text input - for example you can remove the border and background so it's transparent with just text, and use your own art as the border and background.

  • I would advise testing on real devices, as if you use an emulator or anything else, it could have completely different performance and so not tell you anything useful at all about how it will really perform on the actual device you had in mind.

  • Running Construct in NW.js is now deprecated and will no longer be supported (see the updated original post). Please switch to using Construct in the browser at editor.construct.net instead.

  • Construct's offline support means that it starts downloading the entire game on startup. So it's already loading it all at the start of the game. That does not guarantee that the download has finished by the time you try to play a video though!

  • Construct's web export has been working great on iOS for years.

    I am not sure what specific issues Unity had, but it doesn't sound like any problem Construct has had. Maybe it required WebGL 2? iOS has supported at least WebGL 1 for at least a decade, and Construct games work just fine with WebGL 1. It's ubiquitously supported so there is no fallback necessary.

  • We've launched a public beta of a new animation product Construct Animate! Read more about it in the announcement blog post: https://www.construct.net/en/blogs/construct-official-blog-1/announcing-new-product-beta-1589

    For now we're creating this thread to post feedback. So if you have any thoughts, let us know here!

  • It turns out a configuration change was made earlier today that caused some problems. We've rolled back the change and it looks like it's back to normal. Hopefully it will be working better now - once again apologies for the inconvenience.

  • The build server is up and running again, but I'm seeing a few timeouts occurring. We're still investigating what is going on. Apologies for the inconvenience, hopefully it will be back up to usual service soon.

  • Actually it looks like something else has gone wrong. I'm looking in to it now.

  • I was just doing some routine maintenance and the build service was offline briefly. It should be up and running again now.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • We did a recent blog post that demonstrated that even years-old mobile devices can safely manage around 10000 sprites on-screen at 60 FPS. So I think C3 will be more than capable of handling an intensive bullet hell game.

  • It works fine for me.

    "Status access violation" means the browser crashed, not Construct. So you'll need to contact the browser maker for support about that. You could also try using a different browser.