If you are going to use the ASUS PQ321Q, you’re going to want DisplayPort 1.2 support. HDMI will work, but it’ll be choppy with its 30Hz refresh rate. If you have a video card with dual HDMI 1.4 outputs, you can use both of them to drive it at 60Hz if your video driver supports it. DisplayPort 1.2 allows for Multi-Stream Transport (MST) support, letting you drive two displays with a single DP cable. But why does that matter if the ASUS is your only monitor? Because to get the full 60Hz refresh rate out of it, DisplayPort needs to see it as a pair of 1920x2160 monitors that each get their own signal.

The ASUS has MST mode disabled by default. With my NVIDIA GTX 660 Ti I had to manually enable it in the monitor for it to turn on. I’ve been told that with ATI or Intel GPUs over DisplayPort 1.2 it is automatic, but I don’t have those to test with. Once enabled, it quickly went from 30 Hz to 60 Hz while staying at 3840x2160 resolution.

Since I run multiple displays like most people, this seemed to be an ideal time to test out Windows 8.1 and its ability to offer individual DPI scaling on monitors. For this test I used the ASUS PQ321Q, connected over DispayPort, and a Nixeus VUE 30 (review forthcoming) connected over DVI running at 2560x1600. With a single universal setting, you use a percentage setting for scaling in Windows 8.1. With individual control, you use a slider more like on a Retina MacBook Pro. The percentage is hidden, which I dislike. I don’t understand why we have a different way to select the scaling level if you have two monitors versus one. Perhaps it is a beta issue, but I think they should be uniform.

Moving beyond that, when I attempted to scale the PQ321Q, I had an image that was still fuzzy instead of sharp. Thankfully a driver update (as 4K MST panels are new) fixed this issue quickly. The independent display scaling in Windows 8.1 still didn’t work the way I wanted it to. The choices are unclear, including which monitor you are adjusting, and I never could get it setup exactly how I wanted it. I wound up setting it to 150% for both displays and dealing with my 27” running with larger icons than I prefer.

Now I have an effective 2560x1440 desktop, only everything is sharp. Amazingly sharp. It is like moving from my iPhone 3G to the iPhone 4 and its retina screen. The text as I write this in Word is crisp and clear, and editing gigantic spreadsheet in Excel is much easier when the cells are so easy to read. Unfortunately not every application in Windows plays well with DPI scaling.

Chrome is scaled 150% as Windows asked, but it is hazy and blurry. Disabling DPI scaling for the application and then scaling to 150% inside Chrome produces crisp, clear text. Firefox also didn’t scale automatically, but it has a setting to adjust to make it follow the Windows DPI scaling rules. Once set, Firefox looks very nice and crisp. For most people, that setting should already be set to follow DPI scaling.

Finding a chat client that works well is a challenge. Both Pidgin and Trillian don’t do DPI scaling and are fuzzy by default. Another app that had issues is Steam. Right-clicking in the System Tray icon brought up a menu in the middle of the screen, where it would be without DPI scaling. The reality is that some apps are great and support DPI scaling, and some need work, just like when the retina MacBook Pro was released. Evernote looks great, but Acrobat is a fuzzy mess. This is all a bit of growing pains, but I find myself disabling DPI scaling on applications that don’t support it because I prefer tiny and sharp to fuzzy and large.

Because the 2560x1440 resolution is what I’m used to with my usual 27” monitor, I found there to be no real difference in how I used the ASUS monitor. I typically split items to different sides of the screen, with Word on the right and Evernote on the left as I type this. The application that benefitted for me was image editing. Being able to fit more on the screen, or zoom in to higher levels, made working with images on the ASUS better than on a 27” of the same effective resolution. I don’t do that much image editing, but for the work I have done it has been wonderful.

You’ll also quickly find out how much people need to go back and fix up programs or websites to use images and text separately. Text combined in an image scales very poorly, but is often easier than doing proper layout for two separate elements. I feel a bit bad for all the developers that need to go back to fix everything to work with high-DPI screens, but that time has come.

The only way to sum up daily use of the ASUS PQ321Q is “awesome”. It’s not perfect, but much of that is the fault of Windows or other programs and websites. When you have something that can scale and look correct, it is amazing how much the extra pixel density and sharpness helps. Yes, this is the future for displays, and we are entering the transition period to get there.

Introduction, Design and Specs Internal Scaling, Brightness and Contrast
Comments Locked


View All Comments

  • DanNeely - Tuesday, July 23, 2013 - link

    As someone who's been in love with his 30" 2560x1600 display for the past 3.5 years the only thing seriously wrong with this display is it's still about twice what I'm willing to spend.

    Ideally I'd like another inch in the diagonal just to give it the same vertical height as the pair of 20" 1200x1600 screens I'll probably be flanking it with. (I don't have enough desk space to keep the old 30 as a flanker.)
  • Rick83 - Tuesday, July 23, 2013 - link

    I'd prefer if I could avoid the flankers, and just get a screen that is natively wide. 36" 21:9 with 4096 horizontal pixels would be a good start. And going wider wouldn't hurt either, 3:1 - 4:1 h:v ratios should work on most desks.

    Of course, by then horizontal resolution would reach into the 8k pixels, and display port would have a little cry about required bandwidth, and it would take >1000W of GPU power to render anything halfway complex, at 16MP.... With pixel doubling we're back down to 4MP though, much like a current 30" screen.

    I know, pipe dreams, but I just bought new screens, so I can wait another decade or so....I hope people have been buying those 29" 21:9 screens en-masse though, so that manufacturers get it, that there's a market for wide screens, if they have enough vertical pixels.
  • DanNeely - Tuesday, July 23, 2013 - link

    At a 3:1 width (4960/1600), 16" tall, and a normal sitting distance a flat display wouldn't work well. If curved screens ever go mainstream a monolithic display might make sense; until then 3 separate monitors lets me angle the side two so my viewing distance is roughly constant across the entire array.
  • Rick83 - Wednesday, July 24, 2013 - link

    For gaming, it has to be flat, until proper multi-head rendering gets implemented. Otherwise the distortion will mess things up.
    And for films, the central 2.35:1 area should also be flat.
  • sheh - Tuesday, July 23, 2013 - link

    ASUS hinted at 24" hi-DPI monitors in about a year.
    At the end here: http://www.tomshardware.com/reviews/asus-ama-toms-...
  • bobbozzo - Tuesday, July 23, 2013 - link

    I'm getting farsighted (and can't tolerate reading glasses due to the horrible lighting at work (I know, the should fix it)), and am considering moving to a 27" monitor and putting it further back on my desk to reduce eyestrain.
  • Cataclysm_ZA - Tuesday, July 23, 2013 - link

    Chris, can you please test out scaling in Windows 8.1 with the DPI setting on 200% for us? That enables pixel-doubling and that may also make more applications and websites look a lot clearer. If Anand can try out the same thing with his RMBP and Windows 8.1, it would be interesting to see the results.
  • JDG1980 - Tuesday, July 23, 2013 - link

    Does 200% DPI on Windows 8.1 actually do nearest-neighbor scaling on legacy applications? The other scaling factors use GPU scaling (probably bilinear or bicubic) if I'm not mistaken, resulting in the fuzzy results described by the reviewer.
  • freedom4556 - Tuesday, July 23, 2013 - link

    On Windows 8 vanilla you have a choice between Vista-style (GPU) and XP-style DPI scaling, and the XP method doesn't appear to use the GPU scaling methods described, but only text scales and not images and other non-text UI elements, leading to layout issues in most legacy apps.
  • cheinonen - Wednesday, July 24, 2013 - link

    At 200% the poorly scaled text is more readable than before. Things that do scale correctly are incredibly sharp, though I wouldn't keep it here as I miss the desktop space too much. It's certainly better than 150% on those poorly scaled items, but just too large IMO.

Log in

Don't have an account? Sign up now