Contribute
Register

Adding/Using HiDPI custom resolutions

Status
Not open for further replies.
It was just the wrong way to say: yes, the file got copied without the extension via sudo command.

Anyway, no success, unfortunately. What am I doing wrong? DVMT limit maybe?

View attachment 233027

View attachment 233028

Check that you installed it to the correct directory (depends on version), correct file name...
It is not something I can double check for you.
 
I have an apple Cinema Display, 2560x1440. I first tried to just enable hiDPI in its native resolution but when I switch to it, it doesn't seem to make anything look different. I then went down a notch to 2048x1152 and enabled a hiDPI setting for that resolution. it definitely makes things look better and smoother - am I correct in assuming that you need to be running in a lower resolution than your native for this do have any effect? Not sure if I will leave it like this since I miss the extra screen space.
 
I have an apple Cinema Display, 2560x1440. I first tried to just enable hiDPI in its native resolution but when I switch to it, it doesn't seem to make anything look different.

Why would you expect anything different? Native res is native res.

I then went down a notch to 2048x1152 and enabled a hiDPI setting for that resolution. it definitely makes things look better and smoother - am I correct in assuming that you need to be running in a lower resolution than your native for this do have any effect?

Yes, of course.
 
I guess I was hoping it would magically make things look better in native Rez lol!
 
eh, ill try it in 2048x1152 for now. it does make the screen look more retina like.
 
Gosh.
I find myself somehow unable to make it work.
I have a 1920x1080 internal panel.
I want 1600x900 HiDpi, so I created a plist with 1600x900 and 3200x1800, both with HiDpi flags.
Properly installed, checked file ownership, checked Product and Vendor ID, but I cannot see the new resolutions even with switchresX.
So I managed to create a custom resolution with SwitchResX and I was able to switch to Hi-Dpi scaled 1600x900, but the system always hangs up seconds after I choose that resolution.

=> My laptop has DVMT limited to 64MB. Could this be the cause? Maybe the system hides resolutions that can't handle with that DVMT, and forcing them causes KP. Am I wrong?

View attachment 233020

View attachment 233020

View attachment 233021 View attachment 233022

Thank you.

Check that the connector-type in ioreg matches DP <00 04 00 00>.

Maybe change connectFlags to 00 04 00 00 ?

don't work for me too bozma88

my ioreg
| | | | | +-o AppleBacklightDisplay <class AppleBacklightDisplay, id 0x1000003f1, registered, matched, active, busy 0 (0 ms), retain 9>

| | | | | {

| | | | | "IOClass" = "AppleBacklightDisplay"

| | | | | "CFBundleIdentifier" = "com.apple.iokit.IOGraphicsFamily"

| | | | | "IOProviderClass" = "IODisplayConnect"

| | | | | "DisplayProductID" = 1096

| | | | | "IODisplayEDID" = <00ffffffffffff0030e44804000000000017010495231378ea9e95a258559f260d5054000000010101010101010101010101010101012e3680a070381$

| | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/GFX0@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-$

| | | | | "IODisplayParameters" = {"commit"={"reg"=0},"fade-time2"={"min"=0,"max"=10000,"value"=4000},"ggsc"={"min"=0,"max"=65536,"value"=65536},"gsc $

| | | | | "IOProbeScore" = 3000

| | | | | "IOPowerManagement" = {"DevicePowerState"=3,"CapabilityFlags"=49152,"CurrentPowerState"=3,"MaxPowerState"=3}

| | | | | "IOMatchCategory" = "IODefaultMatchCategory"

| | | | | "IODisplayAttributes" = {"IODisplayAttributes"=<676174760000000073676c6600000000726c6f630100000063706220010000006364670080808000676c66640000$

| | | | | "IODisplayConnectFlags" = <00080000>

| | | | | "DisplayVendorID" = 12516

| | | | | "DisplaySerialNumber" = 0

| | | | | }
 
Last edited:
Maybe change connectFlags to 00 04 00 00 ?

don't work for me too bozma88

my ioreg
| | | | | +-o AppleBacklightDisplay <class AppleBacklightDisplay, id 0x1000003f1, registered, matched, active, busy 0 (0 ms), retain 9>

| | | | | {

| | | | | "IOClass" = "AppleBacklightDisplay"

| | | | | "CFBundleIdentifier" = "com.apple.iokit.IOGraphicsFamily"

| | | | | "IOProviderClass" = "IODisplayConnect"

| | | | | "DisplayProductID" = 1096

| | | | | "IODisplayEDID" = <00ffffffffffff0030e44804000000000017010495231378ea9e95a258559f260d5054000000010101010101010101010101010101012e3680a070381$

| | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/GFX0@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-$

| | | | | "IODisplayParameters" = {"commit"={"reg"=0},"fade-time2"={"min"=0,"max"=10000,"value"=4000},"ggsc"={"min"=0,"max"=65536,"value"=65536},"gsc $

| | | | | "IOProbeScore" = 3000

| | | | | "IOPowerManagement" = {"DevicePowerState"=3,"CapabilityFlags"=49152,"CurrentPowerState"=3,"MaxPowerState"=3}

| | | | | "IOMatchCategory" = "IODefaultMatchCategory"

| | | | | "IODisplayAttributes" = {"IODisplayAttributes"=<676174760000000073676c6600000000726c6f630100000063706220010000006364670080808000676c66640000$

| | | | | "IODisplayConnectFlags" = <00080000>

| | | | | "DisplayVendorID" = 12516

| | | | | "DisplaySerialNumber" = 0

| | | | | }

In my case the error was trivial, it was a mismatch in the path (wrong dir name).
 
Hello, i'm going mad...:(

Basically let's say i have a 4k TV and Sierra let's me use 4k 60hz fine. The problem is that i don't have any hidpi resolutions above 1920 x 1080. Since 4k makes things very small i just want the next resolution scaled which should be 3008 x 1692. I made a custom .plist as #1 with 1 non hidpi resolution of 3008 x 1692 and one resolution hidpi as 6016 x 3384 -> reboot. Now 3008 x 1692 shows as hidpi but it's not 3840 x 2160 scaled to 3008 x 1692 it's 1920 x 1080p scaled to 3008 x 1692, why on earth is doing this? And this applies to every resolution i add like 2560 x 1440. It drives me crazy...am i doing something wrong?

Sierra sees the tv to have a native 1080p(not hidpi) resolution, maybe that's why it tries to scale everything from 1080p and not 3840? It's connected via DP by hdmi-dpi active adapter but still seen as TV.

Thanks!
 
Thanks for awesome guide!

I have simple question - it is possible to have 1440p (2560x1440) if my native display resolution is 3840x2160? I am tried this method - resolution does not appears (but display name is changed). And even SwitchResX custom resolution does not work (5120x2880 in scaled mode) - "Not Activated - invalid?".

I just imagine if display should be 5k then? Or it's because of GPU (integrated)? On native 3840x2160 resolution things is too small and on 2x scaled (full hd) they are too big.
 
Hello, i'm going mad...:(

Basically let's say i have a 4k TV and Sierra let's me use 4k 60hz fine. The problem is that i don't have any hidpi resolutions above 1920 x 1080. Since 4k makes things very small i just want the next resolution scaled which should be 3008 x 1692. I made a custom .plist as #1 with 1 non hidpi resolution of 3008 x 1692 and one resolution hidpi as 6016 x 3384 -> reboot. Now 3008 x 1692 shows as hidpi but it's not 3840 x 2160 scaled to 3008 x 1692 it's 1920 x 1080p scaled to 3008 x 1692, why on earth is doing this? And this applies to every resolution i add like 2560 x 1440. It drives me crazy...am i doing something wrong?

Sierra sees the tv to have a native 1080p(not hidpi) resolution, maybe that's why it tries to scale everything from 1080p and not 3840? It's connected via DP by hdmi-dpi active adapter but still seen as TV.

Thanks!

Since you added a HiDPI 3008x1692 it will be rendered at 6016x3384 and scaled down to native resolution 3840x2160, provided you added the native resolution 3840x2160 into the display override file.
 
Status
Not open for further replies.
Back
Top