Dummy resoltuion intervals should be tweaked a bit to include more common resolution options

[alessionossa]

A few months ago I was using BetterDummy to create a virtual display with resolution set to 1680x1050 to get "native resolution" when using Apple's Screen Sharing on my MBP 15" (2016) to connect to my remote Mac (see https://apple.stackexchange.com/a/392044 to understand why this is the resolution of MBP 15").
Today I installed BetterDummy on a new Mac but I noticed that the resolutions for 16:10 aspect ratio only jump by 20 on the vertical axis, missing 1050.

[waydabber]

Hi there,

are you sure? I just created a 16:10 dummy and the resolution seems to be there. How did you create the dummy? Manually or selected the corresponding menu option?

[alessionossa]

I created the dummy by selecting the option from the menu, and as you can see, the resolution is not present in my list (also if I use the slider, I cannot select that resolution). I am running version 1.1.24 Build 6909.

[waydabber]

Yes, I clearly see that. If you directly create a 1680x1050 dummy (by entering these values to the Custom Aspect Ratio option in the Create New Dummy submenu), is the dummy properly created and do you have an 1680x1050 in the resolution list?

What model is the new Mac?

Thank you!

[alessionossa]

That's the result following the steps you suggested:

I am using a MacBook Pro (15-inch, 2018) running macOS 12.4 (21F79).

[waydabber]

That should be right.

I think the issue is that the app is creating the resolutions by an increment of 20 (which should mean increment of 10 for HIDPI resolutions). But on Intel if a HiDPI resolution does not have a corresponding "low res" option, it is not shown in the resolution list while on M1 it does show.

I did indeed change in the past how the resolution intervals are calculated, I might need to tweak that a little.

[waydabber]

Hi @alessionossa - unfortunately anyhow I look at this it I either hardwire this specific resolution to be available (which is not nice), decrease the max. possible range (as with doubled steps the system could not handle the amount of resolution options) or just leave things as it is. I am leaning to the last option. The issue affects Intel only and there is a workaround for that as a custom dummy can be easily specified for the exact specifications. Sorry about this but this seems to be the least problematic solution, albeit a compromise.

Thank you for your understanding!

I'll convert this into a discussion for future reference.