BDSP Eggs Autonomous Error - Unexpected dialog when releasing

[crimson gull]

While running the eggs autonomous program, I had 3 instances of this error overnight. The program was able to self recover, but since it can get the error and reset before checking the rest of the hatched mons, there could be missed shinies.

I was watching when the first error occurred, and I did not see any abnormal dialog.

I'm on the latest release, using a teensy. The only thing I can think of is that I recently switch to a new capture card, but it was similar specs to my old one.

Error logs and screenshot for each instance is attached.

[quaint egret]

u need to have the iv or stat page up in boxes

the display on the right side, ur missing it

have to click the + on ur switch to show

in the automation software, the keyboard control for it is the =

[crimson gull]

it is up

the menu goes away when you release the mons

but that shouldn't affect how the program runs

you can see in the logs that the program was reading stats of each hatch, and watching the error live doesn't show any abnormal dialog

[quaint egret]

huh

is it happening while receiving eggs from daycare man? bc ive had that issue a few times recently & it always self-recovers

but i get message that it "couldnt find daycare man" when it happens to me

that was on v0.55.2, havent had issue yet on current release

[crimson gull]

no? its happening when releasing pokemon as i said. the error message is "unexpected dialog when releasing"

the program does self recover and i wouldn't be concerned about it if it wasn't because the error can happen in the middle of checking a batch, which means the program can miss shinies if one of the unchecked mons was shiny

from what i can tell there isn't anything wrong with the dialog box or any extra messages when releasing

it could be a dropped frame or input that makes the program think there was extra dialog but idk

[fiery lion]

Looking at the code, there's something seriously wrong here. There should only be 1 dialog after releasing. The program will clear up to 3 dialogs before it decides something is seriously wrong and gives that error.

For us to look any further into this, you will need to use OBS to record the entire session with the log visible in real time (and scrolled to the bottom). Then when it happens we'll need that portion cut out for us to see.

[crimson gull]

well the last session was 12 overnight and had 3 errors but i ran it again today for around the same amount of time and no error so i guess it’s fixed 😂

i did switch to the esp32 to test it out instead of the teensy tho idk if that changes anything