alastair's Forum Posts

  • I went pretty small actually with the resolution in this, 540 x 960.

  • So is the conclusion that this latest node-webkit isn't worth using?

    Performance seems to have taken a small hit, in both Chrome and Node-Webkit, but the biggest issue is I don't think WebGL is working anymore. When I run my project in Chrome or Node-Webkit my effects do not work anymore. I have some brightness settings on some background objects, and they don't work now.

    I just updated my nVidia drivers to latest, and my chrome is latest too (v33).

    Has anyone else been seeing anything like this?

    Nardonicus, Which nVidia card are you using?

  • The primary benefit of other software is that you're not at the whims of 3rd party software for exporting support, Construct 2 is absolutely fantastic for making games but yeah the exporting options aren't great and it has a tiny dev team size.

  • Would be cool to be able to use things that every other steam game can do!

  • Huh? Where did you reference that?

    Earlier this month they started allowing for them in the developer version of chrome (canary)

    https://codereview.chromium.org/135523006/

  • Yeah I had a user on steam that has a Radeon 7770 as well, and he's saying my game runs poorly with that card, despite it being a more powerful card than my computers!

  • Thanks, yeah you should be able to get it from your download page.

  • ArcadEd, Hmm? Weird that it gets faster for you but worse for others.

  • Change the 600 in your random to ViewportBottom(a layer number).

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • andreyin, I'm having the same issue, can't open my game on 13.10

  • There probably isn't much reason why it should work, as far as I'm aware only Xinput controllers are meant to work with it?

    However, Chrome 35 (or 34?) will have support for pretty much every controller (all my awesome obscure ones work so far, in Canary). So hopefully that will come hastily to the node-webkit some day!

  • Haven't seen a topic/page with data for this yet. There's this:

    https://www.scirra.com/manual/6/system-requirements

    But it refers to the editor and not games created with it.

    Node-webkit minimum requirements? Is it Windows XP SP3? It doesn't need DirectX does it? How much memory does it use (not including the game)?

  • I think I figured out the issue, it's to do with particle box size! When you apply an effect to the particle object, if you don't make the particles box size large enough then anything outside that box will be invisible/cut-off!

    <img src="http://i.imgur.com/4iafrtz.png" border="0">

    So the solution in my case is to make the box larger, but the question is, is this change intended or a bug?

    I have a .capx with the "ripple effect" instead of the one I was using because it doesn't not come with the progam but gives the same result anyway.

    .capx download

  • Here's an image of the difference with my game:

    <img src="http://i.imgur.com/f9UMiSZ.png" border="0" />

    Basically it seems like the particles with effects are getting cropped (and the larger it is the more is cropped)? I'm using a particle objects.

    Aurel is this similar to your bug, I couldnt understand your cap/post either.

  • The bug is affecting other WebGL effects too (alphathreshold is hardly working in this build).