-
Notifications
You must be signed in to change notification settings - Fork 13
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
Scanner can't seem to scan character after light cones and artifacts. #66
Comments
Looks like the number "40" isn't being parsed correctly from "40/43" under Character. Could you turn Debug Mode in the scanner configure tab, scan only characters, and then go to the debug folder (it gets created in the same folder as your output directory) and send the screenshot that has "40/43" on it here? Looks like I'm gonna need to tweak the sensitivity of the image processing for that part. |
And as an extra test, does this still happen on 1600x900 resolution? |
That is so strange. I'm able to parse 40/43 correctly when I save and run the exact same OCR function on that image. It does look like that the 40 is rather close to the boundary of the image, so I'm gonna try increasing the size of the character count screenshot that the scanner takes and hopefully the numbers will get picked up properly. |
Lmk if it works or not on the latest release |
Now I get the following exception: [10:13:13] [WARN] > Failed to parse character name. Got error: not enough values to unpack (expected 2, got 1). Retrying... (5/5) Same settings as above (1600 x 900) |
That looks like a different issue now because it managed to reach the character screen. Which character does it not parse correctly? (could you send the screenshot of the character name) |
I had this same issue, I was able to fix it by disabling HDR on my monitor. Seems the increase in brightness can cause issues with the detection |
Adding a quick note here, I was getting 'Failed to parse level.' and errors related to having invalid values for relics. Used Debug mode and saw my screenshots were super bright. Should have read the NOTES more closely about HDR needing to be off. I feel like that should be a second bullet, instead of being in the dual monitor config bullet, but that might just be me |
That makes sense to me. I'll do that, thanks for the suggestion! |
Hello! I wonder if it's because of the choice of ESC menu (cellphone) background skin. Can you try different skins and see if that fixes the problem? |
It works when I only scan my Light Cones and Characters, but when I try to scan all 3 I get: During handling of the above exception, another exception occurred: Traceback (most recent call last): I tried changing the background a couple times |
Can you try increasing the navigation delay slider in the configure tab? |
I'm using HSR Scanner beta v0.6.1 and made sure the game is in 16:9 resolution and window. Stood in a dark space and no light in the background. Scanning was going just find, but, when it gets to characters it goes the data bank instead and it abort the scan. I don't what else I need to do for characters, but i did try it with faster scanning settings. My only guess is the scanner hasn't registered the new characters, so I'm turning to you guys if got any idea.
[17:57:24] > Starting scan...
[17:57:24] > Scanning light cones...
[17:57:30] > Quantity: 210/1500.
[17:58:18] > Finished scanning light cones.
[17:58:18] > Scanning relics...
[17:58:24] > Quantity: 650/1500.
[17:58:24] > Sorting by Rarity... (was Lv)
[18:01:01] > Finished scanning relics.
[18:01:01] > Scanning characters...
[18:01:03] > Character total: 43.
[18:01:03] > Scan aborted with error ValueError: Failed to parse character count from Data Bank screen. Got "43" instead. (Try scanning with a different in-game background, window resolution, or fullscreen/windowed mode, or increasing nav/scan delay in scanner configuration.)
The text was updated successfully, but these errors were encountered: