starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Retro Terminal Effect looks bad with 125% screen scaling #13848

New Issue
Open
opened 2026-01-31 03:53:52 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:53:52 +00:00
Owner
Copy Link

Originally created by @jdeloshoyos on GitHub (May 19, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

No response

Steps to reproduce

The Retro Terminal Effect looks very nice with 100% screen scaling (selected in Windows Screen settings), but looks a little bit off when screen scaling is set to 125% (which is the default on my 1920*1080 laptop screen). With 100% screen scaling, the "scan lines" look evenly distributed, but they do not with 125% scaling. I'm attaching screenshots with both scaling factors in the "Expected behavior" and "Actual behavior" sections for comparison.

Expected Behavior

The expected behavior would be evenly distributed scan lines at any screen scaling setting, as seen on this screenshot at 100% scaling:
100 percent scaling

Actual Behavior

The scan lines look uneven at 125% screen scaling, as seen on this screenshot:
125 percent scaling

Originally created by @jdeloshoyos on GitHub (May 19, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software _No response_ ### Steps to reproduce The Retro Terminal Effect looks very nice with 100% screen scaling (selected in Windows Screen settings), but looks a little bit off when screen scaling is set to 125% (which is the default on my 1920*1080 laptop screen). With 100% screen scaling, the "scan lines" look evenly distributed, but they do not with 125% scaling. I'm attaching screenshots with both scaling factors in the "Expected behavior" and "Actual behavior" sections for comparison. ### Expected Behavior The expected behavior would be evenly distributed scan lines at any screen scaling setting, as seen on this screenshot at 100% scaling: ![100 percent scaling](https://user-images.githubusercontent.com/27691677/118873259-84b65580-b8b7-11eb-9b73-04473fabac2d.png) ### Actual Behavior The scan lines look uneven at 125% screen scaling, as seen on this screenshot: ![125 percent scaling](https://user-images.githubusercontent.com/27691677/118873333-a0216080-b8b7-11eb-93bf-50ff50e6e626.png)
claunia added the Help WantedArea-RenderingIssue-BugPriority-3Product-Terminal labels 2026-01-31 03:53:53 +00:00
claunia commented 2026-01-31 03:53:54 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (May 20, 2021):

Is this somewhat related to #4591?

@skyline75489 commented on GitHub (May 20, 2021): Is this somewhat related to #4591?
claunia commented 2026-01-31 03:53:54 +00:00
Author
Owner
Copy Link

@EktoHunter commented on GitHub (May 30, 2021):

Inverted text also can't be read at 125% Scaling with Retro on

image

100% does definitely look better but it's still not great aswell

@EktoHunter commented on GitHub (May 30, 2021): Inverted text also can't be read at 125% Scaling with Retro on ![](https://user-images.githubusercontent.com/23218251/120118660-f2099680-c193-11eb-989d-6ce0381410e2.png "125% Scaling") ![image](https://user-images.githubusercontent.com/23218251/120118686-1c5b5400-c194-11eb-922c-9d70ab011b89.png "100% Scaling") 100% does definitely look better but it's still not great aswell
claunia commented 2026-01-31 03:53:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 6, 2021):

I'm definitely surprised we didn't have an issue on our backlog for this. I searched for a while (though admittedly -- I did not spend the entire two months searching; I'm sorry we took so long to get back to you!).

Promoting this to a rendering bug on our backlog, and marking it "help wanted". Thanks!

@DHowett commented on GitHub (Jul 6, 2021): I'm definitely surprised we didn't have an issue on our backlog for this. I searched for a while (though admittedly -- I did not spend the entire two months searching; I'm sorry we took so long to get back to you!). Promoting this to a rendering bug on our backlog, and marking it "help wanted". Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Rendering Help Wanted Issue-Bug Priority-3 Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13848
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?