Skip to content
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

Unable to select support after 1st run #1619

Closed
3 tasks done
shockzcasts opened this issue Jul 3, 2023 · 9 comments
Closed
3 tasks done

Unable to select support after 1st run #1619

shockzcasts opened this issue Jul 3, 2023 · 9 comments
Labels
bug Something isn't working

Comments

@shockzcasts
Copy link

Preparation

FGO server

NA

FGA build number

2074

Describe the bug

I am unable to select supports after run 1, tried with multiple attempts, phone has no Notch option available, no other screen matching software, default support images extracted and folder replaced. No offset and game area set to default. Play button is also on the bottom left as suggested. I don't know if any offset is required, used FGA since like 2020 and had no issues back then.

Screenshot_20230704-032229_FGA
Screenshot_20230704-033757_FGA
Screenshot_20230704-033812_FGA

Screenshot_20230704-032243_FGA

Video

record_001.webm

Device model

Samsung Galazy A30

Android version

11

Screen size

1080 x 2340

RAM

4GB

@shockzcasts shockzcasts added the bug Something isn't working label Jul 3, 2023
@vybze
Copy link
Collaborator

vybze commented Jul 3, 2023

Did you get a recent phone update?

@shockzcasts
Copy link
Author

Last software update for my phone was back in February, no further updates after.

@vybze
Copy link
Collaborator

vybze commented Jul 4, 2023

You could try stopping and starting the service and also try clearing the cache. If that doesn't work you could export your scripts and uninstall and reinstall again to see if that helps

@shockzcasts
Copy link
Author

Have tried to restart the service a few times to no avail. Also exported my scripts from an older build (1655) to import to this latest build and it also hasn't worked. Can't clear cache as well because this happened immediately after a fresh install so there is no cache to clear. I have both the CI build and the EA build and only the EA is enabled right now, though both aren't working either.

@vybze
Copy link
Collaborator

vybze commented Jul 4, 2023

It seems to be having trouble telling which screen it's on, maybe @reconman can tell what's happening

@reconman
Copy link
Collaborator

reconman commented Jul 4, 2023

Did you change any fine-tune similarity values?

If not, try lowering the Min Similarity by a few % and see if that helps. I wouldn't recommend going below 75 %.

@shockzcasts
Copy link
Author

So I tried again today and it did end up working despite not changing any settings, but it is slightly inconsistent, having to restart every 4-11 runs. FGA doesn't seem to be able to track the screen in a few instances (Usually happens when the phone has a bit of a freeze)

@reconman
Copy link
Collaborator

reconman commented Jul 5, 2023

Battery optimization?

@shockzcasts
Copy link
Author

Doesn't seem to really be affecting anything, seems tuning down the similarity has helped a lot, though any time the game freezes it will completely bork the script and I'd have to restart it. I'd chalk that up to my phone more than anything though

@vybze vybze closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants