You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using monospace xenon on my main monitor in vscode (21:9, 1440p, 1,25 scaling in windows settings), some characters like the 'n' look weird and the text itself looks very "wobbly". This does not happen on my second monitor (16:9, 1080p, standard scaling) and seems to resolve when increasing the font weight.
Main monitor, font weight standard:
Main monitor, font weight 600:
Second monitor, font weight standard:
Display Settings:
Does anyone know why this happens and would know how to fix it?
The text was updated successfully, but these errors were encountered:
Hmm, an important information bit would be which font you use. The variable ttf or the static otf.
Usually such problems are hinting/subpixel rendering/antialiasing problems.
Do you have the problems on Gentoo or on Windows?
The windows font rendering antialiasing wise is ... I do not understand it to not say 'is broken'.
Depending on ttf or otf one could use for example VTT to rehint the font. Not that I ever autohinted a variable font with that tool.
Another issue comes to my mind, did you turn off all the 'optimization' settings in your display's hardware menu? Like 'movie mode' or 'desktop mode' or 'sharpen' or such thing. Usually they destroy any antialiasing and make the font look extremely bad.
But you can spot that when you use a software screen magnifier and the effect is not visible magnified.
When using monospace xenon on my main monitor in vscode (21:9, 1440p, 1,25 scaling in windows settings), some characters like the 'n' look weird and the text itself looks very "wobbly". This does not happen on my second monitor (16:9, 1080p, standard scaling) and seems to resolve when increasing the font weight.
Main monitor, font weight standard:
Main monitor, font weight 600:
Second monitor, font weight standard:
Display Settings:
Does anyone know why this happens and would know how to fix it?
The text was updated successfully, but these errors were encountered: