M1 MBP & LG 34 inch ultra wide 5K2K

[gdasilva23]

Having the same issue here with a MBP 15'' Mid 2017 (Intel SoC) and the LG Ultra Wide 34UW95U-W. I have that screen since 2019 and never have this kind of issues till now.

Resolutions got reduced a lot and the one I use to use (3840x1620) is not there anymore. Also, I made a trial on my wife's MBP 16'' and before the update everything was working right (on Monterey 12.1). Once I updated to the 12.2 the same change happens and resolutions were gone too.

Also tried using BetterDummy to force the 3840x1620 resolution but the screen gets blurry with text and icons.

All this through DisplayPort 1.2 on the screen because with 1.4 the macos get the wrong resolutions (non Ultra Wide ones).

The only solution I have right now is to use the highest possible resolution the mac is giving me: 5120x2160.

I really don't understand apple on this one.

 

[EPO75]

Ah lol now they are also reducing the Intel variants, wtf are they doing? I'm using the LG32UL950 just at the 3008x1692 which is fine, would prefer the higher variants which were available on Intel, but guess not anymore. Seems Apple only thinks there is one scalable display around, the Pro XDR screen which max is also the 3008x.

 

[nikosl7]

Incoming apple monitors?

 

[scuba_fly]

Registerd on macrumors just to share this:

TLDR;
So the LG 5K is running at full 5K ( displayed as 3849x1620 very sharp image )
The other LG is running at 4K ( connected through a usb-c hub and then displayport )
The 5k2k monitor is powering my MBP
Edit: Works on OSX 12.1 but on 12.2 the 3849x1620 option is gone!
===

I'm using the thunderbold cable from the LG 5k2k monitor plugged in direct and it worked flawless from day one on my clean installed MBP M1 Max:

Here's an other screenshot where I alt-clicked the scaled radio button so you can see the resolution:

I had a MBP 16" I7 and had some trouble getting this to work. Also connecting 2 large display's would slow down my mac. No issues with the new MBP M1 Max.

===

Had an issue today where my 5K2K monitor would not display the crisp image anymore. ( resolution was set back to 3849x1620 )
I tried rebooting, unplugging the monitors plugging them in one bye one noting worked.
Then I disconnected power of everything. Waited a minute or so. Turned the power back on and it all started working again.

I love this 5k2k monitor and I hope this helps anyone trying to decide between different monitors.
I'm also glad that other then today I had zero issues with this monitor connected to the MBP M1 Max

 

[EPO75]

Had an issue today where my 5K2K monitor would not display the crisp image anymore. ( resolution was set back to 3849x1620 )
I tried rebooting, unplugging the monitors plugging them in one bye one noting worked.
Then I disconnected power of everything. Waited a minute or so. Turned the power back on and it all started working again.

I love this 5k2k monitor and I hope this helps anyone trying to decide between different monitors.
I'm also glad that other then today I had zero issues with this monitor connected to the MBP M1 Max

But do you still have the 3840x1620 option after upgrading to 12.2 with your M1 Max as some users reporting it's gone.

 

[scuba_fly]

But do you still have the 3840x1620 option after upgrading to 12.2 with your M1 Max as some users reporting it's gone.

I updated to 12.2 and indeed missing the 3840x1620 option. A shame, because that was A nice resolution to work with this monitor. Will post here if I find a way to get it back.

 

[tardieu]

I was able to recover the scaled 3840x1620 option on my Dell U4021QW using an EDID override. The monitor is connected via Thunderbolt to my 2019 16-inch Macbook Pro running Monterey 12.2. The Display preference pane does not offer the resolution even after applying the override. However, SwitchResX does.

$ cat /Library/Displays/Contents/Resources/Overrides/DisplayVendorID-10ac/DisplayProductID-4205

<?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>DisplayProductID</key>
<integer>16901</integer>
<key>DisplayProductName</key>
<string>DELL U4021QW HiDPI</string>
<key>DisplayVendorID</key>
<integer>4268</integer>
<key>scale-resolutions</key>
<array>
<data>
AAAeAAAADKgAAAABACAAAA==
</data>
</array>
</dict>
</plist>

 

[gdasilva23]

I updated to 12.2 and indeed missing the 3840x1620 option. A shame, because that was A nice resolution to work with this monitor. Will post here if I find a way to get it back.

Yeap, that same thing happened to me. The difference is I use a MBP 2017 with Intel SoC... I'm not able to understand what Apple is doing here with those changes... doesn't have any sense.

 

[TssvMxqw]

Same here. Using a DELL U4021QW 5k2k monitor with MacBook Pro M1 Max 16-inch, and no longer had the 3840x1620 after upgrading to macOS Monterey 12.2. Here are my current scaling options. Everything worked well until this update. I tried to upgrade to 12.2 beta and the issue was still not solved.

 

[Ultron]

Apple giveth and Apple taketh away

What a frustrating situation! I haven't made a switch to a high-resolution monitor yet because of these problems, and I'm surprised Apple still doesn't have a good handle on these issues after all this time.

 

[Philstuman]

Yep, i‘ve had the same issue crop up. I filed a bug report and encourage you all to do the same! I miss that resolution…

 

[redcometdust]

I added the scaled custom resolution 7680x3240 in SwitchResX, saved and restarted computer and the resolution came back. You need paid SwitchResX for this.

14" M1 Pro and Dell U4021

 

[TssvMxqw]

I added the scaled custom resolution 7680x3240 in SwitchResX, saved and restarted computer and the resolution came back. You need paid SwitchResX for this.

14" M1 Pro and Dell U4021

Thanks! I can confirm that this method works. After adding the 7680x3240 resolution as custom resolution, it shows up in the available resolutions in SwitchResX as an HiDPI resolution and also the macOS Scaled option.

 

[Grimp]

Hey, I can confirm what TssvMxqw said, I also experienced issue after upgarding to 12.2 on MacbookPro15,1 (15 inch late 2018). My display is LG 34WK95U-W.

After upgrade, I lost 3840x1620 I used for past year, only 3360x1418 next upper step was full native 5120x2120 resolution. My display is set with DisplayPort version 1.2 and connected using direct connection with Thunderbolt cable, no hubs.

Tried BetterDummy, I was able to get 3840x1620 back but it was blurry, no hidpi. Tried to push double resolution of 3840x1620 (7680x3240) via BetterDummy didn't work.

So I tried SwitchResX (paid version), below is a process:

1) ##Disabling System Integrity Protection (SIP)

If you are running OSX 10.11 or higher, SIP must be disabled. To disable SIP do the following:

• Boot into the recovery partition by pressing CMD + R when starting up your Mac.
• Once in recovery mode, open a terminal window.
• Type the command csrutil disable
• Reboot

2) Open SwitchResX, go to "Custom Resolutions", click "+" at bottom. Select "scaled resolution" from menu. All fields shall be empty, appart the last line where you put scale to : 7680 x 3240.

3) Hit OK, and close SwitchResX, it will prompt to save config, answer yes.

4) Reboot mac one again.

5) after reboot, open SwitchResX and check custom resolution tab for your screen, this shall look like:

6) Then navigate to SwitchResX, you shall finally see 3840x1620 as HiDPI available, select it.

7) Do not forget to check "Launch SwitchResX Daemon automatically after login" in SwitchResX's General Settings.

8) Reboot again into recovery partition to disable SIP (csrutil enable).

9) After reboot, external screen shall keep 3840x1620 HiDPI resolution.

10) Looking in OSX menu, I still cannot see 3840x1620 listed:

However display use 3840x1620 correctly and is sharp!

Hope it may help you,

cheers!

 

[gdasilva23]

Yep, i‘ve had the same issue crop up. I filed a bug report and encourage you all to do the same! I miss that resolution…

I sent a report on the same day I updated to 12.2... Still waiting for somebody on support to answer back... Not having this options any more is crazy...

 

[Helmi74]

I can confirm the issue and the SwitchResX fix. Will post to feedback assistant immediately but that alreay got ignored earlier with the early M1 problems so I don't expect anything.

 

[manualCarry]

I added the scaled custom resolution 7680x3240 in SwitchResX, saved and restarted computer and the resolution came back. You need paid SwitchResX for this.

14" M1 Pro and Dell U4021

TYVM for this, this solution works for me on my 16" M1 Max and Dell u4021qw.

 

[EPO75]

That trick is not working for me on my Mac M1, I disabled SIP and added a custom resolution (3200x1800 scaled) and several other, but seems it is not working here probably as it was never supported ever in MacOS for M1? Or am I doing something wrong, anyone got it to work on a M1?

 

[satcomer]

Remember if you hold down the option key then click the display resolutions it will show many more!

 

[issepower]

34UW95U-W here. Since 12.2 also lost 3840x1620 on my MBP M1 Max 16" . Is there any sign they are bringing it back? So stupid of them ...

 

[manualCarry]

That trick is not working for me on my Mac M1, I disabled SIP and added a custom resolution (3200x1800 scaled) and several other, but seems it is not working here probably as it was never supported ever in MacOS for M1? Or am I doing something wrong, anyone got it to work on a M1?View attachment 1956615

I don't think this was ever supported on a M1 original to start with.

 

[grmlin]

Damn, I'm getting a M1 Pro in the coming months and I'm worried now. I'm currently using the display at 150% in Windows and it would suck if I couldn't do the same with a Mac :/

 

[pen-helm]

The Resolutionator guy told me he'd heard that some resolutions vanished in 12.2, but apparently have returned in the 12.3 beta.

 

[EPO75]

I don't think this was ever supported on a M1 original to start with.

Yeah true, just was hoping this trick would fool it, ah well back then to betterdummy.

 

[issepower]

Not fixed in 12.2.1 ...