sqiddster's Forum Posts

  • Pretty much anything you can do in classic (apart from some of the advanced shaders and 3D stuff) you can do in C2 - and a LOT more.

  • I haven't checked Ashley's solution since the bug was really rare and I was working on other stuff.

  • Oh really? That's odd. I'm pretty sure setting it back to medium fixed it for me.

  • Problem Description

    This image pretty much sums it up [tested in Node-Webkit]:

    Steps to Reproduce Bug

    • Export project with high quality downscaling

    Operating System and Service Pack

    Win7 64bit

    Construct 2 Version ID

    r169

  • I talked to an Xbox rep at PAX about HTML5 support. Bascially, it's definitely going to be a thing, but expect a feature set like Internet Explorer. Also, no webGL or web audio, and it doesn't take full advantage of the console's performance.

    I disagree with newt however about indies and consoles mixing in general - it's never been easier as an indie to get on console platforms - even Game Maker is supporting Playstation export.

  • Alternatively you can use 'pick nth instance'. 0th and 1st instance can then be referenced individually.

  • It's definitely possible.

    I believe the method Nuclear Throne used is creating a couple 'walker' objects during generation that would move randomly through the level, carving out space. This meant that there would never be any inaccessible areas. There are a ton of other methods you could use too.

  • Just add another condition to the touch events?

  • Wooo! Thanks Ashley, much appreciated.

    Would this option occur on a project scale or on an individual image scale? It only happens to a few images in the game, and I feel like a dramatically increased spritesheet size for every single animation could be a big sacrifice.

  • newt hahahaha

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • hmm veeery interesting...

  • newt that's interesting - this is in an exported build with Node-Webkit, right?

    I've never heard of anyone *not* getting the lines.

  • I'm thinking some of the engine-specific things that makes it happen (i.e. number of other animations???) will make a bug report difficult.

    It seems so weird to me that removing one animation from the object will stop the issue from reproducing altogether. I can't even begin to imagine why that would be a contributing factor.

  • Ashley yeah, it's weird, isn't it. It doesn't happen at all in NW preview, but there are some other subtle rendering differences there too so I'm not sure that helps you too much.

    Is this enough to file a bug report to Chrome? I'd hate to go through all that again (Last time I waited on Chrome to fix a bug it took over six months)

  • I don't think regressing NW versions is a good permanent solution - we need to find out what's actually causing the issue and get it fixed.