Hi, when i set high dpi, i have big animate button W10 150% upscale. VP16 - 261 same problem 307. When i set upscale 100% or 125% in windows, problem is resolved, but icons etc are too small for work.
As mentioned in an other thread I have the same problem on an UHD-monitor (3840*2160). It currently only works with 125% here. Regardles if I use the application override or the new Vp16 diplay option.
As mentioned in an other thread I have the same problem on an UHD-monitor (3840*2160). It currently only works with 125% here. Regardles if I use the application override or the new Vp16 diplay option.
Hi, when i set high dpi, i have big animate button W10 150% upscale. VP16 - 261 same problem 307. When i set upscale 100% or 125% in windows, problem is resolved, but icons etc are too small for work.
Hi, any news about fixing this issue?
Build 424 still have issue
My configuration : 4K screen, no issue in 100% 125% zoom, but too small to work in good conditions.
175% zoom (same in 150%)
Tried all possible configurations (windows override settings), no success...
I have my laptop's display @ 1920x1080 and the DPI @ 175% ( I need larger toolbar icons due to my 'less than perfect eyes'. It is readable, but some render window parameters are off-screen. When this occurs, I temporarily change the DPI to 150 or 125%. It's an annoyance for sure, but I can live with it. I put a shortcut on the desktop, which takes me directly to the display settings.
The natural tendency is to Preview at full screen resolution. With a 28" UHD monitor, the human eye cannot reliably resolve the differences between 1080p, 1440p, and 2160p (before someone jumps on me, I know you can). But even Superman is not going to see anything "more" at 3840x2160.
Save full resolution for displaying your masterpiece, and edit at a comfortable size for your source preview, screen area, and font scaling. Like @rraud I switch occasionally to reveal cut-off text, but i try to keep it to a minimum. My sweet spot for much HD work is actually at 1280x720.
I am using Vegas Pro in high DPI mode in both my 15 inch laptop workstation (3840 x 2169 pixels at 225%) and in my 27 inch AIO workstation (3840 x 2169 pixels at 200%) and never experienced such problem.
The natural tendency is to Preview at full screen resolution. With a 28" UHD monitor, the human eye cannot reliably resolve the differences between 1080p, 1440p, and 2160p (before someone jumps on me, I know you can). But even Superman is not going to see anything "more" at 3840x2160.
Save full resolution for displaying your masterpiece, and edit at a comfortable size for your source preview, screen area, and font scaling. Like @rraud I switch occasionally to reveal cut-off text, but i try to keep it to a minimum. My sweet spot for much HD work is actually at 1280x720.
Put a 1080p image next to a 4k image, if you don't see a difference you should probably go see an eye doctor as you may need glasses.
On what size display? At what viewing distance? With what background lighting? How do the differences you see on the same calibrated display affect your editing (not final viewing) experience?
As for the rest of your response, please read Community Rule #1 in its entirety. It's the one titled:
1. This is a community – not a competition
Can you look at a 4k 8 bit television screen and know if it is set to resolve 1080 or 2160? The guys at Best Buy can't. I can't either, and I've been working in film and imaging since the real Technicolor days. (signature below).
We have discovered the source of this problem. We were never able to reproduce this locally until we started doing some localization work. We discovered if you have your Region & Language settings set to a region that uses commas for a decimal indication (as opposed to a period), you will see this problem. We have a fix for this and will put it in for future updates.
We have discovered the source of this problem. We were never able to reproduce this locally until we started doing some localization work. We discovered if you have your Region & Language settings set to a region that uses commas for a decimal indication (as opposed to a period), you will see this problem. We have a fix for this and will put it in for future updates.
Thanx Derek! Just applied this fix and it works!
Here is a screenshot of where to change windows setting