R0J0hound's Recent Forum Activity

  • Just to clarify a few things:

    The distance an object moves per frame is speed*dt, so with a speed of 5000 the object will move 5000/60 or about 83 pixels per frame, which is why it can pass other objects without colliding.

    For doing an instant hit, the common approach is called "ray casting", but you can also find examples on the forum about lasers that do it too. By using a sprite and changing the width you can do the same thing as the line segment idea.

    That error is a bug I'd say, and a good candidate for an error report.

    Your last issue is probably something simple, but we'd need to see a capx to find it. The posted events don't seem to cause it.

  • It is possible, I didn't say it wasn't.

    Put two objects in a container, Sprite and SpriteMode7. Position the Sprite objects in the layout editor to define the object positions. Then in the event sheet use the behavior or whatnot to set the SpriteMode7 object's position from the Sprite's position. You then move around the Sprite objects and the SpriteMode7 object will update accordingly.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Cool

  • It's the same with particles and tilemaps too as I recall. It could be nice to be able to disable the visibility culling, but it's done per plugin and probably will run into performance issues with some users.

    The workaround is to move the object onscreen before pasting it, which I suppose could also be done by the paster plugin...

  • it's not that it's not stable, it's just that 1/10 is the highest c2 lets dt get. So basically the game goes into slow mo if the dos drops below 10.

  • It should work as you expect if "on button" and "on button released" refer to the same button. I can't tell without seeing the actual events though.

  • Zebbi

    It's just how you look at it. To me those variables define the top view position and the actual position is irrelevant since the behavior will set that.

  • Maybe make the paster be at an integer position like int(scrollx).int(scrolly)

  • Search the forum for gesture recognition. There are a few examples and even a plugin.

  • You probably should be able to use the xml plugin to do this. Take a look at it, it has methods to loop over tags and such.

  • every tick

    --- set x to self.x+speed*cos(angleOfMotion)*dt

    --- set y to self.y+speed*sin(angleOfMotion)*dt

  • Oh, ok. do this instead: give the layer a paralax of 100x100, and make the hotspot of the paster be the center, then right before pasting the objects to it set it's position to scollx,scrolly.