M1 Pro is performing better than M3 Max

[etrippler]

I have two laptops, an M1 MBP (base model) and an M3 Max. I'm trying to use them with a 4K 144Hz monitor w/ Sequoia. I'm pretty familiar with all the posts on this topic - I get that the limitations are Apple-derived and there is not much to be done. However I am very surprised that my M1 Pro seems to get "better" resolutions/refresh rates at HiDPI than the M3 Max.

• The M1 MBP can go as high as 3584x2016 at 110Hz while on HiDPI
• The M3 Max can go as high as 3456x1944 at 95Hz while on HiDPI.

What is going on here? I was under the impression that the newer laptop should have less limitations, not more. As far as I can tell the EDID and settings being applied on both are totally identical - with the exception that the M3 Max is on 15.1 and the M1 MBP is 15.0.1 Did Apple introduce yet more limitations on 15.1?

[etrippler]

Actually upon further inspection, this may be some variation of this bug: #3489

If I look at unexposed refresh rates, 144hz is available to the M3 Max. Selecting it seems to work at native resolution without issue, but the Display Modes menu reports it incorrectly as being at 60hz. I also have to select 144Hz each time it connects.

I'm on Version 3.1.2 Build 34662

[waydabber]

If the resolution/refresh rate is not listed in the Display Mode section using Show All (under Filter), then it's not a bug - macOS does not expose that resolution as standard mode list and should not be available in System Settings either. The unexposed refresh rate solution to make high refresh rates working is actually a hack to get around some of the system limitations now in place.

[etrippler]

You're right, it's not available in System Settings, which also shows the refresh rate as 60hz. Would it be possible to persist the unexposed refresh rate across sleep/disconnect? I don't mind the incorrect readout, the only real issue is constantly having to select it.

[etrippler]

I should add, Configuration Protection doesn't seem to work here, even if I enable it while on 3840x2160 144Hz HiDPI, when I reconnect it either flips to 3840x2160 60Hz HiDPI or 3840x2160 144Hz LoDPI (depending on which settings I tried to protect).

[waydabber]

I see. Yes, because the mode is not in the normal mode list but there is something similar to it, the app might be choosing a different protected resolution. I might need to tweak this a little.