JoystickMoveToPosition not working as expected

[KyleKun]

Hello,

I'm trying to use JoystickMoveToPosition on my map built with tiled where my objects have polygon collision, but the a_star algorithm seems to not detect them, resulting in locking the player as shown in the video:

Screen_Recording_20210606-183952.mp4

[RafaelBarbosatec]

Hi @KyleKun !
Those elements that contain collision were added as Decoration or by Tiled

[KyleKun]

By Tiled only

[RafaelBarbosatec]

humm. Ok
I will try to reproduce here. can you send a print with the showCollisionArea property equal to true?

[KyleKun]

It's very difficult to see because of the color but the collision is there, player collides with normal joystick

[KyleKun]

I've tested a little bit more and it seems that collisions are overlapping and this is the cause of "locking" the player, player's collision enters the object's collision

[RafaelBarbosatec]

Understand. I will try to simulate a scenario similar to yours. Because it wasn't to trace a route that passes through the objectives that have collision.
In the example of the package it works perfectly.
I'll investigate further.

[RafaelBarbosatec]

Could you send me a print with constructionMode: true ?
Just to get a sense of the tileSize of the map.
Because if there is something collision on the tile. it already discards that option as a path.
I've already noticed an adjustment that needs to be done.

[KyleKun]

Sure, tileSize is 16x16 and "double tileSize" is 20.0 on main.dart

Map is small:

[RafaelBarbosatec]

I've already identified the problem. I'm thinking here of a way to solve this. Hahaha
I set up a matrix to send the algorithm to calculate the path. But in this matrix I'm noticing that a very large collision object occupies more than one cell in the matrix and I wasn't considering that.

[RafaelBarbosatec]

Hi @KyleKun
I guess what resolve this problem.
Fiz available in 1.1.2 version.
I also updated the documentation with more information about this functionality.
https://bonfire-engine.github.io/#/path_finding

I hope it’s works good 😊

[KyleKun]

Will test it asap, thanks very much!

[KyleKun]

The scenario with the table and chairs is fixed, but it still happens in some places, see these 2 videos:

Screen_Recording_20210612-130748.mp4

Screen_Recording_20210612-130929.mp4

[RafaelBarbosatec]

Hi @KyleKun
Try uses 1.1.4 version.

[KyleKun]

Hi @RafaelBarbosatec ,
It still happens in some places, and now the player movement is a little "shaky", check the video:

output.mp4

I've 2 suggestions but maybe they are quite complex to implement:

1. Somehow trace the shortest path without having to go through the center of the tile, it would make the movement more natural

2. Add some default space between player collision and any object collision (very little space), just to make sure that even if the path shocks with something, the player won't be stuck on the object's collision and it will be possible to click somewhere else

[RafaelBarbosatec]

Hi @KyleKun !

Good suggestions. I will work on it.
In this specific case it is because it currently checks for visible collisions on the screen. and on this particular route, he had to turn around and pass a chair that wasn't on the screen.
I can fix it too. increasing the size of the space for route analysis.

[RafaelBarbosatec]

You can check theses spaces that is considered collision adding:

        setupMoveToPositionAlongThePath(
            showBarriersCalculated: true, 
        )

in the player constructor.

[RafaelBarbosatec]

Hi @KyleKun !
Retest with the latest version please

[KyleKun]

It works like a charm!
I'll be closing this issue, thank you once again xD