Ashley's Forum Posts

  • The URL is not valid. Please provide a valid URL to the .capx file.

  • Generally I would say if you can translate a term, you should. The goal of translating C3 is so that somebody who does not speak *any* English can use it and make sense of it. I think trying to leave some terms untranslated to try to teach them English terms is counter to this goal. On the other hand apparently some English technical terms are de-facto standard terms in other languages too, so it doesn't make sense to translate them. (I guess this applies to things like "WebSocket".) I don't know the language so such decisions are up to you, but try to focus on someone who doesn't speak a word of English - what would make their life easiest?

  • I think --ignore-gpu-blacklist would prevent the software renderer ever being used anyway. I guess if you literally don't have a GPU (or it's a headless system or some such) then it actually should fall back to the software renderer, so I guess it's better to remove --disable-software-rasterizer anyway. I think those systems are pretty rare, and surely nonexistent amongst gamers, so it's pretty academic. So it should be fine to just delete that flag, which is what the latest betas do.

  • Other proof is that the same device *used* to work with chrome a month ago, and the same device apparently works with Chrome Canary and Chrome Dev, just tested.

    Well, that sounds like a Chrome bug that just got fixed then - so it just means waiting for the fix to make its way down to the stable channel.

  • It could automatically redirect you, but then it's awkward if you actually want to use r89. The current system at least gives you a clear, 1-click choice.

  • The beta versions have a different URL, e.g. editor.construct.net/r92 for the r92 beta. The stable release runs on editor.construct.net. If you bookmark/add to homescreen/otherwise load editor.construct.net, you're loading the latest stable release (currently r89). Then if you've opted in to get notifications about beta releases, you'll see a notification.

    So currently it's all working as intended, but this question has come up a few times now, so I guess we ought to tweak it to make it better. Maybe stable releases should only prompt you about a new beta once?

  • What device is it specifically? A similar type of issue has come up in the past where the device doesn't actually have an accelerometer sensor. In that case some browsers, but not others, try to emulate an accelerometer via the other sensors. So you'd just be seeing the difference between which browsers do this emulation.

  • The best way to find out is test it on a real device. Nobody can really give accurate advice by speculating.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • This is the C2 bugs forum. Please report C3 bugs here: https://github.com/Scirra/Construct-3-bugs/issues

  • You do not have permission to view this post

  • Why aren't you using the asm.js version? It should be around 3x faster.

  • The Linux NW.js export is for x86-based CPUs. The Raspberry Pi is an ARM system so needs a separate build, which doesn't exist yet unfortunately.

    Your best bet is to try to get a HTML5 export running in Chromium. Last I tried if you enabled their experimental graphics driver you could get WebGL, but it wasn't very fast and was pretty unstable. I think they're still working on it though so it may be getting better, I just haven't checked for a while.

  • Ideally there would be several translators involved so nobody has to do that much work, and it means there are more views on how the translation should be done, which if everyone comes to an agreement on best terminology and such, should help make it better quality. However if someone does an exceptional amount of work we may be willing to somewhat increase the reward, but this is done at our discretion and we cannot make any guarantees about further rewards beyond the 2000 contribution mark.