Ashley's Forum Posts

  • Lol guys, fool'd

  • Thanks Exomarc, confirms my suspicion it's my fault

  • I think it's more likely a bug in Construct until I properly research the bug, in which case it would be coincidence Game Maker has this bug.

    If it is a problem with nVidia cards, I can't and won't do anything about the bug. In that situation it would be nVidia's problem so if the latest drivers still had the problem, you'd have to go complain to them about it. Right now though, can't say which it is. We'll see.

  • Well, it's much more efficient to send commands to the GPU all in one go (in a batch) than separately. I hadn't realised effect rendering wasn't batched, so was just a matter of fixing that.

  • The wiki does need a description of containers, I'd be happy to help out. Note two other features of containers:

    • If you create or spawn one of the objects in a container, it creates instances for every object in the container, to keep the object counts the same.
    • Same with destroying - destroying an object in a container destroys all associated objects (so you only need one Destroy action on any one object to destroy a container).

  • Event Wizard = dialog you use to insert actions and conditions.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Yep, received thanks, will take a look soon.

  • Some of you may have noticed somewhat sluggish results when alot of different textures are created, or objects with many effects.

    I am happy to announce (and this is not an April Fools joke ) that by the tests done, I measure an increase of up to 1000%. Pixel Shader 0.0 operations (such as additive) have also been increased by around 200% in speed, and I hope to optimize other PS effects.

    When 0.94 is released, it'd be good to collate some testing information of the general increase .

  • Dear community,

    I mentioned that 0.94 would be released several days ago, at around this time. I will not renege on this, and 0.94 should be released later today. However, we have been in discussions with a large software company (Adobe) and I am pleased to announce we have agreed terms and Construct has been purchased outright for a 6 figure sum.

    Adobe wish to take Construct into the online and Flash market, as a simpler development environment and with the aim of developing a stronger applications and professional market. I will not be on the development team unfortunately, but I hope my mentoring of Construct and the community is enough to see all our aims through.

    I wish you all the best,

    Ashley

  • This is fixed in 0.94; for reference, it occurred when retrospectively changing actions or conditions to different objects without replacing them (clicking back in the Event Wizard).

  • Looking good

  • Hmm... can you make a .cap showing the problem and send it off to ? Cheers.

  • Thanks for taking the time to leave a message, DavidN. I'll lock this thread now, I don't think further discussion of the matter is going to help anything. I would recommend forum users here also recognise that the matter should be left now, for everyone's benefit.

  • Well the SDK can create objects - so I think we could just add a 'Spawn blob' action to Physics. It would make the instance that had the action called the central node, and spawn other node objects automatically hinging them together, with customisable number, radius etc.

    I don't know when this can be done, but I think its the best idea!

  • Thanks MikeD, but if I remember right you also mentioned it was "much worse" or some such strong opinion (I've said before, theirs is more polished, titlescreen etc, so is probably better, so long as you have the hardware to run it). It looked intended to provoke a reaction, which it did, because it caused the admins enough of a headache to remove a whole thread, which is pretty bad news. I'm glad you understand though.