Ashley's Forum Posts

  • Those conditions only worked with AppCache and so would not work with the browsers which use Service Worker, i.e. Chrome and Firefox (so a lot of the market).

    I want to add support back for checking for those conditions with the new Service Worker system, but it's tricky and it's hard to guarantee they'll work identically to how they did before, so they're deprecated for the time being. I think it is most likely new triggers will be added in future.

  • It doesn't sound like they have any immediate plans to drop support, but I asked Paul to clarify.

    Even if the XDK completely shut down, there's always PhoneGap Build and other build services. It is not and has never been the only build system you can use.

  • The spritefont object is designed to represent a single font, and this basically comes down to two things: representing multiple fonts in the same object, and then effectively a rich-text engine to be able to display multiple font styles within the same text run.

    Both are pretty complicated features to add, and I'm a bit sceptical of the design. For example I think it would be better to leave a spritefont as representing just one font, but then have a way to merge different spritefont objects in the same run of text. But then you still need some kind of markup and parser to specify where you want which font styles...

  • I think if the cone is 0 to 360 then it just extends the crossfade area to the full circle.

    I'm not sure exactly what would be drawn to represent sounds - in your example, at what radius do you draw the circles? The sounds gradually reduce to the minimum volume over what's often a very long range, and even then they continue at the minimum volume, so it seems kind of arbitrary to pick any particular range to draw a circle at.

  • The biggest problem with Android performance is GPU blacklisting - the drivers are buggy or unstable and so the browsers revert to software rendering, which can really tank performance. The best way to check for that is open Chrome and visit chrome://gpu and see what the status at the top is. WebGL should say it's hardware accelerated in green. If WebGL and canvas2d both say software rendered, you probably can't get good performance on that device. (Most modern devices are fine though, this is typically only older phones)

    If both are hardware accelerated, then you simply must make measurements otherwise you are shooting in the dark. If the CPU usage is high, try running C2's profiler in debug mode and it will tell you roughly where your CPU usage is going. If the CPU usage is low but it's still slow, the graphics are too intense.

  • You do not have permission to view this post

  • Closing, please provide a .capx and test the latest version as stated in the bug report requirements

  • Does this help? I guess I should put something like this in the manual.

  • I think this is a problem with the screen recording software if it can't record certain kinds of app. I'd report it to them. Can Chrome be recorded? If not then it's probably the same thing, so you can request support for recording games in Chrome.

    FWIW there is a fairly recent ability to record the canvas and produce a WebM video download from it from within the browser, but that doesn't cover all cases like streaming.

  • Yeah, really the main thing is that you can tile and mipmap non-power-of-two textures. This means tiled backgrounds should have better quality when they're not a power-of-two size. Basically it means you can ignore power-of-two sizes since they don't matter at all any more.

    There are a few other internal tweaks that can be made to help speed up texture creation and such, but they probably won't make much of a noticeable difference. It's quite a lot of effort to refactor our code to use that as well, so we probably won't do that until a future revision of the runtime.

  • criterian21 - I'm not sure what you mean is different? Previously it would also show the old version, and you'd need to reload again to get the new version. Also due to a quirk of Chrome you may have to actually close and reopen the entire browser window.

  • Closing as sounds like this NW.js issue.

  • I looked in to the "WebTechnology" company and it looks like they are a Japanese company that just does image recompression - nothing much to do with actual web technology as far as I'm concerned, so I wouldn't count on that being a sign of anything...

  • Closing as driver bug.

  • Closing, see the guidelines.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads