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
Describe the issue
After creating a macOS VM on an Apple Silicon host, and enabling the "HiDPI (Retina)" setting on the Display tab, the VM window still opens in pixel-doubled size by default (after launch, or after clicking the "Resize Console" button). The guest OS correctly recognizes the display as HiDPI and applies 2x scaling by default, however UTM's default window size is still 2x scaled as well. This results in "4x scaled" display relative to the physical screen's native resolution.
The window can be manually resized, but getting the 1:1 pixel-perfect size requires mad pixel-perfect mouse movements ;) (or scripting)
I'd expect the window to open at 1:1 pixel-perfect scale by default when the "HiDPI (Retina)" mode is enabled, as is the case with QEMU backend machines.
The VM is set to 1680x1050 resolution with HiDPI enabled; this screenshot was taken just after launching it, and it shows that the physical size is 3360x2100 and scaling is evident: Zrzut ekranu 2022-05-2 o 18 52 08.png
The text was updated successfully, but these errors were encountered:
Describe the issue
After creating a macOS VM on an Apple Silicon host, and enabling the "HiDPI (Retina)" setting on the Display tab, the VM window still opens in pixel-doubled size by default (after launch, or after clicking the "Resize Console" button). The guest OS correctly recognizes the display as HiDPI and applies 2x scaling by default, however UTM's default window size is still 2x scaled as well. This results in "4x scaled" display relative to the physical screen's native resolution.
The window can be manually resized, but getting the 1:1 pixel-perfect size requires mad pixel-perfect mouse movements ;) (or scripting)
I'd expect the window to open at 1:1 pixel-perfect scale by default when the "HiDPI (Retina)" mode is enabled, as is the case with QEMU backend machines.
Configuration
Upload VM
The text was updated successfully, but these errors were encountered: