R0J0hound's Forum Posts

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

  • 12 Aug, 2012
  • Quote

  You're talking about the detector sprites getting stuck between the the yellow ramps and green walls, right?

  Give the yellow ramps more thickness.

  So instead of this:

  *

  **

  ***

  ****

  Do this:

  **

  ***

  ****

  *****

  *****

  Ex:http://dl.dropbox.com/u/5426011/fixed/PixelMonkey.capx

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

  • 12 Aug, 2012
  • Quote

  Google quickly revealed the formula here:

  http://en.wikipedia.org/wiki/Range_of_a_projectile

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

  • 12 Aug, 2012
  • Quote

  Can you post a capx file of the problem. Your description doesn't have enough info to locate the issue.

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

  • 12 Aug, 2012
  • Quote

  http://www.scirra.com/forum/simple-gesture-recognition_topic45379.html

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

  • 12 Aug, 2012
  • Quote

  The "is overlapping" conditions are what's causing the trouble. It compares all the picked "destination" and "walk" objects together. It's kind of hard to visualize how it behaves sometimes so if you can reduce what objects are picked it makes it simpler.

  For example you can condense the conditions in event 7 and 8 to this:

  system: for each destination

  walk: selected = destination.selected

  destination: is overlapping walk

  That way you select each pair in turn and "is overlapping" has one of each object to compare when it's reached.

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

  • 12 Aug, 2012
  • Quote

  You could do it with a top level layer. Just make it invisible until you want it viewed. The darkening could be done with a transparent black sprite covering the layout.

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

  • 12 Aug, 2012
  • Quote

  You could try some screen capture software:

  http://www.snapfiles.com/software/gmm/videocapture.html

  You could then crop the video to only the game screen with some video editing software.

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

  • 12 Aug, 2012
  • Quote

  The simplest way to do that would be to add the physics behavior to your objects.

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

  • 12 Aug, 2012
  • Quote

  I think you changed your event. Right now it will only trigger if the player leaves the top of the screen.

  Anyway to fix the crash (or hang) of your game uncheck "global" from your objects properties. When objects are global they do not get destroyed when the layout changes or restarts. So when the layout restarts when the player falls off the screen the layout restarts again because there is still a player off the layout.

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

  • 12 Aug, 2012
  • Quote

  I don't think it's a problem with the events. I have not been able to move into the walls.

  What browser are you using to test?

  It's flawless for me in Firefox 14.0.1 and Chrome 20.0.1132.47.

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

  • 12 Aug, 2012
  • Quote

  Search for "grid movement".

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

  • 12 Aug, 2012
  • Quote

  Possible, yes, but the solution has little to do with construct.

  It's done with the windows api which is normally accessed by programming in c. You can access it in Construct with python and either the ctypes or pywin32 libraries.

• 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,289 posts
  • 1

  • 12 Aug, 2012
  • Quote

  Some possible solutions:

  http://www.scirra.com/forum/destructable-space-invaders-barrier-how-do_topic54056_post337988.html?KW=worms#337988

  http://www.scirra.com/forum/destructible-terrain-better-ideas-than-this_topic55053_post344054.html#344054

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

  • 12 Aug, 2012
  • Quote

  Greg

  What C2 release are you using? The logic of the capx is sound, the wall detector is doing exactly what it is designed to do: it checks the next grid position before moving. The position lag is not the issue.

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

  • 10 Aug, 2012
  • Quote

  Here's an example:

  http://dl.dropbox.com/u/5426011/examples13/forced_scroll.cap