4k Monitor Display issues

Hello, I am having an issue since landing a 4k monitor that the images, text and such look very low res when I zoom out at anything under %110. This was not an issue on my previous 2k monitor. 4k monitor image: 2k monitor image As you can see from the images, the 4k one looks "crunchy" while the 2k monitor one does not. Both were zoomed in at 69% I am using chrome with newest version. Strangely enough this does not occur on Firefox. As you can see below: Unfortunately Firefox is not a viable option for me as it lags considerably over chrome. (I have recommended settings for both browsers.) I am wondering if there is a setting I am overlooking? Any help would be appreciated! UPDATE: Managed to fix this by following the instructions from this blog: <a href="https://blogs.windows.com/windowsdeveloper/2017/05/19/improving-high-dpi-experience-gdi-based-desktop-apps/" rel="nofollow">https://blogs.windows.com/windowsdeveloper/2017/05/19/improving-high-dpi-experience-gdi-based-desktop-apps/</a>

Hi Alex! Most threads I've seen on this subject suggest that It's unlikely to be resolvable. Here is a detailed explanation from a 6 year old post . Some of it is out of date, but I think it describes what's going on: So what's probably going on here has to do with how Windows handles high-resolution displays. There are two modes -- one where everything runs at the "native" resolution of the display (and where everything will look really "tiny" if that makes sense) and then another mode where your display runs at a "virtual" resolution and then Windows tries to scale that up. Here's some info on it: <a href="http://www.infoworld.com/article/2952506/microsoft" rel="nofollow">http://www.infoworld.com/article/2952506/microsoft</a>... The most relevant passage is probably this: For apps that aren't high-DPI aware, Microsoft has a quick and dirty fix called DPI virtualization. Windows deliberately reports the wrong DPI resolution to such apps, so their elements render as if they were on a lower-resolution display. The results are then zoomed to fit the current display. While this trick allows UI elements like buttons and dialog boxes to appear at the right size and proportions, it also makes text blurry, icons fuzzy, and images hazy. ClearType-rendered text looks particularly bad, since the subpixel rendering used for it only works when it matches the resolution of the display. (Sounds familiar?) So it seems like Chrome and Firefox are both treated as "non high-DPI apps" by Windows. It looks like there might be some steps we can take (outlined here:&nbsp; <a href="http://stackoverflow.com/questions/15661339/how-do" rel="nofollow">http://stackoverflow.com/questions/15661339/how-do</a>... &nbsp;) to change how our canvas rendering works (although it sure would be nice if Chrome just handled this for us), so we'll take a look at that and see if we can figure something out. Here is one user's solution, which may not be helpful in your case: Update Update: I have solved the issue. It would appear that the DPI scaling of the monitor throws off the quality IMMENSLEY. The original monitor was 100% scaling, the new blurry monitor was 200%. Dropped the new monitor to 100%, and while everything is tiny as all get out, at least it's clear. You could try reaching out in a&nbsp; Help Center Request &nbsp;and see if there is any more up-to-date information.

keithcurtis said: Hi Alex! Most threads I've seen on this subject suggest that It's unlikely to be resolvable. Here is a detailed explanation from a 6 year old post . Some of it is out of date, but I think it describes what's going on: So what's probably going on here has to do with how Windows handles high-resolution displays. There are two modes -- one where everything runs at the "native" resolution of the display (and where everything will look really "tiny" if that makes sense) and then another mode where your display runs at a "virtual" resolution and then Windows tries to scale that up. Here's some info on it: <a href="http://www.infoworld.com/article/2952506/microsoft" rel="nofollow">http://www.infoworld.com/article/2952506/microsoft</a>... The most relevant passage is probably this: For apps that aren't high-DPI aware, Microsoft has a quick and dirty fix called DPI virtualization. Windows deliberately reports the wrong DPI resolution to such apps, so their elements render as if they were on a lower-resolution display. The results are then zoomed to fit the current display. While this trick allows UI elements like buttons and dialog boxes to appear at the right size and proportions, it also makes text blurry, icons fuzzy, and images hazy. ClearType-rendered text looks particularly bad, since the subpixel rendering used for it only works when it matches the resolution of the display. (Sounds familiar?) So it seems like Chrome and Firefox are both treated as "non high-DPI apps" by Windows. It looks like there might be some steps we can take (outlined here:&nbsp; <a href="http://stackoverflow.com/questions/15661339/how-do" rel="nofollow">http://stackoverflow.com/questions/15661339/how-do</a>... &nbsp;) to change how our canvas rendering works (although it sure would be nice if Chrome just handled this for us), so we'll take a look at that and see if we can figure something out. Here is one user's solution, which may not be helpful in your case: Update Update: I have solved the issue. It would appear that the DPI scaling of the monitor throws off the quality IMMENSLEY. The original monitor was 100% scaling, the new blurry monitor was 200%. Dropped the new monitor to 100%, and while everything is tiny as all get out, at least it's clear. You could try reaching out in a&nbsp; Help Center Request &nbsp;and see if there is any more up-to-date information. Thank you for the reply! I think I will give those solutions an attempt. As far as Firefox lagging, do you have any suggestions on why it might be lagging over chrome? Chrome Roll20 Firefox Roll20

Check if Hardware acceleration is enabled on Firefox? Comparative performance on each browser really does seem to be inconsistent between users. It could also be because Firefox is (by some reports) 4K compatible, so you may just simply be serving up more pixels? I purchased a new monitor earlier this year, and deliberately chose a widescreen standard resolution monitor over a 4K monitor, just for fear of this. I don't regret the choice, since I was after more screen real estate rather than tinier pixels.

BTW, thanks for the comparative videos. It looks like FF is not as smooth as Chrome but it looks playable. It might come down to a choice between responsiveness and clarity. I did do some looking into a Google search of "Chrome on 4K" and there might be extensions and such to investigate. Without a 4K monitor, though, there's not much I can do to test. If you do find a solution, please post it here for the benefit of others with the same issue.