alastair's Forum Posts

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 24 Feb, 2014
  • Quote

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

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 24 Feb, 2014
  • Quote

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

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 22 Feb, 2014
  • Quote

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

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 22 Feb, 2014
  • Quote

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

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 21 Feb, 2014
  • Quote

  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!

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 18 Feb, 2014
  • Quote

  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)?

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 14 Feb, 2014
  • Quote

  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

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 14 Feb, 2014
  • Quote

  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.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 14 Feb, 2014
  • Quote

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

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 13 Feb, 2014
  • Quote

  I'm not using that shader specifically (mine is alphathreshold) and I notice that it's getting cutoff (usually in half), but I didn't check if this was bugged in the earlier versions.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 12 Feb, 2014
  • Quote

  Don't think there's any good export for it atm.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 10 Feb, 2014
  • Quote

  bump

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 6 Feb, 2014
  • Quote

  Yes, I did exactly as you said and the error is identical.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 6 Feb, 2014
  • Quote

  blackhornet, there must be something else as I did exactly as you said but I still get the error when I run the layout.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 6 Feb, 2014
  • Quote

  In Chrome Canary (newest Chrome version) I can use my generic (non Xbox) controllers, so it should work with almost any controller. Can't wait for it to come into Node-webkit!

  Chrome Canary, if you want to test