Ashley's Forum Posts

  • Well, what framerate are you seeing both with and without? Have you measured cpuutilisation as well? If you have a powerful system it may be able to do fine without render cells. It helps more on weaker devices like mobile phones.

  • Everything you import is converted to 32-bit PNG. Choose a different format in the Image Format dialog in the image editor if you want something else.

  • Closing as not a bug. The 'Seams' property is set to 'Overlap'. See the manual entry. This deliberately renders a 1px overlap on the edges to ensure seamless rendering, but it has this effect when changing the opacity, so you'll need to use 'Exact' seams.

  • It doesn't work because the function ends when you 'Wait'. It executes like this:

    1. 'On function' triggers

    2. First action retrieves correct parameter

    3. Wait action is used

    4. The function ends and execution returns to the rest of the event sheet

    5. Event sheet keeps ticking for a while during the 'Wait', until the time expires

    6. The last action tries to retrieve a function parameter, but it's not in a function any more, so returns the default 0.

  • The wallclocktime system expression always advances at the normal rate regardless of any other time scaling.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Why do you need to do that? For a feature suggestion to be compelling you need to outline a really good use case and describe why it's not easily possible by any other means, in detail. Detecting if any event in a group has run seems like a pretty niche thing to do.

  • WebRTC is a standard so any platform that supports it should be interoperable with all the other platforms. Currently only Chrome and Firefox support it, but it should be picked up by other browsers over time.

  • Edited OP to add a note about Windows XP support.

  • Hi all,

    There's a few bits of news about node-webkit:

    • Node-webkit has been renamed to NW.js since the "node" and "webkit" technologies aren't relevant any more. The project also has a new website at nwjs.io. (I've read a suggestion maybe "NW" can be a backronym for "Native Web" )
    • NW.js is now based on IO.js, a compatible fork of node.js. So hopefully this won't break anything.
    • An alpha update has been released for NW.js v0.12.0. This is based on Chromium 41 and therefore should fix the infamous jank bug in node-webkit 0.11.x (which is based on the buggy Chromium 38).

    Since v0.12.0 is described as an alpha, the official version at scirra.com/node-webkit hasn't changed, and I'm just posting this version here as an experimental option for testing. Hopefully everything works smoothly, but let me know if anything is broken. It worked for me with a simple "does Space Blaster work" test.

    I've also read NW.js has dropped support for Windows XP, since the underlying IO.js has. This is regrettable, but probably inevitable. Although Windows XP is still hanging around with ~12% market share (according to StatCounter), it's ~13 years old, a lot of software is already incompatible, it's less secure, and it's going to die out eventually. Windows XP users probably correlate with older hardware with broken graphics drivers that either crash or fall back to software rendering anyway, so they may not have had a great experience with HTML5 games anyway. I do realise this impacts the reach of games published this way, but this is probably the beginning of a trend of decreasing XP support from browsers in future so was only a matter of time.

    Note the name of the d3dcompiler DLL has changed for Windows versions. The next version of C2 (r195) will copy the right version, but at the moment r194.2 will only copy d3dcompiler_46.dll. I'm not sure what the impact of this is, but maybe copy d3dcompiler_47.dll over to the exported folder afterwards to make sure that doesn't cause a problem.

    Download:

    nwjs-for-c2-v0-12-0alpha.exe

    Since we're due a stable release I don't want to make any unnecessary changes, so r195 will probably go out still referring to "node-webkit", and through the next beta cycle we'll go through all the node-webkit references and update them to say NW.js instead.

  • You do not have permission to view this post

  • Can't reproduce - on Windows 8.1 64-bit I can suspend the PC with the image editor open, then wake the PC and everything's still there and working fine. You should also test r194.2 in case it's related to a problem we already fixed.

    Try pressing 'Reset dialogs' in Preferences, and if you can still reproduce then please indicate the steps.

  • Closing, please follow the bug report guidelines (such as attach a .capx).

    • Post link icon

    Closing, Ludei have their own forums - you can ask them questions directed specifically at them there instead of using our forums.

  • If you last tested your large layout before collision cells were added, it would definitely be worth trying again. They can make a very big difference to the performance of large layouts with lots of collision detection going on.

  • You do not have permission to view this post