Ashley's Forum Posts

  • Closing as discussed by email: this is just random variations in dt.

  • Should be fixed in the next build, but only in the asm.js version. We hope to be phasing out the other physics engine soon after.

  • Heh. The installer itself says on the first page "This installation is portable. You can install to a portable drive and run Construct 2 on different computers." But nobody ever reads anything

  • I don't like it. It's just a more limited UI for defining logic which is normally determined by events. Whether you have a movement, oscillation or just a clamp, often you don't want it to apply all the time. So you need to be able to turn it on and off or adjust the parameters in events based on other custom logic in the game. So you will have a bunch of events to modify all this stuff anyway. Now you have fragmented your logic between this UI system and the event sheet. If you went as far as to extend the flowchart system to do everything events have, I see it as an inferior system, since you have your logic spaghetti-fied in to 2D (whereas events are a 1D list, just going down the event sheet), which makes it very difficult to determine the sequence of things, which is an essential part of the game logic.

    The current way allows you to apply, enable/disable and modify behaviors from the event sheet, where it is more or less all done already, with full flexibility to customise the logic and parameters, and it's all kept in the same place (no fragmentation).

  • Are you using asm.js physics?

    Share a .capx so we can take a look.

  • You do not have permission to view this post

  • Sorry, it's by design that the disable collisions feature applies to the whole object type, not specific instances. So this is not a bug.

  • I am supposed to use Cordova when exporting for both iOS and Android?

    Short answer: yes. See the blog post for more info.

    • Post link icon

    Closing as duplicate of https://www.scirra.com/forum/viewtopic.php?f=146&t=123756

  • > has no rendering overhead or use of the DOM.

    >

    Thank you for your input, but with all due respect this is false.

    Why? It will spend no CPU time in draw calls, and the only DOM usage will be an unchanging canvas element. Maybe there will be a bit of memory overhead, but most machines have gigabytes of memory these days.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • If you run the C2 engine in a browser tab, and set all layers to invisible, and you don't use any form controls, you already have an authoritative server that has no rendering overhead or use of the DOM.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • If your main use case is to run in node, then there would need to be a huge set of new features to access all of node's features from the event system (such as hosting servers, opening sockets, accessing databases etc). Without that you pretty much just have an interactive game with no interactivity, which isn't very useful. So this sounds like a pretty huge feature request - almost another product by the sound of it.

  • You do not have permission to view this post