Copy link to clipboard
Copied
Hi,
I have a dual monitor Setup consisting of
1) a fairly large, non-high-dpi main screen and
2) a wacom cintiq pro 16 (a 16" 4K Display, thereby very high-dpi).
I'm on Windows 10.
I have AE windows on both screens, but the UI doesnt scale up on the cintiq, leaving me with microscopic interface elements. Obviously I wouldn't want a app-wide scale up since my main monitor looks just fine. My current solution is to scale the cintiq up to 200% using the build in windows 10 UI scaling options, but that also scales the composition viewports content, footage window etc.
So I end up with readable UI but a composition viewport that's not showing a 1:1 representation of the final image (it's scaled by a factor of 2 just like the UI)
Is there a solution for me to see the high-dpi interface on one monitor only?
How can I achieve readable Interface AND an unscaled, 1:1 viewport?
Any helpful tips are greatly appreciated
Cheers
Stephan
Short and simple: No. The apps will always adapt to the resolution settings of the primary display device, which obviously your Cintiq is not. You have to switch things around or buy a suitable second monitor.
Mylenium
Copy link to clipboard
Copied
Short and simple: No. The apps will always adapt to the resolution settings of the primary display device, which obviously your Cintiq is not. You have to switch things around or buy a suitable second monitor.
Mylenium
Copy link to clipboard
Copied
Thanks man, even though that's obviously not what I wanted to hear
How does the app determine which UI to use? Can I force the high-dpi UI on all monitors somehow?
Cheers
Copy link to clipboard
Copied
You have to set your primary monitor in Windows 10 display settings to whichever monitor has the correct scaling you want the Adobe apps to start with.
Copy link to clipboard
Copied
The correct answer, but I do feel that Adobe could fix this situation. I use other apps that have no problem switching scaling between monitors of different resolutions on Windows 10. I'm sure it's not a trivial fix. I'm also sure that Adobe is making a ton of money off the new subscription enslavement we've all bought into and could afford to fix bugs like this. It IS a bug.