Ashley's Forum Posts

  • Works OK in Firefox here. Note you have to move the mouse off the button to see the correct style; I suppose the button uses its own cursor style (which seems sensible).

  • Closing, please see the bug report guidelines. You need to provide a minimal .capx to prove there is a problem in Construct 2, otherwise with this many events it's most likely you just made a mistake in your events.

  • OK, will follow this up on the GitHub issue.

  • Watching videos isn't going to help anything. What you can do instead is record a profile while something slow is happening. Open Chrome dev tools, go to the Performance tab, and hit Record. Then do something that is slow while it's recording. Then stop recording, right click in the main view and select 'Save profile'. Upload the resulting file somewhere, and then there is detailed performance data I can look at, which should give a lot of insight to what is actually making it slow.

  • Jailbreak won't help. Since Apple ban other browser engines, nobody bothers developing them. So there is no "real" Chrome for iOS to install on a jailbroken device.

  • If you think Construct 2 can't handle graphically intensive games, then as ever, rendering is bottlenecked on the GPU. So if you switch tool because of that, the hardware isn't going to be any faster, and the performance won't be any better.

    I think some people switching tools have hardware-bottlenecked games and are eventually going to realise it was never C2's fault. I do see a lot of games bottlenecked on the GPU, and everyone knee-jerk blames C2, HTML5, Chrome, or anyone or anything else. I don't know why it's so hard for people to believe they've fully utilised the hardware? The engine is designed to let you do just that. I'm happy to be proven wrong, please send me your projects and all that, but it usually only confirms the point. I imagine some people will wander from tool to tool always thinking everyone's engine is awfully slow, never recognising that hardware is a limited resource.

    Just to pre-empt how this discussion usually goes: now someone's going to shift the goalposts and talk about some random bug or some quirk that we fixed, or some other problem they had at some point, or start listing their personal laundry list of things they want changed. That has nothing to do with GPU performance. On this specific point, C2 is as good as a native engine, and I stand by that.

  • I think you need to make sure you're clear on the difference between Java and JavaScript. They're two different languages. JavaScript is the one Construct 2/3 use.

  • Why not provide ... a modified true chrome version for manual installation instead of going through apples system?

    This is something Apple specifically ban. Safari is the only browser engine allowed on iOS.

  • I've no idea how it could take so long - on my system the 400mb project previews in about 25 seconds (most of which is building the spritesheets). It saves the results too so the next preview after that only takes ~2 seconds.

    Note Construct 2 never assembled spritesheets in the editor - it only did that on export, so C3 has more work to do on the first preview. However since the results are saved subsequent previews should be faster.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Sorry for taking so long to get round to this, the launch of C3 has been manic.

    The original .capx is not a very good case - it relies on Platform + Solid on the same object, which has never been a directly supported case in the engine. The engine treats objects as either a moving object or an obstacle; you shouldn't use both. (I might actually block this case in C3 since it's not supported and people keep doing it.) I'd appreciate a different example .capx that shows a similar problem without using this not-really-supported case.

    If we investigate the .capx anyway, the problem comes down to the order of ticking behaviors. Platform has special code to say "if on a moving platform, move with it". Since the .capx uses the unusual case of a platform and a solid, and then another platform on top, it creates a 2-link chain, and the order of updates becomes important. If the bottom object ticks first, it moves to follow the platform, then the top object ticks and follows the bottom object, and everything worked OK. However if the top object ticks first, the bottom object has not moved so it stays where it is. Then the bottom object ticks and moves away to follow the platform, causing a gap to form between the two, which is the problem here.

    There is no obvious way to fix this problem, because we have to tick the behaviors in some order. Any changes we make would just move the problem somewhere else. If we sort by the object name and tick in that order, then renaming objects can change the tick order. If we tick in the order objects were created in the editor, then deleting and recreating an object can change the tick order. There's no gold standard tick order that is the "correct" one. I am also against letting the user customise the tick order; micro-managing such obscure parts of the engine is the exact opposite of the design principles that has made Construct successful.

    I'm also not convinced this is actually a serious problem - C2 has been out ~6 years and we've only just had a report involving an obscure case of using platform and solid at the same time (which is why I'd be interested to see a more convincing example). For the most part, the order behaviors tick in shouldn't matter.

    Even if this does affect a number of projects, it's not clear what to do about it. We have to choose some order to tick behaviors, and that order can probably be changed by something the user does.

  • Closing.

  • Closing as not a bug. Internally C2 stores angles as radians, so it converts degrees to radians. However, CPUs are not perfectly accurate at math. See "Expecting math calculations to be exact" in this blog. It's normal to get results that are close to, but not exactly, the answer you want, hence the need to accept a small range.

  • You need to host on a secure server (HTTPS) for offline support to work, which is provided by a Service Worker (hence the error message). The game should however continue to work. Closing as not a bug.

  • Closing, the URL is not valid and the version of C2 is well out of date.

  • Closing, please see the bug report guidelines.