newt's Forum Posts

  • Z elevation relates to the camera position, where zoom goes to where your x/y position is on the layer.

    Basically Z height is a 3d representation saying that if this object is on this side of the camera offset the object a certain amount, and then offset some other amount if its on another side.

    And then if its right in front of the camera don't offset it.

    All of that based on a percentage .

    Edit:

    No idea whats up with the shadow caster.

  • That doesn't qualify it as a commercial license though.

    Generally speaking companies will need to use multiple copies for multiple employees.

    Your just assigning an arbitrary value to compensate for that.... right?

    Yeah, might wanna rethink that part.

    As it stands your just saying if they make more money, you want more as well.

    Probably not legally binding anyway, even if the amount is negligible... either way.

  • Any thoughts on using an open source compiler so we don't have to worry about license issues with MS?

  • Well its not very linear, but editing everything from one screen does seem appealing.

  • Why not split the behaviors up some? Like instead of a single platform behavior have the movements as separate behaviors like platform move left / right, or platform jump, platform double jump, platform super jump, etc.

    That way you could build up a nice selection, and mix and match. That is if you can get the behaviors to "play nice with each other", unlike physics, etc.

    Should be much easier to debug as well.

    Who's up for a interpolated movement?

  • That's interesting, but they would have to come up with a different license for the open sourced part. Gpl restricts selling anything other than the method of conveyance.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Might also be used as some sort of random seed.

  • Might try adding another function.

  • Might be useful for some sort of captcha, or perhaps a hash check.

  • Probably because the plugins not really as useful now since we had an update that changed how events work.

  • Lerpin angles is a bit complicated, might do an example of that.

    lerp(sprite.angle, new angle,x*timedelta)= boo hoo when new angle is greater than 360, or is less than 0.

    Also a two node path using lerp versus qarp would be a good example.

  • That's fine unless you plan on making the ship that has 2 the same object that can have 4.

    The two extras would be created regardless.

    There's also the object pairer...

  • Might loose some beta testing feedback from the free users... ok all.

  • Probably better to go with a family. Containers always have the objects contained affected, and or picked.

    You could continue to add objects to the container, and use a pv to set opacity, but that seems like a waste.

  • Yeah it would be nice if that worked, but the array cant be modified at runtime.