Sierra and Scaled Resolutions BROKEN!

[campyguy]

Thanks for sticking with me as I try to resolve this.

I should say that while I hadn't deleted the entire Overrides folder (it seems to exist in my installation for a reason), I did purge my system of the plist override for my specific monitor that I downloaded as a 'hack' to get it working. When I did this and used the Acell cable, neither System Preferences.app nor my third party tool which is RDM (Retina Display Menu Beta 2) which looks like a rather old piece of software, showed the scaled resolution that I wanted.

Upon a reboot and re-instating of the haxxed plist file, RDM now (at least for this one time, who knows what will happen tomorrow) shows the HiDPI and I'm using it right now. System Preferences.app, as ever, does not.

If I can't quite get it working tomorrow I will remove RDM and the plist and maybe the entire Overrides folder, and also reset the PRAM and SMC and everything, to try and get everything as clean as possible using just Sierra and the magic compliant cable. If it does work tomorrow, however, I would quite like to not interfere with it any more in case I can never get it back again, you know?

No worries on sticking with you on this, really...

I'm familiar with RDM, IMHO it's not what I'd use on my Macs. The dev stopped supporting it two OSes ago, I'm suspecting it was related to SIP... Those overrides, in essence, block your peripheral(s) from talking to your Mac properly - not necessarily a bad thing if you have the wrong interface. I have no overrides on the 3 Macs in my home office, FWIW...

Now, a couple of updates. I'm aware of the thread on the Home Page of these forums, and I noted - to my chagrin - that some are relating issues related to cable changes but failing to mention that most of the cables "out there" aren't compliant - that's my nit to pick. But, maybe more relevant is that I noted a couple of changes before and after an install of Sierra on my 2012 Mini Server (knowing that I would be installing an SSD soon, I decided to upgrade it from 10.11 to 10.12 while I'm packing up my office for a move...). Not only did I note a change in the default resolution, but also one key bit that may or may not be relevant to all of this borking...

Before (El Capitan):

After (Sierra):

The first change, obviously, is the change in default resolution over the DP interface - 1600x900 Before and 1440p After; both using the DP interface and the same Accell cable. What is new, aside from the default resolution, is the designation of support for "Metal" and "Automatically Adjust Brightness" in the System Information app. And, after the OS upgrade the Mini Server OS interface is far more responsive - it wasn't slow before the update, but it's almost like a "Holy crap" update. I never saw 1440p over DP before, but I did over the HDMI interface that it's usually connected to.

The only change in the two screenshots above is the 323 Build Sierra update, installed over the latest 10.11 Build. The Mini is actually usable as a computer now - and, note the clarity of the screen shots as the Dell P2715Q it's connected to works great as well...

 

[Easttime]

Had me worried after finally getting my 27" Asus monitor working in hi res from my 2010 white MacBook with Apple's dual link mDP/USB cable, but I upgraded to Sierra today and all is well.

 

[miletbaker]

If you're like me and you have a 1440p monitor that you like to run in 1080p HiDPI mode using a custom plist or SwitchResX, DO NOT UPGRADE TO SIERRA.

Likewise if you have a 4K display and you like a bit more space while maintaining that sweet retina look and so you run it in 1440p HiDPI, DO NOT UPGRADE TO SIERRA.

Hi,

I had the exact same issue with my LG 27UD68P IPS 27" 4K display. After upgrading to Sierra I was left with the choice of 3 scaled resolutions instead of the normal 5 and unable to get the scaled 1440p resolution, it was either full 4k with tiny text or default (HD). I ran this command (which someone else mentioned above) and it completely fixed it for me. Try this first before buying another cable!

sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true

 

[filmak]

You should know that TB cables can and do carry DP 1.1a data, and they do work with non-TB displays/monitors. I avoid them for displays as a 2m TB cable costs me $60 and a DP-compliant cable of the same length costs under a third of that.

Sorry, but I think that TB cables can carry, as you say, DP stream, but from device to device in a TB chain. To connect a monitor you need a minidisplayport cable at the end.

 

[miletbaker]

I spoke too soon, although this setting persists for a reboot it seems to get wiped if the Mac goes to sleep. I've had a similar settings issue before (a few years ago with Yosemite I think) where settings such as KeyBoard or Display colour space randomly changed and the only solution that worked was a full wipe and re-install.

 

[campyguy]

Sorry, but I think that TB cables can carry, as you say, DP stream, but from device to device in a TB chain. To connect a monitor you need a minidisplayport cable at the end.

Don't be sorry, however, you're still mistaken. Using a TB cable gets the first DP display in the chain a DP 1.1a "signal", and DP is then terminated downstream. Using a TB cable with a TB display yields a muxed DP signal by the computer and it's demuxed at the TB display and a DP display can still be used downstream. I also don't see why anyone would use a TB cable for a DP display anyway - the latter are so much cheaper. You have your perspective, and I have mine. Over and out for me on this matter...

 

[simima.flyke]

Same here. Upgraded to Sierra, external screen resolutions goes nuts. Sometimes works, sometimes doesn't. Awesome...

 

[accentaudio]

I made a clean install of macOS Sierra on my nMP which is connected via HDMI to HDMI to an Asus MX279H 1920x1080 external monitor.

During the installation of macOS Sierra I had the same graphical glitch that you described with the Apple logo being shifted to the top left of the screen.

Furthermore, every time I boot or restart my nMP there is a graphics error in the form of a scrambled horizontal line just before the log in screen appears.

My guess is that this is an issue with macOS Sierra because I have had the same setup since OS X 10.9 Mavericks and upgraded to every new OS without a problem. I was thinking of starting a new thread about this issue as I couldn't find it mentioned anywhere until I came across this one.

You should start a new post and I will join in. Be sure to post a photo of the glitch and I will as well.
[doublepost=1474737267][/doublepost]The bottom line here, to all those defending this bug as somehow being ok, is that it's not ok. It didn't occur until Sierra and it should not be happening now. Work arounds, new cables, terminal codes, none of that should even matter. What happened to "it just works"? Obviously something changed in Sierra and it was NOT for the better of external monitor support.

 

[filmak]

however, you're still mistaken.

Oh it's not the first time.
Anyway, my setups have the aforementioned cabling, as we need DP1.2 for our 4k monitors.
IMHO there's no need to buy a cable (TB) which is built for another purpose and have only DP1.1 etc.
Cheers!

 

[campyguy]

Cheers!

And, Cheers to you as well! Have a great weekend!

 

[miletbaker]

I spoke too soon, although this setting persists for a reboot it seems to get wiped if the Mac goes to sleep. I've had a similar settings issue before (a few years ago with Yosemite I think) where settings such as KeyBoard or Display colour space randomly changed and the only solution that worked was a full wipe and re-install.

A full fresh install (wipe everything and install from USB drive) has not worked. I have even tried purchasing a Accell cable too. I have trouble with the Mac coming out of sleep, just a black screen, but if I succeed it looses the 1440p scaled resolution. Only 2k or 4k. Same on a cold boot only 2k or 4k but if I then reboot I get the scaled options.

 

[zaxa]

Hey guys,

I'm bumping this thread in hope to find someone who has a solution to this problem. I've had been using a Dell U2515H with a custom HiDPI resolution of 1920x1080 for the last years with a custom override .plist file.

With Sierra, this doesn't seem to work anymore. The OS seems to ignore the custom override. I've tried a few different resolution applications like QuickRes, SwitchResX and RDM, none of them made it possible to set the resolution of the monitor to 1920x1080 HiDPI in macOS Sierra.

This is a real dealbreaker for me, I'd downgrade if TimeMachine didn't just after upgrading decide that my backup is corrupt. I've been happy with Sierra otherwise so far, so this is incredibly annoying, to sum it up.

Also, to clarify, because this apparently confused some people: This is NOT the bug that didn't allow to choose 1440p native resolutions while connecting over HDMI, which was fixed in 10.12.1. It is a completely separate problem and deserves its own fix (by Apple, most preferably, but hey, who am I kidding).

Thanks for any helpful advice/solutions/ideas in advance!

 

[campyguy]

zaxa, you've used a few different utilities - obviously, none of them will work as you hope. I can't get to the bottom of your issues with your display - I own a small company and there's 30+ Macs running about 50+ displays on Sierra with no issues, and I ran through the betas as they progressed. I'm going to reiterate here that I can't find one Dell-supplied cable (COXOC) that meets with DisplayPort specs; we've got about 25 Dell displays in my offices.

Also, I have used RDM, QuickRes, and SwitchResX. RDM is dead. QuickRes hasn't been updated for Sierra, so IMHO for the intent of this thread it's also dead. SwitchResX uses display-specific workarounds - hacks, really - to approximate what a display might be capable of (I've got multiple paid licenses for this nifty utility, none of which I'm using now because I don't need SRX any longer).

See my post here, #26. The OP still has issues, and moved on to follow another thread without following up. What's missing is feedback about this: "... and maybe the entire Overrides folder ...". SwitchResX creates a display-unique directory/folder in the Overrides folder that delineates the capability of each display; this display-unique directory/folder isn't needed if you're using a compliant cable. If you're using a compliant cable and a display-unique directory/folder is installed your Mac/PC and display won't be able to negotiate a proper connection - sadly, IMHO the OP never followed up.

What I can offer is that more than 4 dozen DP displays are working on my Macs without issue. All of them are running DP-compliant cables and a stock Overrides folder. None of our Macs are "new"...

 

[Sheza]

Hey guys,

I'm bumping this thread in hope to find someone who has a solution to this problem. I've had been using a Dell U2515H with a custom HiDPI resolution of 1920x1080 for the last years with a custom override .plist file.

With Sierra, this doesn't seem to work anymore. The OS seems to ignore the custom override. I've tried a few different resolution applications like QuickRes, SwitchResX and RDM, none of them made it possible to set the resolution of the monitor to 1920x1080 HiDPI in macOS Sierra.

This is a real dealbreaker for me, I'd downgrade if TimeMachine didn't just after upgrading decide that my backup is corrupt. I've been happy with Sierra otherwise so far, so this is incredibly annoying, to sum it up.

Also, to clarify, because this apparently confused some people: This is NOT the bug that didn't allow to choose 1440p native resolutions while connecting over HDMI, which was fixed in 10.12.1. It is a completely separate problem and deserves its own fix (by Apple, most preferably, but hey, who am I kidding).

Thanks for any helpful advice/solutions/ideas in advance!

Hi there,

I am exactly the same as you, save for the fact that I seem to have solved it.

The poster above, campyguy, helped me out with this. Of course, the concept of having HiDPI scaling work without third party hacks seemed ideal to me.

Unfortunately I didn't get it to work without hacks, but hey ho.

What I did was use the magic, actually compliant mini-full Display Port cable that he specified. It's from Accell I believe.

That didn't work off the bat, so then I downloaded the plist from a generator website you've probably heard of, made doubly sure the scaling command in Terminal was activated, installed RDM to give me access to the full resolution set and rebooted.

The result was the coveted 1080p HiDPI appearing in RDM's options. I clicked it, it worked, it hasn't stopped working even after an upgrade to the latest version of Sierra.

I'm very scared now to use any other cable or configuration. But unless anything breaks it, it looks like I am sorted, until 10.13 comes out.

 

[Miscellaneous]

You should start a new post and I will join in. Be sure to post a photo of the glitch and I will as well.
[doublepost=1474737267][/doublepost]The bottom line here, to all those defending this bug as somehow being ok, is that it's not ok. It didn't occur until Sierra and it should not be happening now. Work arounds, new cables, terminal codes, none of that should even matter. What happened to "it just works"? Obviously something changed in Sierra and it was NOT for the better of external monitor support.

Very well said! I have recently tried to upgrade to macOS Sierra again but this time to the recently released 10.12.1 update. Seems like that was a bad idea too.

I have started a new thread about this in the Mac Pro section.

https://forums.macrumors.com/threads/strange-startup-issue-since-macos-sierra-upgrade.2011875/

I've also posted in another similar thread which I will try to post a link to shortly. Like you said, something has changed in macOS Sierra and it was not in favour of external monitor support.

 

[zaxa]

zaxa, you've used a few different utilities - obviously, none of them will work as you hope. I can't get to the bottom of your issues with your display - I own a small company and there's 30+ Macs running about 50+ displays on Sierra with no issues, and I ran through the betas as they progressed. I'm going to reiterate here that I can't find one Dell-supplied cable (COXOC) that meets with DisplayPort specs; we've got about 25 Dell displays in my offices.

Also, I have used RDM, QuickRes, and SwitchResX. RDM is dead. QuickRes hasn't been updated for Sierra, so IMHO for the intent of this thread it's also dead. SwitchResX uses display-specific workarounds - hacks, really - to approximate what a display might be capable of (I've got multiple paid licenses for this nifty utility, none of which I'm using now because I don't need SRX any longer).

See my post here, #26. The OP still has issues, and moved on to follow another thread without following up. What's missing is feedback about this: "... and maybe the entire Overrides folder ...". SwitchResX creates a display-unique directory/folder in the Overrides folder that delineates the capability of each display; this display-unique directory/folder isn't needed if you're using a compliant cable. If you're using a compliant cable and a display-unique directory/folder is installed your Mac/PC and display won't be able to negotiate a proper connection - sadly, IMHO the OP never followed up.

What I can offer is that more than 4 dozen DP displays are working on my Macs without issue. All of them are running DP-compliant cables and a stock Overrides folder. None of our Macs are "new"...

Hi campyguy, thanks for your reply!

I read your post, but I am using a Lenovo miniDP-DP cable that should definitely be DP 1.2 compliant. I also never had any issues with my custom 1080p HiDPI resolution on El Capitan with the manual override, I think this is pretty important here, the OS was the only thing that changed between those setups. It should definitely be working. :/

Thank you for trying to help though, I definitely appreciate it.

Hi there,

I am exactly the same as you, save for the fact that I seem to have solved it.

The poster above, campyguy, helped me out with this. Of course, the concept of having HiDPI scaling work without third party hacks seemed ideal to me.

Unfortunately I didn't get it to work without hacks, but hey ho.

What I did was use the magic, actually compliant mini-full Display Port cable that he specified. It's from Accell I believe.

That didn't work off the bat, so then I downloaded the plist from a generator website you've probably heard of, made doubly sure the scaling command in Terminal was activated, installed RDM to give me access to the full resolution set and rebooted.

The result was the coveted 1080p HiDPI appearing in RDM's options. I clicked it, it worked, it hasn't stopped working even after an upgrade to the latest version of Sierra.

I'm very scared now to use any other cable or configuration. But unless anything breaks it, it looks like I am sorted, until 10.13 comes out.

Hi Sheza, thanks for your response!

Good thing that it now works for you, so apparently there is a way to get this working again! I might have made a mistake while installing the custom .plist, so I guess I am going to have to try this again.



In case none of this works I will buy another mDP-DP cable, but this would really be my last resort. It doesn't make any sense as it had worked perfectly fine until I updated to Sierra.


UPDATE: I MANAGED TO GET IT WORKING AGAIN! I indeed made a mistake while creating the override .plist. Custom HiDPI is working perfectly fine again. Thank you so much for your responses! I can finally use my display again!

FWIW, here is the .plist I am using now with my Dell U2515H (DisplayProductID-d06e):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>DisplayProductName</key>
        <string>Dell HiDPI U2515H</string>
        <key>DisplayProductID</key>
        <integer>53358</integer>
        <key>DisplayVendorID</key>
        <integer>4268</integer>
        <key>scale-resolutions</key>
        <array>
            <data>AAAKAAAABaAAAAABACAAAA==</data>
            <data>AAAFAAAAAtAAAAABACAAAA==</data>
            <data>AAAPAAAACHAAAAABACAAAA==</data>
            <data>AAAHgAAABDgAAAABACAAAA==</data>
            <data>AAAMgAAABwgAAAABACAAAA==</data>
            <data>AAAGQAAAA4QAAAABACAAAA==</data>
            <data>AAAKAgAABaAAAAABACAAAA==</data>
            <data>AAAFAQAAAtAAAAABACAAAA==</data>
            <data>AAAKrAAABgAAAAABACAAAA==</data>
            <data>AAAFVgAAAwAAAAABACAAAA==</data>
        </array>
    </dict>
</plist>

 

[campyguy]

Hi campyguy, thanks for your reply!

I read your post, but I am using a Lenovo miniDP-DP cable that should definitely be DP 1.2 compliant. I also never had any issues with my custom 1080p HiDPI resolution on El Capitan with the manual override, I think this is pretty important here, the OS was the only thing that changed between those setups. It should definitely be working. :/

Lenovo doesn't make its own cables, most computer manufacturers do not. Lenovo has many products on the DisplayPort.org Products portal - its cables aren't on their list. The only two manufacturers I've worked with that have supplied branded, DP compliant cables are Apple and Eizo. My Dell, HP, CableMatters cables all had that nifty "DP" symbol on them and the latter brand's own PR description states "DisplayPort 1.2 Compatible" - not compliant, but compatible. I write contracts and pick up on wordplay and spin - the former means "meeting or in accordance with rules or standards", and the latter doesn't. I'm not picking nits with you - all of my branded cables and those from CableMatters returned power over Pin 20 and continually borked my 50-odd PCs and Macs, and they're all in a landfill somewhere now. Me and my multimeter followed up on what I read over on [H]ardforum - and, only the Apple TB cables and Eizo cables didn't cause issues with my computer hardware - and they didn't return power over Pin 20, and, more importantly, my displays are properly identified by the computers they're connected to - look at my screenshots, both indicating "DELL P2715Q" - I used to have to use SwitchResX to get that to show up, now it just shows up...

Yes, something's changed in Sierra, my having noted that with two screenshots earlier in this thread (from my personal Mini Server). I've also noted that Apple may be "cracking down" on non-compliant display-related components. Also, there's a bit of additional data in those screenshots that I alluded to earlier - those additional data fields. Prior to Sierra, your utility mapped, then looked for data in a certain order - and now that data order has been changed; I'm now surmising that this change in order is bunging things up - where there used to be a "Resolution" data switch there's now a "Metal" data switch, and there's a total of two data fields that didn't exist before and your utility doesn't know what to do with those instructions. Think about it that way.

Also, IMHO those two data fields may only be conveyed over DP 1.2 compliant and/or compatible cables, which is why TB cables aren't working well or at all as DP cables as they're DP 1.1a compliant. I've read that others are having issues with TB cables when used with DP displays, and I know now that none of our TB cables work on Sierra while connected to our displays (all DP 1.2).

My nitpick is with Apple - I wish they'd publish the details of what they're doing. I'd offer find an updated haxie, ditch your existing override and create a new one, or get a compliant cable. I've got compliant cables and no display hacks on 25+ Macs, and zero issues - it works for me (and the people making coin for me!). Cheers!
[doublepost=1478286698][/doublepost]

I am exactly the same as you, save for the fact that I seem to have solved it.

The poster above, campyguy, helped me out with this.

Nifty!

 

[keviig]

Rebooting this thread!
I just got my 2016 tBMBP 13" and a Dell U2515H. Now, the monitor looks stunning at 125% scaling in Windows 10 when connected to my desktop computer. But when connected to my Mac it refuses to scale. 1440p native is just too small for me.

Has anyone come to a working solution? I'm on the edge of buying the LG UltraFine 4K monitor to not have to bother with these problems, but it's smaller, uglier and is 2x the price... Please help

 

[filmak]

Rebooting this thread!
I just got my 2016 tBMBP 13" and a Dell U2515H. Now, the monitor looks stunning at 125% scaling in Windows 10 when connected to my desktop computer. But when connected to my Mac it refuses to scale. 1440p native is just too small for me.

Has anyone come to a working solution? I'm on the edge of buying the LG UltraFine 4K monitor to not have to bother with these problems, but it's smaller, uglier and is 2x the price... Please help

So, you have selected the options in system settings -> displays and nothing?
Have you tried the scaled resolutions, while holding the option (alt) key?

 

[keviig]

So, you have selected the options in system settings -> displays and nothing?
Have you tried the scaled resolutions, while holding the option (alt) key?

Yep. When i go there i get 1440p (native) along with other, lower resolutions. None of them HiDPI. If i select a lower one like 2048x1152 i get the scaling i want, but it's all fuzzy. It's showing 2048x1152 on the 2560x1440 panel, which is a mess

 

[Sheza]

Yep. When i go there i get 1440p (native) along with other, lower resolutions. None of them HiDPI. If i select a lower one like 2048x1152 i get the scaling i want, but it's all fuzzy. It's showing 2048x1152 on the 2560x1440 panel, which is a mess

How are you connecting it?

You're describing the problem I (previously) experienced, although I have a 2014 MBP that is connected over Display Port.

Honestly mate, don't go for the 4K UltraFine, it's tiny. If you're going to do anything, go all out for the 5K. Or get yourself a 24" or 27" 4K over USB-C, they're coming out soon.

 

[keviig]

How are you connecting it?

You're describing the problem I (previously) experienced, although I have a 2014 MBP that is connected over Display Port.

Honestly mate, don't go for the 4K UltraFine, it's tiny. If you're going to do anything, go all out for the 5K. Or get yourself a 24" or 27" 4K over USB-C, they're coming out soon.

Im connecting it via Apple Multiport AV and a HDMI cable.
Yeah I've decided against the 4k Ultrafine. If only it looked nice it might have been worth it haha. The 5K one is too expensive for me. I'd get a 24" or 27" 4k monitor, but I only just got my 25" U2515H 1440p one and its so good for my use so far, would be a shame to have to sell it after only a few days.

Edit: Do you think hooking it up via DP would solve the issue? I'd need to get a USB C --> DP cable or adapter. The only ones I could find in the Norwegian stores are stupidly expensive ($50-80).

Edit 2: Why isn't Apple selling this stuff? Anyone wanting to use 4K monitors (except for the Ultrafine ones) with the new MBP's are forced to buy 3rd party cables or adapters. It would be so much easier if they released one themselves.

 

[Sheza]

Im connecting it via Apple Multiport AV and a HDMI cable.
Yeah I've decided against the 4k Ultrafine. If only it looked nice it might have been worth it haha. The 5K one is too expensive for me. I'd get a 24" or 27" 4k monitor, but I only just got my 25" U2515H 1440p one and its so good for my use so far, would be a shame to have to sell it after only a few days.

Edit: Do you think hooking it up via DP would solve the issue? I'd need to get a USB C --> DP cable or adapter. The only ones I could find in the Norwegian stores are stupidly expensive ($50-80).

Edit 2: Why isn't Apple selling this stuff? Anyone wanting to use 4K monitors (except for the Ultrafine ones) with the new MBP's are forced to buy 3rd party cables or adapters. It would be so much easier if they released one themselves.

Yeah, support for displays above 1080p over HDMI is very shady.

I couldn't get it working over Display Port until I messed stuff around an installed a third party tool, but I really don;t think HDMI works well for anything above 1080p. Are there no USB-C to Display Port cables on Amazon for closer to, say £10-20?

 

[campyguy]

Do you think hooking it up via DP would solve the issue? I'd need to get a USB C --> DP cable or adapter.

Yes; that active adapter was designed over a hear ago for a different product. Get a quality cable from a company that makes DP.org-certified products specifically for your needs - any lower-priced cables are likely to not be certified/compliant:
http://www.accellcables.com/collections/cables/products/usb-c-to-displayport-cable
https://www.startech.com/AV/usb-c-video-adapters/usb-c-displayport~CDP2DPMM1MB or https://www.startech.com/AV/usb-c-v...-over-usb-c-to-displayport-adapter~CDP2DPMM6B

I bought 4 of the Accell cables for 2 of my PC workstations that have 2 Dell P2715Q displays connected, and they work perfectly. I preferred the Accell brand over StarTech as the former tells me exactly what the throughput per channel is.

 

[keviig]

Yeah, support for displays above 1080p over HDMI is very shady.

I couldn't get it working over Display Port until I messed stuff around an installed a third party tool, but I really don;t think HDMI works well for anything above 1080p. Are there no USB-C to Display Port cables on Amazon for closer to, say £10-20?

Alright, thanks! I guess Displayport is my next attempt at finding a working solution I could look at Amazon, but usually shipping rates are horrible to Norway
[doublepost=1481315988][/doublepost]

Yes; that active adapter was designed over a hear ago for a different product. Get a quality cable from a company that makes DP.org-certified products specifically for your needs - any lower-priced cables are likely to not be certified/compliant:
http://www.accellcables.com/collections/cables/products/usb-c-to-displayport-cable
https://www.startech.com/AV/usb-c-video-adapters/usb-c-displayport~CDP2DPMM1MB or https://www.startech.com/AV/usb-c-v...-over-usb-c-to-displayport-adapter~CDP2DPMM6B

I bought 4 of the Accell cables for 2 of my PC workstations that have 2 Dell P2715Q displays connected, and they work perfectly. I preferred the Accell brand over StarTech as the former tells me exactly what the throughput per channel is.

I bought the adapter seeing as it was made by Apple, and i figured it would "just work". It does do 1440p@60hz after all, just not scaled. I guess DP cables are the way to go! Accell doesn't ship to Norway, and Startech wants... 50 EUROS?! to ship it haha. I'll look and see if any local retailers have them in stock. Thanks for the help!