Ashley's Forum Posts

  • You need to ask Sony about this. So far there's no way to publish HTML5 games to any Sony platform. We'd 100% support it if Sony made it possible for us.

  • 1. Yes, it should be fine. If you look at the differences between the templates, they just have some different initial objects placed and some altered project settings.

    2. Audio should never have been a problem on Safari. It's long supported the Web Audio API for high-performance low-latency polyphonic audio playback. So I don't know where you got the impression it can't play more than one sound at a time.

  • gameop - please make sure all that information is in a bug report in the bugs forum otherwise I might lose it.

  • You can't send a single bit over the network - the smallest is a byte, which allows you to send 8 booleans at once. This is already documented in Multiplayer tutorial 4.

  • Did you look at the profiler?

  • The next version of node-webkit supports disabling the GPU blacklist in node-webkit in all Windows versions. Previously you needed a workaround (create a shortcut and add the command line parameter to that).

  • gizmodude4 - where did you get this plugin exactly? If it uses the same ID as the official textbox plugin I want to make sure it's de-listed from the forum, since that's a terrible idea and is just going to cause horrible compatibility problems for whoever uses it. The plugin author *must* use a different plugin ID.

  • Please follow the bug report guidelines or there is nothing we can do: attach a .capx made from scratch which demonstrates the problem, and obviously don't use any artwork you don't want to share, the areas of red make it pretty confusing to see what the real problem is.

  • Closing as already fixed.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Closing, a .capx is required or we won't investigate issues. Please submit a new report with a .capx demonstrating the problem as per the guidelines.

  • Closing, please follow the bug report guidelines (include a .capx, etc) or we won't investigate.

  • Closing, we cannot support third party plugins. This error is caused by the "advanced textbox plugin".

  • Closing as not a bug. Set the text object to smuggler*dt and you'll notice it's about 0.4. Since you round the result you get 0. dt is working correctly, you are just rounding it to zero.

  • It's a very difficult problem and I'm not sure it would in practice work any better than SVN. Consider two people editing the same project in real-time who do the following:

    1) User A adds "Player" sprite

    2) User B adds an event referencing the new "Player" sprite

    3) User A presses undo

    You have three options to handle this:

    • undo adding the "Player" sprite, and the event User B added disappears. User B may be left thinking "WTF?" since their work has suddenly vanished. Think of all the weird bugs that could happen with random bits of a project appearing and disappearing like this.
    • undo the previous action only, so User A undoes the previous action by User B. This sucks because User A has no idea when they press undo what will actually be undone, since User B could do something just as User A is hovering over the undo button, and therefore change what is undone just before they undo it. Then user B also sees something they just did vanish unexplainably, which neither user intended.
    • don't allow undo. This will make it far less convenient to use the editor since it's an essential feature.

    I think it would be terribly confusing and awkward to use no matter what solution we pick to that type of problem, and it's really the tip of the iceberg, there are all sorts of complex things you can do to conflict with each other. Source control may be tricky to merge and such at times, but by restricting each user to a particular non-conflicting section of the project, it should be fine.

  • Ideally your game would still run OK using canvas2d rendering, and turn off any effects or provide alternatives/fallbacks so it still looks correct. Then you don't need to tell the user anything.