R0J0hound's Recent Forum Activity

  • Here's an example:

    https://www.dropbox.com/s/eftq33ve74rul ... .capx?dl=0

    It's actually three parts. The first is to move the ball. The second is to move the ball backwards out of the walls. The third is to calculate the normal from the ball to the walls so we can calculate a bounce. It's an approximation that may or may not be good enough.

  • The teleportation is due to the method C2 resolves the collision. You can use the two ways from the custom movement behavior's push our actions.

    One is "push out nearest" which searches in a spiral like path around the object until a free spot is found. It works pretty well most of the time but in tight spaces like you have it can find a spot which isn't the nearest.

    Another is the object moves backward until it's no longer overlapping. That works well except after the bounce. The issue is the backward motion is in steps and after a bounce the backward step could be too much so instead of stepping back to the starting position it could pass it back into a solid so it effectively could tunnel out.

    The physics behavior is a simple way to have better collision resolution in that case. Or you can also do it all manually to have full control and in many cases have better results.

    I'll see if I can wip up an example. A simple idea that strikes my fancy currently would be to do the push backward idea except keep it from pushing back further than the old position.

  • For the math, give the sprite two variables:

    velocityX and velocityY

    Then make this event:

    Always:

    --- sprite: add 100*timedelta to veloctyY

    --- sprite: set x to sprite.x+sprite('velocityX')*timedelta

    --- sprite: set y to sprite.y+sprite('velocityY')*timedelta

    The 100 is the gravity which you can adjust.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • akkthedev

    You can access the pixels, but that is the extent this plugin provides. Outside of that you'd have to find other means.

  • There isn't any program that does that currently.

    Most isometric games made in C2 don't use Tiled at all, they just turn on grid snapping and position sprites in C2's editor.

  • The wait is messing it up in this case. What it's doing is pushing the function call to the end of the event sheet, and what you want is the call done in place.

    When creating a new object this defines when it can be picked:

    and

    "pick by uid" is the exception as it works for any object that was created.

    For accessing new object's immediately from a function you should pass that object's uid. Then you can pick the object by uid in the function, and reverse it to pick a sprite from the sprite2.

    For ex:

    call "hasframechanged" (sprite2.uid)

    on function "hasframechanged"

    sprite2: pick with uid function.param(0)

    sprite: pick closest to (sprite2.x, sprite2.y)

    sprite: x = sprite2.x

    sprite.y = sprite2.y

    --- sprite: set ischanged to true

    AllanR

    The newly created object is added to the object list at the next toplevel event as per the links above.

  • The simplest would be to use multiple layers in tiled and edit the capx to get more than the first layer. For example you could have one layer define the collisions.

    To get it in the layout would need one to write a program to convert a tmx file to a C2 layout file and add it to your project.

  • A simple way would be to create a bunch of bullets from the source object and set their angle to a random direction, also save that angle to a instance variable on each. Next you just move the objects and bounce them as they hit walls. Ideally you'd do it the same way as in that laser example. Now as soon as one of those objects collides with the other object, use that object's initial angle for the laser and delete everything else.

    Sending lots of lasers will use more cpu, this is true, but when it's the only solution atm there's not much you can do.

  • The simplest idea would be to send lots of lasers from one object and let them bounce until one hits the other object, then you can discard the rest.

  • They do something entirely different to what my capx does. My capx loads an isometric tmx file to sprites, and those plugins help with motion and such in isometric. I couldn't tell you more because I've never used them.

  • It just loads the tmx to a bunch of sprites. After that you can do whatever you like with them.

  • Juicy

    You could make you're own loader for isometric tiled files. You'll just need to use sprites instead of the tilemap object.

    Here's an example:

    https://dl.dropboxusercontent.com/u/542 ... d_iso.capx

    The tiles are imported into the sprite's animation as a sprite strip, and the tmx file needs to be saved with csv encoding.