Minor artifacts on characters when using custom display scaling (like 130%) #6448

@j4james commented on GitHub (Feb 15, 2020):

The new image still seems to be a jpeg, but now that I know where to look, I can definitely see what you mean about the artifacts. I wonder if it might be related to your graphics driver. I believe the old console uses GDI for rendering, while the new Windows Terminal uses DirectX, which would explain why you only see the issue in WT. That's just a wild guess though.

@j4james commented on GitHub (Feb 15, 2020): The new image still seems to be a jpeg, but now that I know where to look, I can definitely see what you mean about the artifacts. I wonder if it might be related to your graphics driver. I believe the old console uses GDI for rendering, while the new Windows Terminal uses DirectX, which would explain why you only see the issue in WT. That's just a wild guess though.

claunia commented

@vasily-codefresh commented on GitHub (Feb 15, 2020):

dxgiag sees no problems.

you can try to reproduce this by setting custom scaling on Windows at 130% and rebooting.

@vasily-codefresh commented on GitHub (Feb 15, 2020): dxgiag sees no problems. you can try to reproduce this by setting custom scaling on Windows at 130% and rebooting.

claunia commented

@DHowett-MSFT commented on GitHub (Feb 18, 2020):

I believe this is a /dupe of #4367. Agree?

@DHowett-MSFT commented on GitHub (Feb 18, 2020): I believe this is a /dupe of #4367. Agree?

claunia commented

@ghost commented on GitHub (Feb 18, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 18, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

claunia commented

@j4james commented on GitHub (Feb 18, 2020):

@DHowett-MSFT Just to be clear, it's not a problem with the character heights - there are little rendering glitches to the right of some of the letters. I don't know if that makes it different from #4367 or not.

If you zoom in, it becomes more obvious where the problems are. For example, look at the little bump on the side of the second 'o' in 'Corporation' compared to the first 'o'.

I haven't been able to reproduce it myself though.

@j4james commented on GitHub (Feb 18, 2020): @DHowett-MSFT Just to be clear, it's not a problem with the character heights - there are little rendering glitches to the right of some of the letters. I don't know if that makes it different from #4367 or not. If you zoom in, it becomes more obvious where the problems are. For example, look at the little bump on the side of the second 'o' in 'Corporation' compared to the first 'o'. ![image](https://user-images.githubusercontent.com/4181424/74771609-5a29b700-5286-11ea-876d-239aebb84c7a.png) I haven't been able to reproduce it myself though.

claunia commented

@DHowett-MSFT commented on GitHub (Feb 18, 2020):

huh

@DHowett-MSFT commented on GitHub (Feb 18, 2020): _huh_

claunia commented

@zadjii-msft commented on GitHub (Apr 10, 2020):

I definitely see a repro of this with 130% scaling, font size 9, grayscale or cleartype AA, "Fira Code" as my font. Also repros at size 9 with "Hack" and "Cascadia Code"

When it repros for me, it's happening in the following columns:

Microsoft Windows [Version 10.0.19604.1002]
(c) 2020 Microsoft Corporation. All rights reserved.
                                            
migrie@MIGRIE-SLAPTOP>oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
oooooooooooooooooooooooooooooooooooooooooooooo
      ^             ^             ^               
      7             21            35

It's not always a left-right artifact though. Sometimes it definitely does something weird in the y direction, making some parts of characters look too wide. It kinda looks like an anti-aliasing artifact

@zadjii-msft commented on GitHub (Apr 10, 2020): I definitely see a repro of this with 130% scaling, font size 9, grayscale or cleartype AA, "Fira Code" as my font. Also repros at size 9 with "Hack" and "Cascadia Code" When it repros for me, it's happening in the following columns: ``` Microsoft Windows [Version 10.0.19604.1002] (c) 2020 Microsoft Corporation. All rights reserved. migrie@MIGRIE-SLAPTOP>oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo oooooooooooooooooooooooooooooooooooooooooooooo ^ ^ ^ 7 21 35 ``` It's not always a left-right artifact though. Sometimes it definitely does something weird in the y direction, making some parts of characters look too wide. It kinda looks like an anti-aliasing artifact

claunia commented

2026-01-31 00:39:04 +00:00

@zadjii-msft commented on GitHub (Apr 13, 2020):

Okay, I'm punting this till the next release, because it's a fairly uncommon scenario, that peculiarly doesn't repro with other DPI scalings at the standard 100%/125%/150% (etc.) scalings.

I tried creating a branch where I used a float to store our scaling and DPI. This did seem to make the problem far less prevalent, but didn't entirely resolve the issue. If you look at the above screenshot, you'll see the artifact will be visible on all characters in the column at a specific pixel distance from the left of the window. In this screenshot, it's the right side of all the "WOQ" column of characters.

If you decrease the font size, the artifact continues to occur at that specific pixel column, not that character column.

Maybe there's somewhere else in the DX renderer that we're doing more int math instead of float math?

Note that it also repros with grayscale AA:

@zadjii-msft commented on GitHub (Apr 13, 2020): Okay, I'm punting this till the next release, because it's a fairly uncommon scenario, that peculiarly doesn't repro with other DPI scalings at the standard 100%/125%/150% (etc.) scalings. ![image](https://user-images.githubusercontent.com/18356694/79134551-825c0080-7d73-11ea-8621-5e008af60087.png) I tried creating a branch where I used a `float` to store our scaling and DPI. This did seem to make the problem far less prevalent, but didn't entirely resolve the issue. If you look at the above screenshot, you'll see the artifact will be visible on all characters in the column at a specific pixel distance from the left of the window. In this screenshot, it's the right side of all the "WOQ" column of characters. If you decrease the font size, the artifact continues to occur at that specific pixel column, not that character column. Maybe there's somewhere else in the DX renderer that we're doing more `int` math instead of `float` math? Note that it also repros with grayscale AA: ![image](https://user-images.githubusercontent.com/18356694/79135151-86d4e900-7d74-11ea-907b-dbaf16cce8de.png)

claunia commented

@LinoBarreca commented on GitHub (Dec 9, 2020):

Until I had this problem i underestimated the importance of a clean font rendering. The problem is so bad on my side that I can not concentrate when using the terminal...and i swear i don't suffer from OCD. The glitches are not minor. The lines are deformed both in height and width. For sample pictures look at #8533 (sorry for the duplicate, i searched for it and i found only a bug in which they were referring to a problem with intel cards and acceleration but that wasn't my case)

@LinoBarreca commented on GitHub (Dec 9, 2020): Until I had this problem i underestimated the importance of a clean font rendering. The problem is so bad on my side that I can not concentrate when using the terminal...and i swear i don't suffer from OCD. The glitches are not minor. The lines are deformed both in height and width. For sample pictures look at #8533 (sorry for the duplicate, i searched for it and i found only a bug in which they were referring to a problem with intel cards and acceleration but that wasn't my case)

claunia commented

2026-01-31 00:39:04 +00:00

@adhadse commented on GitHub (Sep 9, 2021):

Found same issue happening on Windows Terminal window for Ubuntu at font 12, 'JetBrains Mono' on Version: 1.9.1942.0.

My screen scaling is set to 110%. Any type of anti-aliasing other than default "Grayscale" gets even worse.

Check the ticked text and compare that to usual text:

Like the two 'n' ticked in blue
The two 'i' ticked in yellow
The two '5' ticked in maroon.

@adhadse commented on GitHub (Sep 9, 2021): Found same issue happening on Windows Terminal window for Ubuntu at font 12, 'JetBrains Mono' on Version: 1.9.1942.0. My screen scaling is set to 110%. Any type of anti-aliasing other than default "Grayscale" gets even worse. Check the ticked text and compare that to usual text: - Like the two 'n' ticked in blue - The two 'i' ticked in yellow - The two '5' ticked in maroon. ![image](https://user-images.githubusercontent.com/56764399/132659991-9f3990a5-c677-4728-a8c2-b4d30439e878.png)

claunia commented

2026-01-31 00:39:04 +00:00

@kXborg commented on GitHub (Nov 4, 2021):

I don't know how you guys are closing the issue. I don't see any proper fixes.
Setting display scaling back to default 100% does improve the rendering a little but this too is not very good. Take a look at the screenshot below. Left side is of Terminal and Right side is of Default Powershell. Both are using same text and scale. Please provide fixes. The texts are not beautiful at all (in Terminal).

@kXborg commented on GitHub (Nov 4, 2021): I don't know how you guys are closing the issue. I don't see any proper fixes. Setting display scaling back to default 100% does improve the rendering a little but this too is not very good. Take a look at the screenshot below. Left side is of Terminal and Right side is of Default Powershell. Both are using same text and scale. Please provide fixes. The texts are not beautiful at all (in Terminal). ![Terminal-Powershell](https://user-images.githubusercontent.com/55614432/140271398-83eddcfd-4115-41ea-828e-d61d2dce31d5.jpg)

claunia commented

@kXborg commented on GitHub (Nov 4, 2021):

This is the zoomed view. Zooming out makes me feel like I am using a 640x480 pixel display.

@kXborg commented on GitHub (Nov 4, 2021): This is the zoomed view. Zooming out makes me feel like I am using a 640x480 pixel display.

claunia commented

@zadjii-msft commented on GitHub (Nov 4, 2021):

I don't know how you guys are closing the issue. I don't see any proper fixes.

We're not? I'm simply combining threads reporting the same issue to a single thread, for easy tracking. Custom display scaling sizes, like 130%, or 118% cause a LOT of visual artifacts, that we're using this thread to track resolving.

@kXborg From the settings you sent me in #11679, you have text antialiasing turned off:

{
    "altGrAliasing": true,
    "antialiasingMode": "aliased",
    "colorScheme": "Campbell Powershell",
    "commandline": "powershell.exe",
    "font": 
    {
        "face": "Courier New"
    },
    "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
    "hidden": false,
    "name": "Windows PowerShell"
},

Getting rid of the "antialiasingMode": "aliased", will probably help you.

@zadjii-msft commented on GitHub (Nov 4, 2021): > I don't know how you guys are closing the issue. I don't see any proper fixes. We're not? I'm simply combining threads reporting the same issue to a single thread, for easy tracking. Custom display scaling sizes, like 130%, or 118% cause a LOT of visual artifacts, that we're using this thread to track resolving. @kXborg From the settings you sent me in #11679, you have text antialiasing turned off: ```json { "altGrAliasing": true, "antialiasingMode": "aliased", "colorScheme": "Campbell Powershell", "commandline": "powershell.exe", "font": { "face": "Courier New" }, "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "hidden": false, "name": "Windows PowerShell" }, ``` Getting rid of the `"antialiasingMode": "aliased",` will probably help you.

claunia commented

@kXborg commented on GitHub (Nov 5, 2021):

@zadjii-msft,
Hi, it fixed the issue. Thanks a lot, Mike

@kXborg commented on GitHub (Nov 5, 2021): @zadjii-msft, <br> Hi, it fixed the issue. Thanks a lot, Mike

claunia commented