I've been having quite a few problems with SPS, some of which I can't explain. The root of the issue is when I use SPS_Setup twice (well, more than once). It completely messes up SPS_GetMyPos and makes it difficult (I couldn't manage to) to start a new path.
Example of using two different maps:
Simba Code:
[SPS] SPS_Setup() took 32 ms. Areas: ['9_7']
SPS_GetMyPos: Finished in 328 ms. Result = (3847, 3179)
[SPS] SPS_Setup() took 110 ms. Areas: ['banktodungeon1']
SPS_GetMyPos: Finished in 889 ms. Result = (395, 219)
As you can see, the position does change. It's just way off. This is what I should be getting:
Simba Code:
[SPS] SPS_Setup() took 125 ms. Areas: ['banktodungeon1']
SPS_GetMyPos: Finished in 717 ms. Result = (259, 123)
Also, I have to point out that the off coordinate for my SPS map change depending on the area used in the first setup.
Finally, a nice pearl that happens if you try to setup the same area twice in a row:
Simba Code:
[SPS] SPS_Setup() took 110 ms. Areas: ['banktodungeon1']
SPS_GetMyPos: Finished in 827 ms. Result = (255, 123)
[SPS] SPS_Setup() took 125 ms. Areas: ['banktodungeon1']
SPS_GetMyPos: Finished in 795 ms. Result = (-1, -1)
Successfully executed.
It has the same result with non custom maps.
It's a bit too late for me to put more thoughts into this. I'm about to put make one gigantic SPS custom map for all I need to avoid this issue, but I'd love to hear other solutions.