Skip to content
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

open deck when auto start, and can not recognize the image #258

Closed
SurpassIllusion opened this issue Oct 19, 2024 · 6 comments · Fixed by #259
Closed

open deck when auto start, and can not recognize the image #258

SurpassIllusion opened this issue Oct 19, 2024 · 6 comments · Fixed by #259
Milestone

Comments

@SurpassIllusion
Copy link

SurpassIllusion commented Oct 19, 2024

when the system aoto starts, it always opens Battle Deck, I'm sure the resolution is adjusted to 720 * 1080. I don't know if this is related to the scaling of my desktop 1.5, but there are still problems after adjusting the scaling to 1. And when I manually start the game, the system cannot recognize it correctly

@fe-art
Copy link
Collaborator

fe-art commented Oct 19, 2024

hey, please send terminal logs

@SurpassIllusion
Copy link
Author

[2024-10-19 22:36:24] INFO | main_window:start_bot:91 - Starting bot
[2024-10-19 22:36:24] DEBUG | emulator:_run_command:139 - D:\Project\github\ClashRoyaleBuildABot\clashroyalebuildabot\emulator\platform-tools\adb -s emulator-5554 kill-server
[2024-10-19 22:36:24] DEBUG | emulator:_run_command:150 - Command executed in 0.038475990295410156 seconds
[2024-10-19 22:36:24] DEBUG | emulator:_run_command:139 - D:\Project\github\ClashRoyaleBuildABot\clashroyalebuildabot\emulator\platform-tools\adb -s emulator-5554 start-server
[2024-10-19 22:36:27] DEBUG | emulator:_run_command:150 - Command executed in 2.059553623199463 seconds
[2024-10-19 22:36:27] INFO | emulator:_get_valid_device_serial:44 - Trying to connect to device 'emulator-5554' from config.
[2024-10-19 22:36:27] DEBUG | emulator:_run_command:139 - D:\Project\github\ClashRoyaleBuildABot\clashroyalebuildabot\emulator\platform-tools\adb -s emulator-5554 get-state
[2024-10-19 22:36:27] DEBUG | emulator:_run_command:150 - Command executed in 0.023287057876586914 seconds
[2024-10-19 22:36:27] INFO | emulator:_get_valid_device_serial:48 - Successfully connected to the device 'emulator-5554' from config.
[2024-10-19 22:36:27] DEBUG | emulator:_run_command:139 - D:\Project\github\ClashRoyaleBuildABot\clashroyalebuildabot\emulator\platform-tools\adb -s emulator-5554 shell wm size
[2024-10-19 22:36:27] DEBUG | emulator:_run_command:150 - Command executed in 0.04107213020324707 seconds
[2024-10-19 22:36:27] DEBUG | emulator:_update_frame:176 - Starting to update frames...
[2024-10-19 22:36:27] DEBUG | emulator:take_screenshot:241 - Starting to take screenshot...
[2024-10-19 22:36:27] DEBUG | detector:run:35 - Setting state...
[2024-10-19 22:36:27] INFO | bot:step:171 - New screen state: Screen(name='lobby', ltrb=(315, 48, 356, 89), click_xy=(220, 830))
[2024-10-19 22:36:27] DEBUG | emulator:_run_command:139 - D:\Project\github\ClashRoyaleBuildABot\clashroyalebuildabot\emulator\platform-tools\adb -s emulator-5554 shell input tap 220 830
[2024-10-19 22:36:28] DEBUG | emulator:_run_command:150 - Command executed in 0.22602152824401855 seconds
[2024-10-19 22:36:28] INFO | bot:_log_and_wait:71 - Starting game. Waiting for 2 seconds.
[2024-10-19 22:36:30] DEBUG | emulator:take_screenshot:241 - Starting to take screenshot...
[2024-10-19 22:36:30] DEBUG | detector:run:35 - Setting state...
[2024-10-19 22:36:30] INFO | bot:step:171 - New screen state: Screen(name='unknown', ltrb=None, click_xy=None)
[2024-10-19 22:36:30] INFO | bot:_log_and_wait:71 - Unknown screen. Waiting for 2 seconds.
[2024-10-19 22:36:32] INFO | bot:pause_or_resume:83 - Bot paused.

@Leviaria
Copy link
Collaborator

Please uninstall BlueStacks completely and reinstall it

@SurpassIllusion
Copy link
Author

it doesn't work

@Wildstylez23
Copy link

it is changed after the update i have the same problem. dont know why but i have the same. before it works fine. now it doesnt work anymore

@fe-art fe-art linked a pull request Oct 21, 2024 that will close this issue
@fe-art fe-art added this to the V1 milestone Oct 21, 2024
@SurpassIllusion
Copy link
Author

the latest commit has perfectly solved the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants