#Item Printer RNG Heavy Ball Bug
33 messages · Page 1 of 1 (latest)
I've tried it 3 times, got the same error all three times.
Also I'm using the older switch, not the OLED.
Can you go to the change date menu, set the date to what the program was trying to set it to and take a screenshot?
Looks like it's trying to set it to July 24, 2029 11:53::11. And it's unable to read the month.
Thoughts on solutions for this? We can either get rid of the '/' -> 7 in the substitution table. Or we use read_number_waterfill for the date reader.
7 -> / is probably one of the most common misreads. I need to see what the OCR is actually reading. I don't think it should be reading the slash to begin with.
when I looked into it. the filtered binary image looked fine; it was just a 7. but depending on how slanted it is, it can misread as a '/'.
the '/' -> 7 is a relatively new addition to the substitution table. I think all the prints were working fine before that.
It was added because it was breaking for someone. 
The yellow boxes are the US ones. So it's not actually covering the /. OCR must be "making it up" (which it does quite often.)
What the fuck. Since when did they add this option? 
So now you have 6 combinations:
White: Default
White: Invert
White: Greyscale
Black: Default
Black: Invert
Black: Greyscale
Invert for either white or black fails completely. Like it doesn't even detect that it's on the date change menu.
this time this was the set date, even though it should be July,, not March
@gloomy rampart Try switching to "Basic Black" under Themes. That should fix the issue for now.
for some reason, it doesn't misread in dark mode. (at least for me)
I just tested it out with read_number_waterfill, and it works in both light and dark mode. It no longer misreads the 7.
Can you send post the full game screenshot of that date menu for both March and July?
it seems to work now when switched to Dark mode
Switch it back to the non-working settings. I want the screenshots of the non-working ones so I can fix them.
oh you got it?
So OCR made up the /.
yes.
What the fuck tesseract? 
I think we should just use read_number_waterfill from now on. I find it to be more reliable.
and waterfill is performant enough that I don't notice much of a hit in performance.
I think the date setting function predated read_number_waterfill.
I'll make this fix, since I'm also trying to make it work for the other color themes.
the only annoying part will be that you have to specify the min and max RGB values, which will be different for each font color.
I have a color scheme that works for all 6 settings on my cap-card.