Air111
commented
4 months ago 这位群友的另一次卡住，这会不会是电脑太慢？3.7秒内没有识别到info_bar，点击EQUIP_OFF后却又识别到？
────────────────────────────────────────────── RECORD FLAGSHIP EQUIPMENT ──────────────────────────────────────────────
2024-05-03 22:19:07.301 | INFO | RECORD FLAGSHIP EQUIPMENT
2024-05-03 22:19:07.308 | INFO | <<< UI CLICK >>>
2024-05-03 22:19:07.344 | INFO | Click ( 967, 672) @ FLEET_DETAIL
2024-05-03 22:19:11.292 | INFO | Click ( 136, 388) @ FLEET_DETAIL_ENTER_FLAGSHIP
2024-05-03 22:19:17.107 | INFO | RECORD EQUIPMENT
2024-05-03 22:19:17.114 | INFO | DETAIL_SIDE_NAVBAR set to right=1 bottom=1
2024-05-03 22:19:17.127 | INFO | Nav item active: 4 from range (0, 4)
2024-05-03 22:19:17.147 | INFO | <<< UI CLICK >>>
2024-05-03 22:19:18.681 | INFO | Click ( 986, 168) @ EQUIP_INFO_BAR_3_0
2024-05-03 22:19:22.921 | INFO | <<< UI CLICK >>>
2024-05-03 22:19:22.952 | INFO | Click ( 865, 649) @ UPGRADE_ENTER
2024-05-03 22:19:26.408 | INFO | <<< UI CLICK >>>
2024-05-03 22:19:26.420 | INFO | Click ( 217, 298) @ UPGRADE_QUIT
2024-05-03 22:19:28.368 | INFO | <<< UI CLICK >>>
2024-05-03 22:19:29.430 | INFO | Click (1066, 158) @ EQUIP_INFO_BAR_4_0
2024-05-03 22:19:32.771 | INFO | <<< UI CLICK >>>
2024-05-03 22:19:32.795 | INFO | Click ( 837, 660) @ UPGRADE_ENTER
2024-05-03 22:19:35.781 | INFO | <<< UI CLICK >>>
2024-05-03 22:19:35.794 | INFO | Click ( 238, 372) @ UPGRADE_QUIT
2024-05-03 22:19:38.929 | INFO | Recorded equipment index list: [3, 4]
2024-05-03 22:19:39.023 | INFO | Click (1181, 104) @ EQUIPMENT_OPEN
2024-05-03 22:19:41.578 | INFO | Click ( 944, 583) @ EQUIP_OFF
2024-05-03 22:19:43.466 | INFO | Click ( 797, 510) @ POPUP_CONFIRM_
2024-05-03 22:19:47.146 | INFO | Click ( 972, 577) @ EQUIP_OFF
2024-05-03 22:19:48.580 | INFO | <<< UI CLICK >>>
2024-05-03 22:20:47.676 | INFO | Function calls:
<string> L1 <module>
spawn.py L105 spawn_main()
spawn.py L118 _main()
process.py L297 _bootstrap()
process.py L99 run()
process_manager.py L151 run_process()
alas.py L514 loop()
alas.py L68 run()
alas.py L395 gems_farming()
gems_farming.py L411 run()
gems_farming.py L126 flagship_change()
fleet_equipment.py L36 fleet_back()
ui.py L324 ui_back()
ui.py L80 ui_click()
device.py L161 screenshot()
device.py L219 stuck_record_check()
device.py L40 show_function_call()
2024-05-03 22:20:47.698 | WARNING | Wait too long
2024-05-03 22:20:47.706 | WARNING | Waiting for {'BACK_ARROW', 'FLEET_DETAIL_CHECK'}
2024-05-03 22:20:48.366 | INFO | [Package_name] com.bilibili.azurlane
2024-05-03 22:20:48.374 | ERROR | GameStuckError: Wait too long
2024-05-03 22:20:48.380 | WARNING | Saving error: ./log/error/1714746048380 
ec7529a2
Heipen
在提问之前...
描述你的问题
一群群友发的，实在看不懂。
DETAIL_SIDE_NAVBAR_0_3后1.3秒识别到Nav item active: 4 from range (0, 4)EQUIP_INFO_BAR_3_0的前提条件是识别到EQUIPMENT_OPEN，点击后（最终报错存储的截图）却是在装备页而不是详情页附上#3700 动画太慢导致装备还没加载完全问题（五群群友的）的原始log，也存在多余的navbar操作，但最终能切换到详情页
如何复现
No response
预期行为
No response
相关 Logs
No response
截图
No response
还有别的吗？
No response