pathfinding long distances bug

0 favourites
  • 4 posts
From the Asset Store
Full game Construct 2 and Construct 3 to post on Google Play
  • Problem Description

    when I try to calculate a long distance, the pathfinder does not respond, or pathfinder trace an incorrect path

    example number one

    [attachment=2:3ln8i024][/attachment:3ln8i024]

    example number two, the path finder does not respond on my main project

    https://dl.dropboxusercontent.com/u/13512632/pathfinding%20bug2.gif

    Attach a Capx

    ____ Upload a Capx to this post ____

    [attachment=0:3ln8i024][/attachment:3ln8i024]

    Description of Capx

    this is a example of the capx problem

    this is the capx of the first case

    Steps to Reproduce Bug

    • click to anywhere
    • and watch the bug.

    Observed Result

    ____ the pathfinder does not respond, or pathfinder trace an incorrect path____

    Expected Result

    first example

    ____ the sprite go to the x ____

    second example

    in this second example on my main project. the expected result is the indicator trace a similar path like this image

    [attachment=1:3ln8i024][/attachment:3ln8i024]

    Affected Browsers

    • Chrome: (YES)
    • FireFox: (YES)
    • Internet Explorer: (YES

    Operating System and Service Pack

    ____ win 7 service pack 1 64bits ____

    Construct 2 Version ID

    ____ release 173____

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Closing as not a bug. In your attached .capx the touch positions do not line up with the layers, because you change the layer scale and use Touch.X and Touch.Y without a layer param. If you use the expressions which specify a layer e.g. Touch.X(0) or Touch.X("Game") it lines up and works OK.

  • Closing as not a bug. In your attached .capx the touch positions do not line up with the layers, because you change the layer scale and use Touch.X and Touch.Y without a layer param. If you use the expressions which specify a layer e.g. Touch.X(0) or Touch.X("Game") it lines up and works OK.

    Ashley sorry for that mistake, I update the project, but now i use the X.posx ando X.posy when we click on the map and the same bug persist; i did this because in my project I use specific pos of the objects place in the map, the strange is that the bug happen only some times no all the times

    look at the example 2, I try to trace the route to the office of other building, but the sprite stuck in the route, the posicion that i used are a office´s doors positions.

    this is how to work the code of this example

    https://www.scirra.com/forum/download/file.php?mode=view&id=4023

    [attachment=0:d5t2msbe][/attachment:d5t2msbe]

    https://dl.dropboxusercontent.com/u/13512632/pathfinding%20bug2.gif

  • Closing as not a bug. Your updated example appears to work correctly. Given the absolutely extraordinary size of the layout, it takes 10-15 seconds for my high-end desktop machine to trace a path. Once it's found the path though, it is calculated correctly and goes to the right place. I'm afraid your gif images of a project I am not familiar with are not much help; from the evidence I see here it is working correctly, just very slowly, due to the extreme scale of the layout.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)