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

  • B3an - Tuesday, July 23, 2013 - link

    I think the individual DPI scaling in the Win 8.1 preview is broke. I don't know anyone who has got it to work properly, so i'm not surprised it didn't work for you either. Hopefully it's fixed in the final release.
  • mrdude - Tuesday, July 23, 2013 - link

    Is it interesting that the benefits of that working or not hinge greatly on what you're planning to do with this monitor?

    My first instinct is, "Awesome! Finally some great PPI for the desktop crowd," but after a bit of thinking my response is quickly subdued.

    How would I use this thing? and for what? It's very nice having additional real estate, but using a 31.5" monitor at native resolution w/o PPI scaling (to fully utilize the extra real estate) means sitting closer to it than I would a lower res monitor that's smaller in size. I guess that's one question I have for Chris: How is it like sitting 2' away from this thing for hours on end when using native resolution? I had a 27" monitor that I returned for a 1080p because I found it too big and needed to sit farther away from it.

    If you sit farther back, than the DPI scaling would have to be set higher and you'd be losing real estate - a trade-off that many would gladly live with for a sharper image. The thing is, there's still a vast majority of software out there, particularly in the Windows landscape, that can't handle or scale well, especially when it comes to legacy professional applications which tend to have cluttered menus.

    I guess my point is that there's only so much screen real estate that one needs until it starts to become a hindrance and scaling is required, and that's heavily influenced by personal preference and screen size. I would rather have three x1200 at 21-24" monitors for the screen real estate than a single 31.5" at 4K. When it comes to gaming, though, I'd love the 31.5" 4K monitor
  • airmantharp - Tuesday, July 23, 2013 - link

    I have two examples for you:

    First, games. They still need some kind of shader-based anti-aliasing, like FXAA or MSAA, but the resolution is amazing- I really enjoy 2560x1600 with a pair of GTX670's.

    Second, any application that is currently resolution limited. Think CAD, photo editing, and video editing; anything that requires a rendered visualization. For instance, I'm editing 20MP files shot from a Canon 6D on a 4MP monitor that has UI elements on it, reducing the effective workspace. A monitor with over 7MP would improve my productivity.
  • thurst0n - Tuesday, July 23, 2013 - link

    Wait, you have a 1440p 120hz IPS?
  • tviceman - Tuesday, July 23, 2013 - link

    Hey Chris,

    Out of curiosity did you try to run Half Life 2 at 1080p? Performance is going to crush most GPU's running at 4k, and I am just curious as to the clarity of the scaling when running non-native resolution that keeps the same pixel uniformity.
  • Spunjji - Tuesday, July 23, 2013 - link

    @ Chris: Out of interest, did you get any of the POST / boot failure problems with your setup that were experienced by the chaps at PCPer?
  • cheinonen - Tuesday, July 23, 2013 - link

    No, I did not. A firmware update is supposed to be coming that will fix those, but I haven't seen them.
  • Assimilator87 - Tuesday, July 23, 2013 - link

    Chris, if HDMI supports 2160p30 and DisplayPort 1.2 has double the bandwidth of HDMI, then why is MST used instead of a single signal/stream?
  • rpsgc - Tuesday, July 23, 2013 - link

    Basically, apparently there aren't timing controllers (Tcon) capable of 4K@60Hz so Sharp (and Asus) cheated and used two controllers.
  • thurst0n - Tuesday, July 23, 2013 - link

    This was supposed to be in reply to dishayu.

Log in

Don't have an account? Sign up now