You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The native resolution is marked as Invalid in Ventura 13.2 but just happens to work. The app checks if it's Ventura 13.2 or newer and does match the native resolution and un-invalidate it in a special logic. But the app doesn't account for the fact that the resolution might be flipped so it's not un-invalidated then. This should be fixed.
The text was updated successfully, but these errors were encountered:
Abt #1537, there is a problem with screen rotation in BetterDisplay.
If the screen resolution is set to anything other than 100%, rotating the screen will cause the screen size jumping.
For example, with the screen set to 120% display (2304x1296 HiDPI) in the horizontal position (no rotation), rotate the screen 90° in BetterDisplay to portrait view. The screen resolution will then change to 200% (2160x3840 HiDPI).
In this state, change the screen resolution to 120% (1296x2304 HiDPI) and change the rotation to the horizontal position. The screen size will then change to 68% (1296x729 HiDPI).
I think you may be confused about the handling of vertical and horizontal when the screen is rotated. Because when the resolution is set to 100%, this strange phenomenon does not occur.
BetterDisplay 1.4.3
MacBook Pro 13 inch M1 2020
macOS Monterey 12.6.3
Acer CB241HYK (23.8 inch 4K)
change rotation at 120%
waydabber
changed the title
Some invalid resolutions do not show up properly when the display is in portrait orientation
Various display rotation / portrait orientation issues
Feb 17, 2023
All right, the problem seems to be on the macOS side - these resolutions (having flags that do not correspond to any specified display mode flags) do not honor rotation settings. I'll try to fix it with a workaround.
For more info see:
https://ptb.discord.com/channels/903276571773771796/903276571773771799/1075885910119436288
The text was updated successfully, but these errors were encountered: