-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not quite finding all spawns in big areas #26
Comments
that looks to me like one or more of the threads crashed, what version was this done on, how many workers, and how many steps? |
Going back to the log and yeah, it seems like a lot of threads crashed trying to sleep a negative time. The version was one from ~10 hours ago. Will try a rescan with your update ^^ |
if many threads crashed, i would also change stepsPerPassPerWorker in the config down to 45 |
I'll try that. On a side note, the time for doing a 'pass' seems to increase a lot sometimes. |
hmm, passes should take 500-600 seconds, lower numbers tend to mean its the tread that got all the oddments not done by the others, but numbers that high are concerning (anything over 900 is definitely not getting all the spawns) |
There are clear patterns where no pokemon spawns are found. This only happens in large areas
(See the following picture)
http://i.imgur.com/teU9V0O.jpg
There are some horizontal lines where no pokemons are found, even though there are definitely pokemons there.
I'm not sure what causes it, but I suspect that workers are jumping too far (from the far right to the far left) when a 'row' is completed- resulting in no pokemons found for a long duration.
The text was updated successfully, but these errors were encountered: