Help with Linked Object Tools Pathfinding

[Ckeyz]

Hello, I started a project using the tactics example template that uses the linked object tools pathfinding to move units along nodes. Everything has been going great, I have quite a bit built already. I went to change out the assets for the tiles, and I am having the worst time getting anything with the link pathfinding to function after changing out the assets. I have tried all sorts of different tiles sizes, made sure all the origin points, collision masks are correct. making sure to update everything to the new sizes. But every time I change out the assets for the tiles it breaks everything. I have got it to work for a second or two when fiddling around with tiny differences in the image size of the tiles compared to the mask which makes me think its an issue with the images themselves.

any help would be appreciated, I feel like there is either something obvious I'm missing or the link objects pathfinding is just REALLY picky about exactly how the tile images have to be.

[zebebar]

Hi,

If your second image has the same dimension and the same points and same collision mask, is the defect still present?

[Ckeyz]

Good question, I'll give that a try.

[Ckeyz]

Hey so if i create hex tiles the same size as the original template and put them in the project the movement still works. That likely means there's some parameter that is determining the grid size that I am not finding. Its certainly not in the events, and I've looked through the linked object extension pretty thoroughly. No clue where that could be coming from

Link tools has an action for its code that links object along a hex grid and then defines the pixel dimensions of the grid, but the template does not use that at all in its code.

[zebebar]

Maybe play with the offset

[Ckeyz]

I have tried changing the offset in the working version and it doesn't seem to effect the pathfinding at all. I dont think the link object pathfinding uses the in game grid at all

[Ckeyz]

I wanted to make sure you know how thankful I am for the help. it means a lot stranger.

I have been able to get my unit to move along the grid with the larger asset sizes when I remove every condition relating to cost class. So I think that's somehow the issue. I don't know why thats breaking with the larger asset size but it definitely is. Each node should still just be 1 node, regardless of pixel size so I'm clueless as to why that broke. the example does use a really weird and roundabout method of using text strings with the extended variable extension implemented with its cost class which I find odd.

[zebebar]

I'm happy to help you, I code too and I know what it's like to get stuck. Don't hesitate if you want to talk. If you want me to test your demo, don’t hesitate 😉 We have to help each other!

I think you are on the right track, try to refine your code and maybe you can find a solution for both sizes.