I think am using this wrong

[krz30]

Hi and thanks for the effort

Hi have a monitor that its resolution is 3440 x 1440 am trying to the application to enable the "escale text option" after digging online i found that is because mac need to recognize the monitor with higdpi

So i downloaded the app and installed created a customer and checked highdpi rebooted and still the same did I miss something?

i tried using thunderbolt cable and thunderbolt to display port with the same results

i already have csrutil disabled, i had switchresx installed on the laptop but i decided to removed since i dint know if it could cause a conflict

[leonmz]

You cannot enable HIDPI for your native resolution(3440 1440) You need to add a new logic resolution that ideally is half of height and width(1720 720) of your physical resolution(3440 * 1440) with HIDPI checked. However this is not really useful since it make UI too big to use - in my opinion, 34 inch ultra-wide monitor: you can create a 5120x2160 option and clicked the HiDPI checkbox. Once you restarted, you should get an 2560x1071 HiDPI option in RDM

REF: https://medium.com/@happy_one/thanks-for-the-tip-john-a15393960ecd

[krz30]

I follow your comments and it created a 2560x180

but no matter how many times y click on the resolution it doesn't change

[leonmz]

Is 1720 720 useable and which GPU are you on? In order to do a proper HIDPI for 2560x1080 the GPU must be able to render pixels at 5120 2160 level.

[krz30]

s 1720 * 720 useable and which GPU are you on? Yes, Radeon Pro 560X 4 GB Intel UHD Graphics 630 1536 MB

[leonmz]

This is likely being caused by https://github.com/usr-sse2/RDM/issues/15. I have running into the same issue of yours after install the newest version. You can try to patch the newest PR: https://github.com/usr-sse2/RDM/pull/19 to get it working. You will need to have a XCode running.

[corentinleberre]

Hello guys! I am facing same issues than krz30 (I have a LG35 3440x1440). I cloned the repo and compile the newest pre-release. I create custom HiDPI resolution, then reboot. Despite all of that it's not working... Any idea? :/

[leonmz]

I guess you already resolved the saving issues. If you have not, you can get it writeable via sudo mount -uw/ killall Finder I can work without issues in newest OS version with SIP enabled after saving.

[krz30]

i really didnt know how to compile it but i tried

sudo mount -uw/ killall Finder

and click the desired resolution but still dint work :(

[corentinleberre]

@krz30 if you want to compile the PR you have to clone the repo with git and then compile it using Xcode. (You can use Github Desktop, if you are not familiar with git)

After that you have to exec commands below before clicking on save in RDM. sudo mount -uw/ killall Finder

Despite all of that, it dont work better, I think i will just return my 21:9 and buy a regular 16:9 ..

[krz30]

thanks for the quick explanation, it didnt work on my mac as well, i will stick with the none hpdi until i found a workaround

[jnooree]

Hello, I'm the author of #19. The PR version does not require SIP to be disabled, so mounting root directory as rw mode is not needed (after macOS 10.15). The only thing you have to do is rebooting after saving configurations. If you are in troubles, could you provide me the macOS version of your machine and the output of $ ioreg -lw0 | grep IODisplayPrefsKey? It would help me debugging. Also note that you could not enable HiDPI mode if your host machine (and/or the protocol you've used for connection) does not support 2x resolution. For instance, in the previous comment of @corentinleberre, your hardware should support 5120 2160 resolution to enable 25601080 in retina mode (as @leonmz mentioned).

Hello guys! I am facing same issues than krz30 (I have a LG35 3440x1440). I cloned the repo and compile the newest pre-release. I create custom HiDPI resolution, then reboot. Despite all of that it's not working... Any idea? :/

Also I'm curious that if the /Library directory works just the same as /System/Library for the previous macOS versions or not. I only have a 16'' MBP so I have no way to check the others...

[krz30]

Hi, this is my output, am the monitor is connected using thunderbolt 3

| |   |   | |           "IODisplayPrefsKey" = "Alias:0/AppleBacklightDisplay-610-a040"
| |   |   | |           "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/ATY,Palena@1/AMDFramebufferVIB/display0/AppleDisplay-1e6d-772b"

[jnooree]

Thanks for the info. While working on the PR I've found that some display overrides has different HiDPI flags (looks like), to the "hacked" values the app is currently using. Well, but this time, I don't see any default overrides in my mac. It seems that it would not the case then (maybe?).

Next step: could you provide me the contents of the files, namely:

• /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b
• /Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b

The two files only differ in the root directory (/System). Ignore non-existent files.

[krz30]

/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b

systemlibrary.txt

this one /Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b

doesn't exists

[krz30]

also maybe important to mention i previously used

https://github.com/xzhih/one-key-hidpi

[jnooree]

also maybe important to mention i previously used

https://github.com/xzhih/one-key-hidpi

Indeed. These fake-hidpi tools all use the overrides folder, so it could have contaminated your plist file. (Side note: I also have used it before, but it didn't work well with me either ToT)

/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b

systemlibrary.txt

this one /Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b

doesn't exists

Thanks very much. OK, I think the value is wrong for this time: the <scale-resolutions> should be AAAUAAAACHAAAAABACAAAA==, according to my build. Could you just erase the file (in the /System/Library) and save the resolution again with the PR version? I also included the install script, so you actually do not need to 'open' xcode (but it should be installed). Also, could you notice me the macOS version and SIP status?

[krz30]

hi, deleted the file, this erased the resolutions, i recreated the resolution reboot the machine and if i click the resolution didnt change

osx 10.15.6 System Integrity Protection status: disabled.

i didnt saw the script

[jnooree]

You should clone my forked repo: jnooree/RDM@b6935468139b8a62c73ec822d2d5b60cc2cb47d9 (UPDATE 09/13). Also note that you have to checkout to with-sip branch. The install and uninstall script will then appear in the project root directory.

[krz30]

its funny the built in display can reach the desired resolution on hpi but the external cant, but i can have a resolution twice,

any who, i tried the install and the behaviour :(

maybe something with the monitor i dont know

[jnooree]

Sorry for your inconvenience, but too little information to make any decision. Just to make sure, could you check the /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b file and the contents of it once more? I think some kind of logging mechanism should be added to this app for debugging. Maybe I can implement it, but it would take time.

[usr-sse2]

Thanks for the info. While working on the PR I've found that some display overrides has different HiDPI flags (looks like), to the "hacked" values the app is currently using.

Well, but this time, I don't see any default overrides in my mac. It seems that it would not the case then (maybe?).

Next step: could you provide me the contents of the files, namely:

• /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b

• /Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-772b

The two files only differ in the root directory (/System). Ignore non-existent files.

Actually the new values from one-key-hidpi are right (they enable the new preferences), but one-key-hidpi is doing too many unnecessary things. Currently I'm using one-key-hidpi but with some parts of code removed. I plan to implement it properly in RDM 2.5.

[jnooree]

Actually the new values from one-key-hidpi are right (they enable the new preferences), but one-key-hidpi is doing too many unnecessary things. Currently I'm using one-key-hidpi but with some parts of code removed. I plan to implement it properly in RDM 2.5.

That's interesting, I tried it once before but didn't work well. Maybe it was just my mistake or something.