-
-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FGA don't click anything on Support Servant screen #1654
Comments
I can't help you without a video |
Hello, I had the same issues (I'm on NA). It clicks to go to the next quest but it doesn't select the servant class (and the servant)in the support liste. When I go directly into the fight, it completes the entire fight, but when it goes back to the support servant selection, it repeats the same thing as before. By closing FGO and FGA several times, it worked at some point. Here what it does with the debug mod SVID_20230808_092405_1.mp4[EDIT] I change Manual to First, and it works know, I don't really understand |
try lowering the fga button so it doesn't block the support icons |
Having same issue, even when the FGA button doesn't block the support icon |
same problem |
I have the same issue with this one. It happened after updating. At first it was just scrolling down the support screen not choosing any servant, but after a restart it wasn't doing anything at all anymore. |
Ok I think I found the issue. If you have a phone that hides the camera notch, turn it off. I have an S21 Ultra and it has that feature, it's probably messing with how the script scans at the entire screen. |
Since OP doesn't respond and others post comments without any helpful info, I'll close this issue. |
Preparation
FGO server
NA
FGA build number
2113
Describe the bug
FGA never click anything on servant screen even though i choosen servant class and "first" instead of "manual" on FGA app, it started to do this when i updated this app
Video
.
Device model
Xiaomi Note 9
Android version
11
Screen size
No response
RAM
No response
The text was updated successfully, but these errors were encountered: