search

ssjshields / archetype-counter

PowerShell WinForm script for the online video game PokeMMO. Automatically track encounters (Horde, Safari, etc.) and manually track when you receive Eggs or Fossils. Utilizes ImageMagick and OCR technology.
41 stars 17 forks source link

Unable to scan Gloom, Bellsprout and Weepinbell #44

Closed Romsmesme closed 1 week ago

Romsmesme commented 6 months ago

Hello, I've been using your encounter counter for a few weeks now, and I'm regularly having issues with counting Gloom (single encounter, no issue with hordes), Bellsprout and Weepinbell (both with single enc, I don't know about hordes).

Here is an example with Bellsprout 1

DEBUG_OCR_OUTPUT.txt

I tried changing the Picture mode setting, tried resizing the Battle window size (as I set mine smaller than the default setting). Haven't tried the Name Fix thing, as I couldn't find the file, only the .png file.

Thanks for your time, and if you need Gloom and Weepinbell pictures and debug files, tell me!

EDIT: I have no other mods, no custom theme, only strings

realmadrid1809 commented 6 months ago

Ok, switch back to the default picture method, find another failed encounter and send us ALL the debug files (text file + 4 pngs). That way we can see what went wrong.

Romsmesme commented 6 months ago

ArchetypeScreenshot ArchetypeScreenshotEncounter ArchetypeScreenshotEncounterEx ArchetypeScreenshotMagick

DEBUG_OCR_OUTPUT.txt

realmadrid1809 commented 6 months ago

Ok so what happens is that as you can see we cut away most of the screenshot so only the names get picked up. However since you reduced the battle window size, the counter won't cut away the sleep icon. The counter thinks the sleep icon is a letter and wrongly picks up the name. The issue should not persist on 100% battle window size. If it does, please send us new reports

Romsmesme commented 6 months ago

Okay it seems to have fixed it, which is weird as I'm sure I tested going back to 100% battle window size and there was still issues

Thank you anyways !

AnonymousPoke commented 1 week ago

Issue resolved in v4.0.0.1.