These methods DO NOT work for MBPr with Thunderbolt Display, for whatever reasons.
GET HIDPI SWITCHRESX PRO
I am here to present a solution for users with 15" MacBook Pro with Retina display connected to a Thunderbolt Display. That solved the issue I was having on one of my laptops.Īfter reading through several forums, websites, blogs. Also, if something's still not working after you did all the steps in the FAQ, consider uninstalling and reinstalling SwitchResX.
Minor update: Apple says the 2016 MBP (no distinguishing between 13 or 15) supports 5K, but Intel doesnt have 5K support in their iGPUs yet so Im thinking that only refers to 20162017 MBPs with dGPU.For users trying to do this on El Capitan, please read the FAQ on SwitchRes's website. You might want to search and see if its better in High Sierra - beta (it doesnt appear so from a quick look that I did). In any case, 5K monitors were only supported in MBPs starting in 2016. Thanks doublepost1499531374doublepostI guess another way to word the question is: Whether all these problems are still applicable to Sierra, or if they are fixed and its a HW limitation for the Late 2013 rMBP. Hence my question here to ask for others experiences when it comes to Late 2013 rMBP on 4K monitors. It thus isnt clear to me whether this is a Sierra problem, or a hardware problem. I dont think its absolutely clear whether the 3840x2160 30Hz limit is a limit in terms of driving real pixels, or even just in rendering virtual pixels. On the other hand however there are many posts saying that HiPDi works much better pre-Sierra. I do agree and suspect that the limit is at the CPU and GPUs ability to render at such high resolution and then scale it back down to 4K resolution to display. So what HiPDi should do for a 4K monitor to look like 2560x1440 is to render the asset at 5120x2880 and then downscale it to display at 4K (3840x2160) resolution. In fact, it tries to do this for a multitude of resolution Larger Text - Looks like 1024圆40 (UI element rendered at 3x) Default - Looks like 1280x800 (UI element rendered at 2560x1600 native) More Space 1 - Looks like 1440x900 (UI element rendered at 2880x1800 and downscaled to 2560x1600) More Space 2 - Looks like 1680x1050 (UI element rendered at 3360x2100 and downscaled to 2560x1600) As you can see, the resolution of the MBP monitor imposes no limit on whether the UI elements are rendered at beyond the monitors resolution. It is then downscaled through anti-aliasing into the MBPs native resolution of 2560x1600.
When More Space is selected, its displaying UI element at a size of 1680x1050 x2. I dont know if a better GPU (requires a new computer or an eGPU) would improve the quality or not (beyond the refresh rate). Why were you expecting 1440 HiDPI from a UHD (3840x2160) monitor It appears you tried resolution scaling and that wasnt satisfactory. So 1440 HiDPI requires a monitor that supports 2880 pixels vertically, which a 3840x2160 monitor cannot do. They did successfully enable 51Hz 1080 HiDPi or 51hz 2160 Native. Tried to do (3) with custom EDID that I modified to either 51Hz or 30Hz.
GET HIDPI SWITCHRESX 1080P
I put in all the valid resolution between 1080p scaled and 1440p scaled with no avail.Īll did not appear in either SwitchResX nor RDP.
Switchresx Custom Resolution 1080P Scaled And Manually fiddle with DisplayProductID plists. HiDPI means 5120 x 2880 scaled down by 2.) 3. SwitchResX with SIP disabled: Anything over 3840x2160 scaled is deemed Invalid. I went through many hoops, went through a lot of posts on both MacRumors and on, resulting in the following attempts.īuying Accell mDP - DP cable: Its claimed in a thread that this is one of the few properly DisplayPort 1.2 certified cable. If I try to do something in between, it just ends up getting not sharp.
0 kommentar(er)
