SandLouse's Forum Posts

• • SandLouse
  • 
  • • Joined 19 May, 2015
    • 
    • 2 topics • 6 posts
  • 1

  • 21 May, 2015
  • Quote

  [quote:sv0172v6]"You have the option to check whether a Cell is an obstacle or not using the path finding. So you could use that for checking."

  Yes, this is my point exactly. So how do you do it?

  [quote:sv0172v6]"The cell size is based on the settings in the path finding. So if cell size is set to 30 each cell will be 30x30 pixel so you could use this information to make a functionality to check cells around the object. "

  How?

• • SandLouse
  • 
  • • Joined 19 May, 2015
    • 
    • 2 topics • 6 posts
  • 1

  • 20 May, 2015
  • Quote

  Let me ask a different question -

  How do you determine what cell that an object using the pathfinding behavior will move through next? (cell coordinates not layout coordinates)

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • SandLouse
  • 
  • • Joined 19 May, 2015
    • 
    • 2 topics • 6 posts
  • 1

  • 20 May, 2015
  • Quote

  Let me ask a different question -

  How do you determine what cell that an object using the pathfinding behavior will move through next? (cell coordinates not layout coordinates)

• • SandLouse
  • 
  • • Joined 19 May, 2015
    • 
    • 2 topics • 6 posts
  • 1

  • 20 May, 2015
  • Quote

  1 - Why? What happens to the grid during all of this?

  2 - The built in collisions when misused as a workaround for bad pathfinding not only eat your processor alive, they do not yield reliable or useful results.

• • SandLouse
  • 
  • • Joined 19 May, 2015
    • 
    • 2 topics • 6 posts
  • 1

  • 20 May, 2015
  • Quote

  How do I get a sprite, using the Pathfinding behavior, to -

  1.) Check the next single cell of its path for obstacles, (cell of the A* grid).

  (The very next cell mind you, cant afford to regenerate the whole path every time it scans for an obstacle.)

  2.) Choose between moving into the cell (if the cell is not obstructed)

  OR performing an alternative action (if the cell is obstructed).

  3.) Repeat.

• • SandLouse
  • 
  • • Joined 19 May, 2015
    • 
    • 2 topics • 6 posts
  • 1

  • 19 May, 2015
  • Quote

  I've been trying to set up path finding using the built in path finding behavior. This has been extremely frustrating, as the official documentation is incomplete, and the path finding example file uses a workaround. Where can I find a complete list of expressions that this behavior uses? The manuals list was missing most of what I need. How do I see the array that it uses? How do I refer to specific cells, by their number, without using some weird inefficient workaround like generating another grid on top of it or creating a new array just to keep track of the original? How do I change these cells obstacle status? How do I see which cells, (not nodes) the pathfinding object will be moving through or moving to next? How can I find out what numbers to use for the path finding condition "is cell obstacle" when the cell being tested by this condition needs to change in real time?