Repository navigation
video resolutions #3705
Description
Steven Malis (@smalis-msft) John Starks (@jstarks)
at the moment only 1024x768 and 1280x1024 is supported.
without touching the vram we can support 640x480 ... 1920x1080,
when touching the vram we can go up to 2560x1600
i can do that - do You want :
a) not touching the vram, just add resolutions
b) touching vram also, bump up until 2560x1600
c) make a parameter how much vram we want to allocate, and make offered resolutions dependent on that ?
d) make a parameter with the max resolution, and allocate vram dependent on that ? (my preference)
if we change vram, I guess your screenshot tests will also need to be adopted.
at the curren ram prices ;-) it would be kind of cool if we´d only allocate the vram needed, not the fixed 8MB. I just hit that looking for further VNC optimisations.
just steer me, I will do the footwork
Activity
smalis-msft commentedon Jun 10, 2026
I think that adding more resolutions that can fit in the vram we already reserve is certainly a good idea. As for what to do about sizing the VRAM, that's a question for John Starks (@jstarks).
bitranox commentedon Jun 10, 2026
then lets wait for the majesty
jstarks commentedon Jun 11, 2026
Let me see what we do in Hyper-V. At one point we made VRAM configurable for some scenarios. We certainly need to stick to 8MB by default.
jstarks commentedon Jun 11, 2026
Hyper-V supports all these resolutions with the 8MB default: 640×480, 800×600, 1024×768, 1152×864, 1280×720, 1280×800,
1280×1024, 1366×768, 1440×900, 1600×900, 1600×1200, 1680×1050, 1920×1080.
We should do the same here.
Additionally, I'm OK if you want to allow opt in to a different VRAM size. Hyper-V has a min at 4MB--there is probably a good reason for this, but I don't recall the history. If you want to do this via max resolution, that seems reasonable to me.
But this should be opt in--leave 8MB as the default.