R0J0hound's Forum Posts

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 19 Mar, 2013
  • Quote

  You can also use a sprite per leaf of the tree with three instance variables: parent,child1 and child2 to store the UIDs of those leafs or -1 for nothing.

  Example of building a tree:

  http://dl.dropbox.com/u/5426011/examples17/bsp.capx

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 19 Mar, 2013
  • Quote

  It's the "wait" action that is causing you the trouble. You need some additional states when waiting:

  "false" --- no queued actions.

  "upcoming action" --- countdown to perform actions.

  "true" --- start an action.

  "completing action" --- countdown.

  http://dl.dropbox.com/u/5426011/fixed/n1ch0la5.capx

  I also changed the countdown timer to use dt since every 1.0 seconds was a bit off.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 18 Mar, 2013
  • Quote

  One way to do it is with overlapping at offset with collision poly that are a bit smaller than the image, so sprite next to each other aren't counted as overlapping.

  http://dl.dropbox.com/u/5426011/examples17/virus_grow.capx

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 18 Mar, 2013
  • Quote

  You can do it with the canvas plugin. Here's an example:

  http://dl.dropbox.com/u/5426011/examples17/puzzle_piece.capx

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 18 Mar, 2013
  • Quote

  When the layout is changed all objects that are not global are destroyed.

  — if your bullets are not set to be global then I'd say its a bug that they are not destroyed on a layout change.

  The only point where I think it may be useful to destroy everything is at a layout change, but you can do that now by making all the objects not global.

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 15 Mar, 2013
  • Quote

  Have you tried measuring the cpu usage when moving the mouse without previewing? 5-7% is likely just caused by Windows posting notifications of mouse movements.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 13 Mar, 2013
  • Quote

  It opens fine here with r121 and the latest rex_moveto and rex_function plugins. Perhaps try reinstalling those plugins.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 12 Mar, 2013
  • Quote

  What errors are displayed when you try to load?

  If none then look in the projects toolbar. My guess is the cap is loaded but no editor windows are opened.

  The reason for this is .persist files, which are created per cap and keep track of what layouts and eventsheets are opened.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 11 Mar, 2013
  • Quote

  Interesting problem indeed.

  Here's another algorithm that works well but is a bit slower:

  It finds 1/7 and 1/13 quite well.

  http://dl.dropbox.com/u/5426011/examples17/dec2frac.capx

  It's based on the forth answer here:

  http://stackoverflow.com/questions/5124743/algorithm-for-simplifying-decimal-to-fractions

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 11 Mar, 2013
  • Quote

  XManBG

  It's possible. There are a few examples in this topic on how to draw shapes. Animation can be done by drawing one shape, clearing and drawing another.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 10 Mar, 2013
  • Quote

  Do you want the tile being dragged to push the other tiles or just stop?

  Number 3 can be helped by spacing the tiles out more by either position, size or collision poly. Objects right next to each other count as overlapping.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 7 Mar, 2013
  • Quote

  One way to go about it is to look up graphs of various formulas and see which most closely matches the shape of a plot of your numbers. Then you could then use some sort of regression to find a formula for it.

  In this case a little bit of intuition helped me find the formula. The more you do the easier it gets.

  formula:

  (1-n/(n+1))*100

  where n is the nth number (0 for the first)

  Edit: ninja'd with a simplified formula.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 7 Mar, 2013
  • Quote

  Save the old position of the object at the end of every tick and set it's angle at the beginning of every tick to the angle from the old position to the current as calculated by the angle() expression.

  EVERY TICK:

  set sprite angle to angle(oldx, oldy, sprite.x, sprite.y)

  set oldx to sprite.x

  set oldy to sprite.y

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 7 Mar, 2013
  • Quote

  One way to make it more accurate is to use a loop to check for collisions in between positions. Also if you restrict fence positions and sizes to grid positions it's simpler to keep it precise.

  Loops will also enable the lines to be done instantly. For example:

  http://dl.dropbox.com/u/5426011/examples17/fence.capx

  For a horizontal line the detector moves from the starting position right to just shy of a fence then back left. That gives the start and end positions.

  You can similarly find the top/left and bottom/right corners of a box in the same way. With that you can create a box to fill that area and check for collisions or calculate the area.

• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 6 Mar, 2013
  • Quote

  xavy027's idea is pretty much the way to do it. Don't use particles, instead use sprites with the bullet behavior. There is no way to get the position of individual particles of the particle object.