Ashley's Forum Posts

  • It's possible with WebSockets, but you'd need to write your own server, and it might not be suitable for real-time "twitch" gaming since WebSockets can only use TCP transmission, not UDP.

  • No, they do not support WebGL.

  • The WebStorage manual entry notes:

    ote WebStorage only stores strings. If you set a key to a number like 100, when you retrieve it back it will be a string. To convert it back, use the system expression int, e.g. int(WebStorage.LocalValue("score")).

    So you're probably getting the value back from WebStorage as a string "2" rather than the number 2. Make sure you convert it back to a number when reading from WebStorage if it's supposed to be a number.

  • You do not have permission to view this post

  • It may be possible with the next generation of browsers (XBox One, PS4), but we can't make any guarantees until the devices launch and we see the developer options available.

  • It looks like it's only supported in the native SDK. Doesn't look like web apps can use it yet.

  • I think it keeps the window hidden until the progress bar that you would see in a browser completes. I'll make it show the window sooner so the user can see the progress bar rather than wondering why nothing's appeared. I think you can already use a loader layout to show the window sooner as well.

  • Arima - Chrome have announced the intention to support asm.js, but in the mean time they've made the ordinary V8 engine better at handling it, so it's still quite fast.

  • You do not have permission to view this post

  • Can't reproduce. Are your graphics card drivers up to date?

  • I've investigated further. I can reproduce on both Windows 7 and Windows 8 reliably, but only in release builds. When in a debug build, it does not occur. This is one of the most difficult classes of bug that can occur in software development. I have almost no leads from which to investigate. It's possible to debug release builds, but there is hardly any useful information (the debugger simply reports there may have been heap corruption, which is also another very difficult class of bug).

    Obviously this needs fixing and it may also be the source of other random crashes or instability in Construct 2, so I will keep working on it, but I don't know how long this could be around for. In the mean time I recommend trying to find workarounds (perhaps avoiding showing the grid?). I have also tried to add more useful information to the error messages for the next build, so let me know if any error messages change from r145+. On top of that any extra information such as which build the problem first started occurring in could be useful.

  • Did you test in r144.2? We fixed some related issues recently already. I've made some further changes for the next build anyway (added CloseCode and CloseReason expressions; made sure the error message is read properly).

    Note: please don't adjust official plugins. It's better to suggest the code changes then allow us to make them through official builds. Anyone using that plugin you provided will now have compatibility difficulties with the official plugin that will come in the next build.

  • Can't reproduce, works for me every time (and as far as I know, most other users, since we don't have any other reports of this). Are you sure you have the right version of Java installed? You need the 64-bit Java for minified export to work in 64-bit Windows.

  • Closing - I'm afraid we cannot do anything about projects that are already corrupt. We need the steps that caused the project to become corrupt in the first place to be able to do anything about it.

  • Can't reproduce in my dev copy of r145. Closing - let me know if you still have any issues with r145 when it's out.