R0J0hound's Recent Forum Activity

  • —

    Paster seems to work with the minifier.

    What does the browser console say? You can open it with ctrl+shift+j.

  • Do you use "pick nth instance"? I think I've seen it before, but I forgot what was causing it. I'll see if I can reproduce it.

    Edit:

    I can't seem to reproduce it. :/

  • bladedpenguin

    Here's a list of variables that C2 provides for use in the shaders. To use them you still need to declare them at the top of your fx file.

    Most third party shaders are made by copying what existing shaders do. There was a question about variable qualifiers which may also be useful:

    Thirdly as a testing ground I've seen this online tool used to make shaders quicker:

  • Nice, that looks pretty cool.

  • Valex

    Other objects can still collide with them, but you still need to disable collisions between the beams.

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

    The only other option would be to change the location where you add the joint so that the beams aren't touching.

  • How are you pairing the ships with the colliders? From what it looks like you're using an overlap check to pick the ship from the colliders. You could eliminate those collision checks by putting the colliders and ship into a container.

    Another thing you can do is check for collider overlaps once and store the result in a variable.

    every tick:

    --- controller_smallShip: set blockedL to false

    --- controller_smallShip: set blockedR to false

    --- controller_smallShip: set blockedF to false

    --- controller_smallShip: set blockedB to false

    colliderL is overlapping obstacles:

    --- controller_smallShip: set blockedL to true

    colliderR is overlapping obstacles:

    --- controller_smallShip: set blockedR to true

    colliderF is overlapping obstacles:

    --- controller_smallShip: set blockedF to true

    colliderB is overlapping obstacles:

    --- controller_smallShip: set blockedB to true

    Then for the remainder of the event sheet just check those booleans. You shouldn't need to actually check for collisions again that tick unless you change the object's postions in the event sheet. This technique is mainly useful if you you're doing the same overlap check in multiple places.

  • You can do the pattern you're specifying like so:

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

    To create near an existing point you could do something like the following:

    pick random instance of sprite

    --- create sprite at (random(-100,100)+sprite.x, random(-100,100)+sprite.y)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Valex

    You can disable the collisions between the joined objects by giving them the same non-zero collision group.

  • How are you handling the collisions? Using distance instead of is overlapping is just a different way to detect collisions, they don't affect how the collision is resolved.

  • —

    I should have looked into it earlier, it ended up being dead simple to fix.

    Updated to version 2.2c:

    * Now with minifier support.

  • It just changes the value of dt.

    At 60 fps with a timescale of 1, dt will be ~0.0166.

    If you change the timescale the the fps will stay the same but the frame time ( which is usually dt) will be multiplied by the timescale to give a new dt.

    So for example at 60fps

    If Timescale=2 then dt will be about 0.0333

    Or if timescale = 0.5 dt will be about 0.00833