7 ms·
I wish they would use this in Windows 8. As far as I can tell, their scaling algorithm for 4k displays is: scale up 2x using nearest neighbor, then randomly dr
by jrockway 13y ago
I wish they would use this in Windows 8. As far as I can tell, their scaling algorithm for 4k displays is: scale up 2x using nearest neighbor, then randomly drop pixels to get back to 125% or 150%. The result is horrifyingly bad. Not just kind of bad, but unusably bad. (Adding insult to injury, they ClearType the text before scaling.)
- bluedino 13y agoI would guess it's for performance reasons.
- jrockway 13y agoI have 4 i7 cores and a $500 graphics card. I feel like it's possible :) TF2, for example, plays beautifully at 3840x2160@60Hz. Scaling up the graphics for an 800x600 visual novel that plays at 1 frame per 30 seconds is computationally possible. (The good news is that someone has written an emulator for one VN that I'm working through, so I should be able to play with scaling in that way. If I can get it to compile.)
- rkuykendall-com 13y agoDo you know if MS is working on Mac-Style resolution independence for W9? I'm currently running a Retina MBP, at 2x res I think, and it works _perfectly_. The first few months some apps didn't work well, but the community adapted very quickly.
- bri3d 13y agoWindows has had support for resolution independence where DPI is configurable across a continuum (rather than only available as 1x or 2x scale like on the Mac) for quite some time - the issue is that with a huge legacy application base, a giant morass of drawing technologies, and no shipped "HiDPI" or "Retina" Windows hardware until recently, there's been no real incentive for app developers to support it. In Windows 7 and 8, WPF apps are already supposed to be resolution independent (vector-based). Old-style GDI+ apps which aren't marked as "resolution aware" (i.e. almost everything) are poorly scaled by the window manager and hideously ugly.
- DougBTX 13y ago> (rather than only available as 1x or 2x scale like on the Mac) It isn't continuous, but there are more than two scaling levels on OS X: https://blog.qt.digia.com/wp-content/uploads/2013/04/qtRetinaMacDisplaySettings.png https://blog.qt.digia.com/wp-content/uploads/2013/04/qtRetin... More details: https://blog.qt.digia.com/blog/2013/04/25/retina-display-support-for-mac-os-ios-and-x11/ https://blog.qt.digia.com/blog/2013/04/25/retina-display-sup...
- bri3d 13y agoRight, but as noted in the blog you link the application is still only exposed to 1x or 2x scale (where 1pt = 2px), and then everything is scaled back down. On Windows the app is exposed to the scale factor (for better or worse): https://blog.qt.digia.com/blog/2009/06/26/improving-support-for-higher-dpi-on-vista/ https://blog.qt.digia.com/blog/2009/06/26/improving-support-...
- interpol_p 13y agoPrior to retina display Macs, OS X implemented resolution independence as an arbitrary scale factor, with most of the UI elements being vector rendered. You could test it out with Quartz Debug. TextEdit, for example, scaled very nicely and remained crisp at arbitrary scale factors. They didn't end up using this approach because the 2x mode is so simple, and will likely be the last scale factor really needed (especially with the additional scaling modes).
- jjcm 13y agoWhile something similar would probably be better, this is heavily optimized for pixel artwork. Lots of curves, shading, and most importantly - limited colors. UI is generally much straighter, less shaded, with far more colors. Here's an example of UI that's scaled with potrace (a similar algorithm): http://i.imgur.com/jDq4M7e.png http://i.imgur.com/jDq4M7e.png (left side is the converted side, right side is nearest-neighbor. Top is 3x, bottom is 2x) That's with the highest amount of colors/depth that potrace allows. On an i7 processor, it takes a LONG time to compute all of that. Each icon is no longer just a couple hundred pixels, it's a couple hundred vector paths. Even rendering it takes a number of seconds to refresh the screen in inkscape.
- krakensden 13y ago> That's with the highest amount of colors/depth that potrace allows. On an i7 processor, it takes a LONG time to compute all of that. OTOH, for icons, you just need to compute that once and then cache the png.
- dublinben 13y ago1. That looks awful. 2. We just need vector-based icons already.
- slazaro 13y agoI think the ideal would be something similar to fonts: there's the vector definition for big sizes, and optional pixel-perfect definition for small sizes, because rendering vectors on very small sizes (16x16, 32x32) might look worse than hand-crafted pixel work.
- oofabz 13y agoThese days, font rendering does not often rely on bitmaps, even at small sizes. Instead, they typically use hinting and subpixel rendering. I would love to see these effective techniques applied to vector graphics too.
- deleted 13y ago[deleted]
- balls187 13y agoUnfortunately I think this is just the price of being an early adopter.