stein3
07-20-2014, 06:38 PM
Hey all,
I am working on making a script with a short walk through the desert.
When starting to walk, SPS gets an incorrect player position to an area on the map which looks (to me) not much like where the player actually starts from.
Sometimes getPlayerPos() actually returns a point outside of the map I have loaded.
I am using map accuracy 4, tolerance 500, and required match 0.4 through 0.6.
The walk can be done by a human in two clicks, so using an alternative to SPS would not be too difficult. I just wanted to use SPS because this would be an easy case to learn on.
What can I do to reduce these false positives?
I am working on making a script with a short walk through the desert.
When starting to walk, SPS gets an incorrect player position to an area on the map which looks (to me) not much like where the player actually starts from.
Sometimes getPlayerPos() actually returns a point outside of the map I have loaded.
I am using map accuracy 4, tolerance 500, and required match 0.4 through 0.6.
The walk can be done by a human in two clicks, so using an alternative to SPS would not be too difficult. I just wanted to use SPS because this would be an easy case to learn on.
What can I do to reduce these false positives?