-
Notifications
You must be signed in to change notification settings - Fork 121
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
1280x720 after ultrawide resolution #62
Comments
Also in this type of situation programm just crashes. I think we should process exceptions generated by Convert.ToDecimal. Or maybe use Decimal.TryParse? |
Yea some user recently have figure out this ui bug recently as well. I will need to put a faq or more instructions on how to deal with the issue. Yea i use decimal try parse, I just got to keep looking for more breaking points. I should have designed my program to fail from the beginning instead of realizing how important it is to do so. |
How did you fix this? I'm experiencing the same issue (also using widescreen). The artifacts column shows 7 columns, but the scanner is missing 1 column. Thanks in advance for your help. |
@call-me-void mentioning. |
@mynameisdolor just fully close the game while it is in1280x720 windowed mode. Then open it again. |
I am closing this issue in favor of issue #40's thread |
Just wanted to notify you, that when genshin resolution is switched from ultrawide (3440x1440 in my case) to 1280x720 the game looks slightly different. The most striking difference is the number of artifact collumns, it equals 6 instead of 7. Also, navigation and pretty much all offsets are off.
I ended up forking and fixing offsets, thinking the devs have updated UI. But it's just a bug/feature of the game. In order for the game to show proper UI one should close it and restart with 1280x720 as the starting resolution (or any 16:9 for that matter).
Maybe it should be stated somewhere in help/wiki. Or even better you can check for this type of misalignment in future versions.
The text was updated successfully, but these errors were encountered: