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

Scanned image is offset #192

Closed
afrasso opened this issue Jan 29, 2022 · 3 comments
Closed

Scanned image is offset #192

afrasso opened this issue Jan 29, 2022 · 3 comments

Comments

@afrasso
Copy link

afrasso commented Jan 29, 2022

First, thank you for working on this program. I've used it before without issues, and it's great for artifact analysis. :)

When I downloaded the latest release (1.2), when I scan my artifacts the screenshot is offset (see the attached screenshot I grabbed from the logging/artifacts folder):
artifact0

I currently have my resolution set to 1920x1080, but I tried a bunch of the different resolutions, and all seemed to have the same problem.

Any ideas?

@afrasso
Copy link
Author

afrasso commented Jan 29, 2022

Update: I completely closed out GI and restarted it, and that seems to have fixed the issue. Not sure why. I usually play on a widescreen monitor with a resolution of 3440x1440, so many that has something to do with it.

@afrasso
Copy link
Author

afrasso commented Jan 29, 2022

I can confirm I can reproduce the issue again by going back to 3440x1400 fullscreen, exiting out of GI, reopening it, and setting the resolution to 1920x1080. Something about changing the resolution while in-game is different than if you start up the game with that resolution (things are slightly shifted around).

@Cupcak3
Copy link
Collaborator

Cupcak3 commented Jan 29, 2022

There is a specific behavior with Genshin and ultrawide resolutions. Issue #40 figured it out that the UI on ultrawide is compressed slightly. Changing resolutions in Genshin keeps this compressed UI until a restart. We can probably adjust screen region capturing but it's low priority for now since a reliable fix is known. I'll add something about this to the readme

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

No branches or pull requests

2 participants