R0J0hound's Forum Posts

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

  • 5 Feb, 2013
  • Quote

  You can do lines just as easy as points:

  http://dl.dropbox.com/u/5426011/examples16/line_trace.capx

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

  • 5 Feb, 2013
  • Quote

  When an object is created it becomes the only instance of that type that is picked. Once it is no longer picked it cannot be picked until the next top level event.

  Some more info:

  http://www.scirra.com/forum/picking-problem_topic41776_post257714.html#257714

  http://www.scirra.com/forum/r102-breaking-change-questions_topic56576_post352637.html#352637

  The way I'd do it is create the 5 sprites in one event then position them in the next.

  http://dl.dropbox.com/u/5426011/examples16/create5.capx

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

  • 3 Feb, 2013
  • Quote

  Construct 2 does not have per pixel collision detection as would be needed for this. If you build the image with smaller pieces like rotated/re-sized rectangles then that's one option.

  That being said if you really need per pixel collision detection you can get something working with the canvas plugin with the rgbaAt() expression.

  Here is a simple example:

  http://dl.dropbox.com/u/5426011/examples16/perpixel.capx

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

  • 1 Feb, 2013
  • Quote

  Jerbens

  The math is escaping me at the moment but to map a sprite to this would require a perspective transform. Google has a lot on the subject, but it may take some tinkering to get the transform to match.

  PixelPalette

  You could modify the fx so that you get the image to repeat in only a line by putting // in front of one of these lines:

  xx=clamp(xx, 0.0, 1.0/scale_x);
  yy=clamp(yy, 0.0, 1.0/scale_y);
• • R0J0hound
  • 
  • • Joined 15 Jun, 2009
    • 
    • 90 topics • 7,320 posts
  • 1

  • 1 Feb, 2013
  • Quote

  nothaseo

  That would cause pieces to disappear. The proper solution would be to split only the relevant pieces instead of all of them.

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

  • 1 Feb, 2013
  • Quote

  Here's an effect for that.

  fx: http://dl.dropbox.com/u/5426011/plugins/conditionalOpacity.zip

  capx: http://dl.dropbox.com/u/5426011/plugins/conditionalOpacity.capx

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

  • 29 Jan, 2013
  • Quote

  Set each value in the array to the value to the right.

  Array: For each X element:

  ---- Array: set value at self.CurX to self.At(self.CurX+1)

• 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

  • 28 Jan, 2013
  • Quote

  Every cut doubles the amount of objects so after 10 cuts there are 1024 objects. So it's going to have lower fps the higher the object count gets.

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

  • 24 Jan, 2013
  • Quote

  If "HP" started at 5 then yes it is the same.

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

  • 24 Jan, 2013
  • Quote

  C2 already can do this. Give the enemies an instance variable and call it "hits". Then use two events like this:

  Bullet collides with enemy:

  ----- add 1 to Enemy "hits"

  ----- destroy bullet

  Enemy "hits" >=5

  ----- destroy enemy

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

  • 20 Jan, 2013
  • Quote

  50 is just a conversion factor from box2d units/sec^2 to pixels/sec^2. I found it by measuring how far a physics object dropped and plugging it into this formula y=0.5*a*time^2 solved for a a=2*y/(time^2) which gave a value ~=500 or 50*physics.gravity.

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

  • 20 Jan, 2013
  • Quote

  The uistate files are not essential and can be deleted if need be. The file looks like it's a zip file since "PK" are the first two letters in the file. Can you open it in a zip program?

  EDIT:

  Looking at your files it looks like your gameplay eventsheet is corrupt. You can use your backups though. Open your backup capx in a zip program and extract it to a folder. For me two of the files couldn't be extacted:

  1. ..\DragonJoust.uistate.xml

  So I just deleted it.

  2. ..\Animations\player\Default\000.png

  But your zip had it so I copied it over.

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

  • 20 Jan, 2013
  • Quote

  With an undo you would want to save the state (position, variable values, etc...) that the card was before it was moved. The only issue that may come up in my example is with the positioning of stacks of cards, but there may be others.

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

  • 20 Jan, 2013
  • Quote

  If you set the physics gravity to 30 then change the global variable ay to 50*30 or 1500.

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

  • 19 Jan, 2013
  • Quote

  tanoshimi

  To clarify, pushing onto a 2d array will look like this:

  Push back A on X axis

  Set value at (self.Width-1, 1) to B

  Set value at (self.Width-1, 2) to C

  http://dl.dropbox.com/u/5426011/examples16/sorted_runs.capx