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

Solve error #35

Closed
marcincichocki opened this issue Apr 2, 2021 · 0 comments · Fixed by #37
Closed

Solve error #35

marcincichocki opened this issue Apr 2, 2021 · 0 comments · Fixed by #37
Assignees

Comments

@marcincichocki
Copy link
Owner

marcincichocki commented Apr 2, 2021

Describe the bug
Autosolver broke after successful ocr read

To Reproduce
Try to solve attached png

Expected behavior
Should solve it.

Software information

  • OS: Windows 10
  • autosolver version: 1.4.0
  • autosolver flags(if applicable):
  • monitor resolution: 2560x1440
  • gamma(if applicable):

Cyberpunk 2077 information

  • version: 1.2
  • resolution: 2560x1440
  • language: japanese
  • gamma(if applicable):

Additional context
error 1440p

error 1080p

EDIT: looks like bottleneck is sequence production(not enough fallback values). Also lack of error handling makes it weird for end user.

@marcincichocki marcincichocki self-assigned this Apr 2, 2021
marcincichocki added a commit that referenced this issue Apr 5, 2021
More sequences will be generated, drastically increasing success chances of a program.

Also, sequences now contain exact information about daemons they implement, specifically 
in what order they appear, their strength and child sequences.

fixes #20 
fixes #35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant