Ashley's Forum Posts

  • As I noted previously, the old releases are all still there and available to use in r198 and older if you need to use the key password field.

  • OK, I think we have to add back the key password field, so it's done for the next release. More details in the resolution of the bug report: https://github.com/Scirra/Construct-3-bugs/issues/3949#issuecomment-646664916

  • The animations and animation frames belong to the object type, and object types are global to the project. It has nothing to do with how many instances exist.

    • Post link icon

    Subscriptions are widely used across the software industry. We are clear about the prices up-front and lots of customers are perfectly happy to subscribe to what I think is a perfectly fair deal and much cheaper than many other options on the market.

    This topic has been discussed a lot, and the original post accuses us of a crime for what is standard practice across the entire software industry, so closing this thread.

  • You haven't shown a screenshot, but I would hazard a guess that this blog post explains exactly what's happening and how to solve it in Construct.

  • WebSockets don't work peer-to-peer. WebRTC does, and that's what the Multiplayer plugin uses.

  • To avoid wasting loads of memory, all instances of an object type share the same set of animations and animation frames.

    Loading a URL permanently overwrites the animation frame it's loaded in to.

    If you want to keep around the original, load the URL in to a separate placeholder object.

  • The engine doesn't support that internally though, so I doubt it's a simple solution. That would probably be a pretty complicated overhaul.

  • The same signalling server is used for both C2 and C3, and it's still actively supported and will be for the foreseeable future.

    I would guess you're having unrelated connectivity issues. Try changing the room name in case someone else is in the room as host who you can't connect to.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • LaurenceBedford - it's not clear that your posts are actually related to this thread. I saw you asking questions about Cordova adaptive icons, which have an unrelated issue involving a Cordova bug. If that's the issue, it's nothing to do with this thread.

  • If you want to move to a point over a fixed time, the Tween behavior is more appropriate.

    If you want to move to a point with a maximum speed, the Move To behavior is more appropriate.

  • As noted, speech recognition is not supported in Safari.

    Since Apple ban all other browser engines on iOS, all other browsers like Chrome, Firefox and Edge are just skins over Safari. So there is no difference in support between iOS browsers. Speech recognition is just not supported on iOS right now I'm afraid. It's something Apple will need to address.

  • It's out of the question to change the default since it would be a wide-ranging breaking change.

    Further, I think this is more complicated than stated - there is currently no UI to arrange the order, and there is also the question of if an object belongs to multiple families, what is the ordering between families? There is no way to arrange that order either, and I'm not sure how that could even be managed in the editor.

    Another option is to use all the effects on the object instead of the family, if that can be workable.

  • We can't go back to exactly what it used to do. The old approach was simply broken, and people kept running in to the brokenness, and ending up making forum posts, filing issues and contacting support.

    Previous Construct releases are still available - which is specifically done for cases like this where there is some kind of unexpected issue. So if you go back to r197.2 you can carry on using it like it was before, at least in the short term while we figure out what to do about this.

    Considering a permanent change will cause permanent confusion, even years down the line, I would still prefer to use a workaround if one is feasible. That should only cause temporary disruption, and then should be a non-issue years down the line. So before taking any further action it would be useful to know: can you use keytool to rename a key password and continue publishing? Once you have the tool, it should only be one or two lines per keystore - not a lot of work at all.