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
The upper side is cropped when the window is too big #1163
Comments
|
Hi, The issue is, when the window was bigger than the monitor screen, the rendering was shifted (the upper side was cropped) and cursor position seemed not to match with the screen. Is that correct? |
|
I could not reproduce this on macOS. I'll try Windows or Linux later. BTW, thank you for using Ebiten! |
|
Confirmed. |
|
Thank you for taking a look! I'm only able to replicate on Windows for what it's worth. |
@mortenson Is my understanding correct? |
|
You can use this fix by specifying the latest Ebiten ( I don't plan to back-port this fix to 1.11 so far, but if you think this fix is urgent, I'm fine with back-porting. What do you think? |
|
Your understanding was correct. 👍 It's not urgent 😄 My game jam game is already submitted so I'm in no rush. Thanks again! |
I made an Ebiten game recently and decided that the normal resolution (800x600) was too small for the majority of users, so I decided to call
ebiten.SetScreenScale(1.5)in the game loop to scale it up by default (https://github.com/mortenson/trianglovers/blob/master/main.go#L376).Some Windows users have reported that the cursor is slightly offset by default, but when they enter full screen mode (by pressing "f"), or set the scale back to "1" (by pressing "s"), the cursor works as expected. I think this only happens when the scale makes the window larger than the computer's native resolution.
On my machine, I was able to replicate this by making the screen scale much higher (3). When that happened, the window looks like this:
You can see the "Normal mode" button hovering, but my cursor (not shown) is actually hovering over "Sam" below.
Any idea what's going on here?
The text was updated successfully, but these errors were encountered: