Weird behaviour with diagonals enabled about easystarjs HOT 8 CLOSED

Hey CubixSystem. Thanks for opening an issue. Let me see if I can create a test which reproduces this issue. The start and end points you provided are helpful information. What size is your map ? Are there any other settings such as tile costs ?

Can you provide the version of EasyStar you are using?

from easystarjs.

Thanks for your great work and fast response.
I am very impressed by possibility of setting tile costs!

version is 0.2.1, from npm
In examples above I use this code:

  var EasyStar = require('easystarjs');
  var easystar = new EasyStar.js();
  var grid = [];
  for (var i = 0; i < 20; i++) {
    grid[i] = [];
    for (var j = 0; j < 20; j++) {
      grid[i][j] = 0;
    }
  }
  easystar.setGrid(grid);
  easystar.setAcceptableTiles([0]);
  easystar.enableDiagonals();

Similar to #16, without easystar.enableDiagonals(); all works fine.

from easystarjs.

Order of points is very important:
Start point (2, 2)
End point (4, 4)

Start point (4,4)
End point (2, 2)

from easystarjs.

Hey CubixSystem. Thanks for all of the details you provided. Can you let me know if the latest commit fixes your issue ?

from easystarjs.

@prettymuchbryce still the same:

from easystarjs.

Are you using 0.2.2 from npm ?
Is the 4,4 to 2,2 search working as expected now ?
Can you provide me with the start/end coordinates of the 3 searches being performed on the grid from the above image ?

from easystarjs.

It was problem on my side, I update to 0.2.2 but forget to update client-packed scripts.
Now It all works as expected!
Thank you! 👍
I continue my tests and let you know If I met any other issues.

from easystarjs.

No problem. I'm happy to help. Please feel free to open another issue if you experience any other problems. Good luck with your game. It looks cool. 😎

from easystarjs.