R0J0hound's Recent Forum Activity

  • Well it should be as simple as:

    Every tick

    — sprite: rotate 100*dt degrees towards (320,240)

    Where 100*dt means 100 degrees per second.

  • Just replace the random() stuff to whatever you like. Random can be defined as random(min, max) of that helps. All a box is a low and high value vertically and horizontally.

  • You do not have permission to view this post

  • There’s a “rotate toward position” action that lets you smoothly rotate to face a location.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • For something simple like variable that only increases or decreases you can utilize the trigger once condition.

    Variable timer = 10

    Every tick

    — subtract 123*dt from timer

    Timer <= 7.5

    Trigger once

    — set text to “three quarters left”

    Timer <= 1/3

    Trigger once

    — set text to “a third left”

    Timer <= 0

    Trigger once

    — set text to “done”

    Something that counts up would be >= instead.

    Another option could be to still change the variable by whole numbers but use a dt multiplied one to control it.

    Variable timer =0

    Variable countdown = 10

    Every tick

    — add 100*dt to timer

    Repeat int(timer) times

    — subtract 1 from timer

    — subtract 1 from countdown

    — if countdown=5

    — — set text to “halfway”

    — if countdown = 2

    — — set text to “a fifth left”

    — if countdown = 0

    — — set text to “done”

    Anyways those are two ideas that come to mind.

  • One way is to just spawn the objects in random positions and if the object collides with the player move it to a random position.

    Here’s one possible example. Create it on the player, and repeatedly move it to a random position till it’s not touching the player.

    On function “add spear”

    — Create spear at (playerbox.x, playerbox.y)

    — while

    — spear: overlaps playerbox

    — — spear: set position to (random(windowWidth), random(windowheight))

  • One way to do it would be with a second array. So if A is the first one B could be the second. And you’d do this:

    On function “journal”

    — B: set size to (0,2,1)

    — A: for each xy

    — — B: push A.at(A.curX, A.curY, 1) to front

    — — B: set at (0,1) to A.at(A.curX, A.curY, 0)

    — B: sort

    Then B would have the sorted list in the 2nd column.

  • Possibly. The only physics part I touch is enabling and disabling it for a frame.

    Actually, the issue probably has to do when the polygons have an odd number of points. Distort meshes only have an even number of point with the way I’m using it, so it just sets two points to the same spot. Which is probably breaking the physics library’s collision response sometimes.

    Edit:

    That doesn’t seem to have fixed it. It seems to work fine without the physics behavior. Probably need to debug the polygons. Likely some numeric errors that are cropping up.

    This is assuming that the physics behavior, how the collision shape it generated, and how the collision polygon is distorted are working without bugs.

    Edit2:

    Found it can crash too. Seems to be in the physics behavior. Anyways, best I can do is add code to make sure the polygons are convex and ordered clockwise. Maybe on another date. If it still fails then the issue is out of my control. Guess there’s always event based physics if I can fit it in and get the inspiration.

    Edit3:

    Can't fix. My code is generating convex polygons. The mesh distort feature also seems to be giving the correct collision shape. The physics behavior seems to bug out sometimes?

  • So c3 has a feature that can let you distort sprites with a a grid mesh. The cool thing about it is it not only visually distorts the sprites but it affects their collision shapes too, which in turn is transferred to the physics behavior.

    Anyways, I finally got a chance to test it and confirm it lets you do that. Next I was able to use that as a tool to slice up physics object. The basic idea is each sprite is paired with an array making up the points of the polygon. From that with some math I was able to divide two polygons into two utilizing a line. The final step was to take that array of polygon points and setup the distort.

    Here's the example of it working. drag a line to cut the sprite.

    uc4218dc537c3ccf66c134e1e9a5.dl.dropboxusercontent.com/cd/0/get/CiCZzEOX1Zth9UrAToprVbMEakvUlk79QhD71AFZ4hZspLEEggOiKwu2v6AlDgch6tdbeUOGi16kAck2fLavt2xIe_zNreoXLSmk4mP4XcmwxOEkNPMb2qhZIbEtJrkPza63USXZ7mGOaMiYUBh_XCjP/file

    One quirk with the physics behavior that I had to work around was when creating objects you need to disable them for a frame before enabling them again or they will jump. It's been there for ages.

    This only scratches the surface, and was mainly just to show how to slice objects up. I could be adapted to do dynamic breaking by running it in a loop where you'd set the line to be random angles from the collision point.

  • So the overall logic would be when a collision occurs see how hard of a collision it was and if it was hard enough break the object up.

    Seeing how hard the collision was should be a matter of looking at the difference of kinetic energy (KE=0.5*mass*velocity^2) of the object before and after the collision. You can do that by saving the KE to a variable at the end of a tick to reference later.

    Breaking the object up is either done with pre-made pieces or by somehow breaking it up dynamically.

    The pre-made pieces way is the more doable approach. There are two ways to do it though.

    1. Destroy the main object and create all the pieces.

    2. Just have all the pieces joined together with joints which are later unjoined.

    There are pros and cons of either. With 1 you’ll need to be able to place the pieces in the right position and angle, as well as set their linear and angular velocity from the original object.

    With 2 setting up the joints between the pieces can be tedious, and you’ll need a way to look at all the pieces as a group with events. Also joints tend to be springy, and you may need multiple joints between pieces to keep them from rotating.

    Now the fanciest approach would be to dynamically break the objects up as needed. For that we need to be able to change the collision polygon and what is drawn. For c2 you’re out of luck there with vanilla features, but in c3 you can in theory do it with the distort mesh feature. However it wasn’t meant for that sort of thing so some creative use will be needed.

    Anyways, using mesh distort as a tool we will want a way to slice a convex polygon into two separate convex polygons. With multiple cuts we should be able to break the objects up. There are many ways we can take the idea from there such as making the breaks originate from the contact points and use voroni cells to change up how it breaks.

    Anyways that’s a general overview. There are probably lots simplifications that can be done to make it more feasible.

  • You don't need javascript, here's a way to do it with events. It uses the tiledbackground object to draw it, and uses some math to do the raycast calculation.

    ucd2fd9ec799f82873ad055982af.dl.dropboxusercontent.com/cd/0/get/Ch7AsUeNQKD_l_4KySBlJKuXJ7ZQ6RbQFphxb_rsSQNpiIW5w9JQecIAy0q3laeIgWdRL1qBfeD4iLOdaHbInFrBd1JcZgAwVV6pnFtzIepK1Ij-hSxZNd1XU3BqC4RPu3QY5IYpr21yU1exVsRgPqC6/file

    Kudos to construct for giving access to collision points. I didn't use the line of sight raycast feature since that doesn't provide the necessary data to do the texturing.

    Also since events are so slow I tried utilizing javascript instead:

    ucbe9c11b450497d5e72ba9c1b8d.dl.dropboxusercontent.com/cd/0/get/Ch6tZsoqIFHut07HyR7dnkVcELoPBC-3R_MmPR9liXyG8LUEbylRFBPxZ4YJI2HWap31un9Q2nvsduljpmUsj0YEk9RTijHtyiKig2rCdCXUkojlHV0tMJiL51a1MQ5lfCpWo8CM8Cfc-f8n-XSpxVjG/file

    It's much faster, even though it does the same thing. But man was that unpleasant to get working. Once i got past the syntax errors, i had to deal with all the silent errors that made it not work. Anyways, it's a shame js is needed to make things faster.

  • Well there’s two different approaches to do that kind of 3D with textured walls with vanilla features.

    One is the raycast method. That’s what that link and template do. Logic wise it’s a raycast per vertical line and depending on the distance each ray is to a wall you set the visual height of that slice. You can use the tiledbackground object to draw slices of a texture to do that.

    Floors and ceiling would need to done via an effect.

    The other method is to use distort meshes with a sprite. Rufus’ example does this. Basically you need a sprite per face and you set the xyz of the corners to make a cube. Then you can use some math to rotate and move the points from a camera point of view.

    Construct makes this a bit more complicated though. You can’t set the zelevation of a mesh point to negative value, and the xy positions are relative to the sprite’s bounding box. Probably can get how to work around that from rufus’ example.

    Otherwise 3D shapes aren’t usable because you can’t rotate them. But there is a third party plugin you could use that does do that.

    Sorry I’m not really good at writing step by step solution stuff.

R0J0hound's avatar

R0J0hound

Member since 15 Jun, 2009

Twitter
R0J0hound has 156 followers

Connect with R0J0hound

buymeacoffee.com

Trophy Case

  • 15-Year Club
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

28/44
How to earn trophies