Hello, ever since I updated to 0.29.5, I eventually get this error code when using Item Cloner. It worked fine (without this error) on 0.28.17, but has been happening ever since (0.29.5, 0.30.2 and 0.30.5; have not tested on the latest 0.30.7 beta). The program runs fine for a random amount of time, but eventually runs into this error. From my limited understanding, it appears the switch lags a bit for whatever reason, and the program tries to detect the menu while it is still loading, which doesn't work. I have since gone back to 0.28.17 to try to check if this was caused by a CC update, and it works fine on that version.
#"Unable to detect menu" error on Item Cloner
stuck zealot
stuck zealot
Since making this post, got the error once on 0.28.17. But I was outside, instead of inside the dorm as usual, which could cause some delay and trigger the error. I had not run into this error previously on this version. Will continue running it, but in the dorm, to see if it happens again
warm ivy
Is there by any chance a lot of video lag? And when you enable the stats overlay, do you see any yellow/orange/red in the CPU or thread utilizations?
stuck zealot
Not that I have ever seen, in any program. But I cannot know for sure if at the times of the error there was, as they happened when I wasn’t looking (I usually leave it running overnight, or when I’m away). For what it’s worth, before the last test I did on the 0.30.5, I restarted both the pc and the switch, and still got the error after some time. I’ll try to see if I can catch the high utilisation. Is there any way to automatically log them in the error log?
warm ivy
Utilization doesn't get logged. But you should be able to just watch it while it does a few iterations. If anything stays yellow or turns red even for a split second, it's an indication that your computer is slow.
That said, most programs will still work properly on computers that aren't fast enough, but you enter the realm of "gradual degradation" where the slower the computer is, problems become more and more common until things just stop working altogether.
stuck zealot
While using the newest version (0.30.7), and running several other things on my computer alongside PA, I was able to hit red CPU utilization, and brief flashes of yellow Main QT Thread. However, the program remained perfectly stable for several hours, and I was not able to recreate the error.
My first thought when I first ran into the error was indeed slow hardware (either the switch or my PC), but the problem persisted even after rebooting both. That's why I thought maybe it was a change in the code, especially since it started after a version update.
I'll keep running 0.30.7 a little more to see if it errors; and after that I'll run the old versions that where giving me troubles again. But I'm starting to think I'll just have to attribute the cause of the error to the usual Windows black magic fuckery and move on.
warm ivy
So your computer is being overutilized and the program is running in the "gradual degradation" region. 
stuck zealot
(Leaving it on running PA 24/7 probably didn't help, but that's besides the point)
stuck zealot
FYI, this is it after a reboot
stuck zealot
I think the cause is related to Windows turning off the display. Versions 0.29.5 and up give me the error only when I let the display turn off (so essentially when I idle from the pc), which explains why it doesn't happen when I am actively using the pc. However, the same doesn't happen on versions 0.28.17 and lower, regardless of the display turning off or not.
I have kept on testing all these versions, and the result is always the same:
- Versions 0.29.5 and up always error some time after I idle, but will keep running well if I am using the computer and not letting it idle.
- Versions 0.28.17 and lower will not error regardless of idling or not
The same thing used to happen to me in the earlier versions of Auto Max Lair 2.0, in which I'd also get a fatal error whenever I'd let the display turn off. It was fixed on the newer versions, so I simply moved on.
I believe I wouldn't get the error message immediately when the display would turn off, but some minutes later. So maybe it wasn't directly caused by the display turning off, but just correlated so some other thing Windows does when the user idles (sleep mode is turned off, btw)
When I get some time, I will try to disable the "Turn off the display" option on Windows and leave the program running idle to see if the error persists.
My usual settings:
