Sub Switching causes problems

[aradragoon]

Please read the FAQ/Common Issues section of the README before opening a ticket. Please remove sections of this template you do not find relevant when creating your ticket.

Environment details

• kancolle-auto version (date on first line of your CHANGELOG.md): 2017-06-07 ([Release 10
• Viewer/browser: Chrome 60.0.3112.101
• Operating system: Windows 10

Issue

Is the issue consistent (can be reproduced consistently) or is it transient (only happens sometimes)?: consistent

When using sub switching the program will eventually get stuck in the repair dock. Nothing is being done and the program seems to get caught in a loop attempting to do something but the result is that it is unable to do anything, expeditions battles etc.

Relevant config snippet (if applicable)

[Combat]
Enabled = True
FleetComps = 1
Area = 3
Subarea = 2
CombinedFleet = False
Nodes = 1
NodeSelects =
Formations = double_line
NightBattles = False
RetreatLimit = 2
RepairLimit = 1
RepairTimeLimit = 9900
ReserveDocks = False
CheckFatigue = False
PortCheck = False
MedalStop = False
LastNodePush = False

[SubmarineSwitch]
Enabled = True
EnabledSubs = ss
ReplaceLimit =
FatigueSwitch = False
UseBuckets = False

[lainconnue]

Value for replace limit? 2 taiha 1shouha

…

On 20 Aug 2017 09:38, "aradragoon" ***@***.***> wrote: *Please read the FAQ/Common Issues section of the README before opening a ticket. Please remove sections of this template you do not find relevant when creating your ticket.* Environment details - kancolle-auto version (date on first line of your CHANGELOG.md): 2017-06-07 ([Release 10 - Viewer/browser: Chrome 60.0.3112.101 - Operating system: Windows 10 Issue Is the issue consistent (can be reproduced consistently) or is it transient (only happens sometimes)?: consistent When using sub switching the program will eventually get stuck in the repair dock. Nothing is being done and the program seems to get caught in a loop attempting to do something but the result is that it is unable to do anything, expeditions battles etc. Relevant config snippet (if applicable) [Combat] Enabled = True FleetComps = 1 Area = 3 Subarea = 2 CombinedFleet = False Nodes = 1 NodeSelects = Formations = double_line NightBattles = False RetreatLimit = 2 RepairLimit = 1 RepairTimeLimit = 9900 ReserveDocks = False CheckFatigue = False PortCheck = False MedalStop = False LastNodePush = False [SubmarineSwitch] Enabled = True EnabledSubs = ss ReplaceLimit = FatigueSwitch = False UseBuckets = False — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#390>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATdLFAOwUl_UyD42Z859Mu6xueCV4nsMks5sZ44hgaJpZM4O8fXC> .

[aradragoon]

I tried 1 and 0 which https://github.com/mrmin123/kancolle-auto/wiki/Setup-config.ini gives as valid values.

I ran into the same issue on the value 0 and with no value. If I set it to value 1 I had an issue where the program decided to move me from 1 ss to 3 ss in my fleet gradually. Not sure if it would have continued and made my whole fleet ss. I took it back out and left it out since it says that the replace limit is used on top of switching subs being repaired which is all I really need.

[kenahamtan]

Having this issue for quite some time.

for any ship going into repair, at the repair start confirm, the cursor did not move to the repair_start_confirm button, the program crash out.

[mrmin123]

Completely forgot about this issue. I'll take a closer look tonight once I'm home.

[kenahamtan]

Thanks for the quick respond.

The log goes lke this:

�[94m[2017-09-06 08:53:51] Available docks: 4; repair queue: 1�[0m
[log] CLICK on L(321,276)@s(0)[0,0 1440x900] (530 msec)
�[94m[2017-09-06 08:53:57] Check for critically damaged ships.�[0m
�[94m[2017-09-06 08:53:58] Check for moderately-damaged ships.�[0m
�[94m[2017-09-06 08:53:59] Check for lightly-damaged ships.�[0m
[log] CLICK on L(533,244)@s(0)[0,0 1440x900] (539 msec)
�[92m[2017-09-06 08:54:00] Starting repair on lightly damaged ship!�[0m
�[94m[2017-09-06 08:54:02] Got valid timer (00:24:52)!�[0m
�[92m[2017-09-06 08:54:02] Repair should be done at 2017-09-06 09:17:02�[0m
[log] CLICK on L(730,552)@s(0)[0,0 1440x900] (535 msec)
[log] TYPE "#ESC."
�[91m[2017-09-06 08:54:18] Non-catbomb script crash, or catbomb script crash w/ unsupported Viewer!�[0m
FindFailed: repair_start_confirm.png: (104x28) in S(0)[0,0 1440x900] E:Y, T:3.0
Line 2718, in file Region.java

[error] script [ C:\kancolle-auto-r3\kancolle_auto.sikuli ] stopped with error in line 542
[error] FindFailed ( repair_start_confirm.png: (104x28) in S(0)[0,0 1440x900] E:Y, T:3.0 )
[error] --- Traceback --- error source first
line: module ( function ) statement
585: util ( pattern_generator ) m = match(r'M[\d+,\d+ (\d+)x(\d+)]', str(find(pic)))
544: util ( wait_and_click ) kc_region.wait(pattern_generator(kc_region, pic, expand), time)
574: combat ( go_repair ) wait_and_click(self.kc_region, 'repair_start_confirm.png', 10)
256: main ( sortie_action ) combat_item.go_repair()
478: main ( kancolle_auto_wrapper ) sortie_action()
540: main ( ) kancolle_auto_wrapper()
[error] --- Traceback --- end --------------

[mrmin123]

@aradragoon @kenahamtan unfortunately there isn't much for me to work with in the info and logs provided. What screen exactly does the script crash on? Do you have subtitles on and if so, how large are the fonts?

[kenahamtan]

Its at the screen where confirm repair for the ship. The button is repair_start_confirm.png in combat.
Subtitle is enabled and font 12px.
The cursor did not move to the button.
FindFailed: repair_start_confirm.png: (104x28) in S(0)[0,0 1440x900] E:Y, T:3.0
Line 2718, in file Region.java

[mrmin123]

I can't reproduce this error and it might be a network lag related deal... Try raising the SleepModifier in the config to 1 or 2.

[kenahamtan]

Tried SleepModifier 10. Still same issue.
Reinstalled Java, still same issue.
Another computer with Win7 64bit, no issue.

[kenahamtan]

A Tablet with Atom 1.5Ghz 4C4T and 4GB ram makes the repair modules very unstable even when raised the SleepModifier to 20.
Moved to a desktop 2.6Ghz 4C8T and 8GB works flawlessly.