#Problems with Auto Story since Electric Badge Segment

84 messages · Page 1 of 1 (latest)

frosty kestrel
#

SInce I am fairly new to all this i will try to describe my issue in the best way possible.
After the Update I tried out the new Auto Story feature with an new Account and it worked perfectly (thanks you very much to all the devs) until it encountered the Electric Arena mission with the Search Minigame. It looped the mini game for 12 hrs straight (over the night) and could not get passed it. It could not find the person in the picture and resettet after zooming in once or twice. then i resettet everything including my macbook and tried again. It still could not get passed it even after few more tries. so i finished the electric mission and badge manually and let it automate the next segment (steel titan).
similar issue accured, the character walked for a little bit, got the phone call, walked a little bit and resettet the game. tried this one aswell a few times and nothing changed. so i completed this one manually aswell.

Next would be the Poision Star Segment, but when starting this mission it only gets to the point where it opens the map and then loops the map: opening closing, opening closing etc. (error in log window is that it could not find fast travel)

so it seems that something broke right before the electric badge and it hasnt run since.

can anybody provide some suggestions what i can try?

blissful palm
#

Hard to know without a video recording.

#

These are all likely separate issues.

#

Posting logs would help too.

#

!programlogs

raven tartanBOT
#

To help the developers understand the automation problem you're facing, please find the log file and upload it to the help channel.

Where are the logs?

The logs are created in a file called "SerialPrograms.log".
On Windows, it is in the folder where you launch the program. On macOS, it is at /Users/<your_username>/Library/Application Support/SerialPrograms/.

Whenever the log file reaches about 50MB its content will move to SerialPrograms-<timestamp>.log. Depending on how recent the problem is you may need to look for logs in older log files.

You can send the whole log file (which may be large!) or isolate the lines that illustrate the problem you are facing.

Each line in the file has a time and date stamp. Use that to find the portion of the logs where the problem occurred. You can edit the file with any text editor.

If the text editor is too slow to work on large files, choose a modern high-performance text editor like the free Sublime Text Editor.

frosty kestrel
blissful palm
#

The problem in this case is that you didn't visit the Fly point next to Orthworm.

#

because you did that segment manually.

#

See the blue marker here.

#

If you visit that fast travel point, so that it shows up on your minimap. Autostory should be able to resume.

frosty kestrel
#

Ah, did not realize there was one, I thought it had troubles recognizing the pokecenter

#

Thank you

blissful palm
#

As for why it failed with the Electric gym challenge, it's an issue with detecting the white triangle within the star.

#

I can't fix it unfortunately, without your screenshot.

earnest socket
#

Do these send error reports?

blissful palm
#

Error reports are automatically generated if the error bubbles up to the top, right?

earnest socket
#

yeah

blissful palm
#

Each reset does not generate an error report. because resets are expected.

#

but when it fails 100 times, the error bubbles up to the top. so hopefully, an error report was generated.

earnest socket
#

@frosty kestrel If the program asks you to submit error reports, please say yes. If these errors were recorded, they'll probably be in the foldersErrorReportsLocal or ErrorReportsSent/.

frosty kestrel
#

Same folder paths as the logs? If so I don’t see any

blissful palm
#

As for why it failed to get to Orthworm. It looks like you only gave it less than 5 attempts. You may have just gotten unlucky. Various things can cause it to fail, such as Switch variance causing the marker not to be placed exactly where it needs to. Or Tera raid crystals throwing off the placement of the marker. I would only be concerned if it fails >10-20 times.

frosty kestrel
#

Alright thank you 🙏🏼
Maybe you are right, I kinda got skeptical after the electric segment so I just did it manually 🤓

#

Btw quick notice, I had to visit all nearby pokemoncenters (including the city below) now it works

earnest socket
frosty kestrel
#

Issue is still bugging me sadly, I thought that it was solved because the character started moving to the right mission and startet the Trainer battle before entering the Star Minigame. All of this works. But after the counter on the minigame hits 3..2..1.. then the program just closes the game and restarts the segment.
I let it run this time and the program killed itself after 100 fails. But I cannot find an error log anywhere.

#

I will try recording the issue aswell, will take me a few minutes tho

#

Ignore the first logs, I cut out the part where I started the Mission approximately

blissful palm
#

It's failing to detect the North symbol in the minimap. Please send a screenshot when it enters the Team Star base and it fails.

#

There's another issue somewhere. It looks like it's having issue placing down markers. But I'll need video to debug.

frosty kestrel
#

HDR is turned off,
I recorded 2 different types of error that acure during this task. Video was to big had to put it on a link.
It’s loading will take 2-3 minutes

#

Feel free to ping me when answering

blissful palm
#

Normally, it can unlock it itself, but within the Team Star minigame, it can't do it.

#

In the other video, it failed just due to bad luck. Sometimes Pokemon in the minimap will cover the North symbol, so it can't detect direction. So the program resets and tries again. Nothing we can do about that.

#

If you unlock the minimap, that should hopefully fix your issue.

frosty kestrel
#

Will try and let you know any other things that might or might not happenyaybulba

#

Problem solved🎊
Thank you for being this helpful

earnest socket
#

How did the program get that far with the minimap locked? Or is that the first phase that needs it?

frosty kestrel
#

Honestly it is highly possible that I misclicked something while dealing with the first 2 issues manually

earnest socket
#

You changed the settings?

frosty kestrel
#

Map locking is enabled and disabled via clicking the cursor, so I probably locked it while using the mini map without knowing

#

But that is just a guess, don’t know what really happened

earnest socket
#

You mean pressing down on the joystick?

frosty kestrel
#

Yes

earnest socket
#

I didn’t know that. lul

frosty kestrel
#

Me neither, and that is probably how it happened I would guessKEKW

blissful palm
#

yes. Almost certainly that you clicked the stick while using it manually. Autostory unlocks the minimap in the tutorial, and it assumes that it's unlocked for the rest of the time. Normally, it can unlock it on its own, but the Team Star minigame prevents that.

earnest socket
#

This probably won't be the only corner case left. When AutoStory announcement goes out this weekend, jw will be full time fixing AutoStory. laughinginfurnace

frosty kestrel
earnest socket
#

This was bound to happen. AutoStory is absolutely massive. And it hasn't really been advertised. That will change this weekend.

frosty kestrel
#

can shomebody explain me what causes this error: beginning of the area zero segment after arriving at zero gate

#

"CoreML execution provider is not supported in this build"

blissful palm
#

Can you post the logs?

#

Maybe this is a Mac issue with YOLO? @buoyant nova

frosty kestrel
#

i think its logged somewhere in here, i tried cutting out most of stuff before and after, since i switched programs now to shiny hunt in the meanwhile haha

blissful palm
#

What macOS version do you use?

frosty kestrel
buoyant nova
#

What MacBook? What cpu?

frosty kestrel
#

MacBook AIr M1

buoyant nova
#

What year’s MacBook?

frosty kestrel
buoyant nova
#

Oh I forgot CoreML on Mac needs a special ONNX runtime build sadman

#

We will fix this by running on CPU for Mac users first. At same time need Koi to set up macOS builds to use that custom ONNX runtime KEKW

frosty kestrel
pallid flint
#

What custom onnx runtime?

proud thicket
#

I'm also confused because from https://github.com/cansik/onnxruntime-silicon:

⚠️ The official ONNX Runtime now includes arm64 binaries for MacOS as well with Core ML support. Please use the official wheel package as this repository is no longer needed.

blissful palm
#

I think we used a custom onnx runtime to get GPU support for Windows. So, when we changed the onnx runtime, we might have lost support for mac.

buoyant nova
#

I know the ONNX runtime I got from Homebrew on macOS does not come with CoreML support

#

I had to build ONNX Runtime on my own locally on my MacBook to get an ONNX Runtime library that supports CoreML

pallid flint
#

I use the brew one. Should I build from source? If so, will need to modify CMakeLists.txt because it's currently hard-coded to look two dirs below SerialPrograms which is no bueno.

buoyant nova
#

As far as I know you would need to build from source. I will check if I have notes for enabling CoreML when I go back home

pallid flint
#

Or maybe the brew one works now, who knows. Have no way to test myself atm.

buoyant nova
#

I already set the cmakelist in arduino-source to prioritize my local built ONNX runtime, which is in a git repo placed in the same folder as arduino-source

buoyant nova
buoyant nova
pallid flint
#

I see that in CMake logs but hard-coding like that is not ideal. Especially for CI.

I don't have YOLO models nor do I have a save that's further than 15 minutes into the game.

buoyant nova
#

YOLO models are already part of the package repo. SV Auto Story uses them

#

You don’t need to go to Area 0 in game to test YOLO. Just enter game and run the model with model path option set to the YOLO models in Packages for Auto Story purposes