Inconsistent rendering of characters #18690

Closed
opened 2026-01-31 06:21:26 +00:00 by claunia · 6 comments
Owner

Originally created by @edemaine on GitHub (Oct 15, 2022).

Windows Terminal version

1.15.2713.0

Windows build number

10.0.22000.1098

Other Software

Cygwin vim 8.2
zsh 5.8

Steps to reproduce

Type in some text such as console.log 'hello', palette in vim or zsh

Possible relevant:

  • System / Display / Custom scaling of 135%
  • 3840x2160 monitor
  • Font is Hack FC Ligatured at 14pt. Also tried a more vanilla Hack with similar effects.
  • Text antialiasing set to ClearType. (Also tried Grayscale with similar effects.)
  • No apparent difference with "Redraw entire screen" or "Use software rendering" turned on.

Expected Behavior

Identical characters to look similar

Actual Behavior

Some strokes look thicker than they should, with possible overdraw.

In Vim: look at weird s and different os

image

In zsh: look at different hs and ls

image

Originally created by @edemaine on GitHub (Oct 15, 2022). ### Windows Terminal version 1.15.2713.0 ### Windows build number 10.0.22000.1098 ### Other Software Cygwin vim 8.2 zsh 5.8 ### Steps to reproduce Type in some text such as `console.log 'hello', palette` in vim or zsh Possible relevant: * System / Display / Custom scaling of 135% * 3840x2160 monitor * Font is [Hack FC Ligatured](https://github.com/gaplo917/Ligatured-Hack) at 14pt. Also tried a more vanilla Hack with similar effects. * Text antialiasing set to ClearType. (Also tried Grayscale with similar effects.) * No apparent difference with "Redraw entire screen" or "Use software rendering" turned on. ### Expected Behavior Identical characters to look similar ### Actual Behavior Some strokes look thicker than they should, with possible overdraw. In Vim: look at weird `s` and different `o`s ![image](https://user-images.githubusercontent.com/2218736/195997823-9a6470f4-d64a-43d9-9f40-9a4a1b18fea0.png) In zsh: look at different `h`s and `l`s ![image](https://user-images.githubusercontent.com/2218736/195997844-1b69cac8-e6d7-4743-8bda-de30d8ba9589.png)
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:21:26 +00:00
Author
Owner

@lhecker commented on GitHub (Oct 17, 2022):

Do you have the "AtlasEngine" feature enabled under the "Rendering" settings? Could you try toggling the switch and restarting Windows Terminal to see how the other rendering mode works for you?

@lhecker commented on GitHub (Oct 17, 2022): Do you have the "AtlasEngine" feature enabled under the "Rendering" settings? Could you try toggling the switch and restarting Windows Terminal to see how the other rendering mode works for you?
Author
Owner

@zadjii commented on GitHub (Oct 17, 2022):

This is #4591

@zadjii commented on GitHub (Oct 17, 2022): This is #4591
Author
Owner

@edemaine commented on GitHub (Oct 17, 2022):

Agreed, @zadjii, this seems like the same as #4591. Thanks for spotting. (I did try to look for scaling issues, but missed this one.)

@lhecker I don't see an AtlasEngine option. Is it one of the following?

image

@edemaine commented on GitHub (Oct 17, 2022): Agreed, @zadjii, this seems like the same as #4591. Thanks for spotting. (I did try to look for scaling issues, but missed this one.) @lhecker I don't see an AtlasEngine option. Is it one of the following? ![image](https://user-images.githubusercontent.com/2218736/196210776-f5bfc5c0-0808-4c1f-8544-8e9f96717a0a.png)
Author
Owner

@lhecker commented on GitHub (Oct 17, 2022):

Ah sorry, I thought we had merged that into the 1.15 release branch as well. If you install Windows Terminal Preview (1.16) the issue will most likely not occur anymore.

@lhecker commented on GitHub (Oct 17, 2022): Ah sorry, I thought we had merged that into the 1.15 release branch as well. If you install Windows Terminal Preview (1.16) the issue will most likely not occur anymore.
Author
Owner

@edemaine commented on GitHub (Oct 17, 2022):

Oh, thanks. On 1.16.2642.0 with Atlas turned on (as is the default), I see a different issue:

image

Both lines should be identical, but the top one has weird rendering. Moving lines up and down consistently misdraws the top line (whichever one is in the second row of the window).

Perhaps clearer with antialiasing turned off:

image

I assume this is also #4591, or should I open a different issue?

@edemaine commented on GitHub (Oct 17, 2022): Oh, thanks. On 1.16.2642.0 with Atlas turned on (as is the default), I see a different issue: ![image](https://user-images.githubusercontent.com/2218736/196234851-f16a7d13-d428-45e0-8506-0b4b23ad6248.png) Both lines should be identical, but the top one has weird rendering. Moving lines up and down consistently misdraws the top line (whichever one is in the second row of the window). Perhaps clearer with antialiasing turned off: ![image](https://user-images.githubusercontent.com/2218736/196235375-c648a55c-8883-40ff-a088-1f8c2600665a.png) I assume this is also #4591, or should I open a different issue?
Author
Owner

@lhecker commented on GitHub (Oct 17, 2022):

Interesting! I'd say it's the same issue even if it behaves slightly different. I suspect this is a bug in Direct2D which we can't do that much about just yet as we depend heavily on it. But I'll have to look into it first...

@lhecker commented on GitHub (Oct 17, 2022): Interesting! I'd say it's the same issue even if it behaves slightly different. I suspect this is a bug in Direct2D which we can't do _that_ much about just yet as we depend heavily on it. But I'll have to look into it first...
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18690