-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command "set" not working on latest MacBook Pro 16" #32
Comments
same here.
I forgot how I set to 3072x1920 back when I bought this mac 😩 |
For for those you have the same issue: in the meantime you can use the GUI application RDM https://github.com/avibrazil/RDM |
Same, but not on a MacBook. I have an ultrawide Samsung split into two monitors. List shows options correctly, and when I select the current resolution it dumps out the same error as mentioned above. |
This tool looks awesome! https://apple.stackexchange.com/a/450370/53510 led me here. I'll be so excited if we can get this working. Unfortunately on my 16" MacBook Pro, this happens:
I have a 42.5" Dell display plugged in via USB-C. I don't need the built-in Mac display to be turned on (although it's fine if it is, as long as it's identical to my main external display). I wonder if the difference in precision between |
I also get an error when trying to set the resolution of the built in liquid retina xdr display that supports 120 hz. The command does work to update the resolutions of my external monitors though.
That was the default resolution. When I tried setting it to a resolution from the |
Thanks for your comment. Yeah, I'm still not sure what's wrong with mine:
|
The issue is the float compare, this works around it, but maybe better to check if the floats are "close enough" to each other?
|
Yeah, these are the real numbers coming back from the OS:
|
On latest MacBook Pro 16" (running Catalina)
list
works fine but runningset
with any of the available resolutions doesn't have any effect. Any ideas what the issues could be or how this could be fixed?The text was updated successfully, but these errors were encountered: