Closed moonlee7777 closed 8 years ago
I would try upping the SleepModifier to 1 or 2.
I set it to both 1 and 2 in separate times, but the error is still showing up.
You'll need to observe kancolle-auto closely and find out what's exactly
happening at the time of a crash. Timing is especially important as
kancolle-auto does not do an exists
check for the next button. Important
things: what screen? What's on the log? What is the mouse doing before the
crash? What is the log saying right as it happens? Is what the log saying
in line with what is happening on the screen? Is it at a screen where
looking for the next button would make sense? Etc. If kancolle-auto is
crashing because the next button can't be found because the next button
hasn't loaded yet, then you need to adjust the sleep modifier accordingly.
On Thu, Jul 7, 2016 at 11:11 AM, moonlee7777 notifications@github.com wrote:
I set it to both 1 and 2 in separate times, but the error is still showing up.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mrmin123/kancolle-auto/issues/194#issuecomment-231161463, or mute the thread https://github.com/notifications/unsubscribe/AEIF0qUe_dPYoWhzDQB-ndbCYPfWLK5Iks5qTUFhgaJpZM4JGud9 .
Nevermind, it's going smoothly after setting it to 2 for a while. Thank you.
Cool, closing now.
It tends to mostly crash on the sortie map selection screen, but also on the expedition screen and the refuel screen. I don't think it's a bug, but more a problem with my setup. Here are some things that might help you out:
config.zip