starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-10-01 11:22:33 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

HDR "SDR Brightness" With Multiple Monitors Can Cause Acrylic Flicker #17600

New Issue
Closed
opened 2026-01-31 05:47:20 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:47:20 +00:00
Owner
Copy Link

Originally created by @zamadatix on GitHub (May 30, 2022).

Windows Terminal version

1.14.1452.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

2 (or more) HDR monitors in "Extend" configuration bordering each other with differing "SDR content brightness" values set:

image

In my scenario I have 4 HDR displays in the following arrangement:

image

Monitors 1,3,4 are HDR with SDR brightness set to 20% while monitor 1 is HDR with SDR brightness set to 100%.

Once the monitor conditions are met make sure the Acrylic background is enabled. I haven't checked if the experimental renderer either snap the terminal window to be adjacent to monitors that have different SDR brightness values or wholesale span the WT window over multiple monitors. Now inside a single monitor move the cursor around and the WT window may flicker.

!!! Assumption Zone !!!
Suspected/Assumed cause of flicker: 1) The Acrylic effect strength seems to depend on the SDR brightness value. 2) For some reason having the WT window snapped causes it to think it's on the adjacent monitors 3) WT has some sort of race condition/selection issue with picking which monitor it is on (and therefore which SDR brightness value will be used) even though the mouse is just moving around inside of 1 monitor, sometimes not even over the WT window.
!!! Assumption Zone !!!

The easiest way for me to trigger the flicker is to snap WT to the left of monitor 2 and some other window (such as Settings) to the right of monitor 2. At this point any time I click on WT (to activate the Acrylic effect) then move my mouse to hover over Settings and back I will get flicker as it renders the Acrylic with different opaqueness (sometimes very gray, sometimes less gray).

As a note it does not matter if I use the experimental renderer or not, though the experimental renderer is enabled in this video.

Expected Behavior

No flicker to occur as the mouse is moved inside the monitor.

Actual Behavior

I have a demo video of both the effect below, it also shows how it doesn't matter what the SDR sliders are just that they not be the same across the bordering monitors at play:

https://user-images.githubusercontent.com/343550/170905952-1c10aec0-1e03-4c2c-891a-49829037fd20.mp4

Originally created by @zamadatix on GitHub (May 30, 2022). ### Windows Terminal version 1.14.1452.0 ### Windows build number 10.0.22621.0 ### Other Software _No response_ ### Steps to reproduce 2 (or more) HDR monitors in "Extend" configuration bordering each other with differing "SDR content brightness" values set: ![image](https://user-images.githubusercontent.com/343550/170904684-013f5f1d-3803-4cb7-a136-8ea15f001afe.png) In my scenario I have 4 HDR displays in the following arrangement: ![image](https://user-images.githubusercontent.com/343550/170904712-acd5cf0a-f35b-40b5-a10c-be8234e346dd.png) Monitors 1,3,4 are HDR with SDR brightness set to 20% while monitor 1 is HDR with SDR brightness set to 100%. Once the monitor conditions are met make sure the Acrylic background is enabled. I haven't checked if the experimental renderer either snap the terminal window to be adjacent to monitors that have different SDR brightness values or wholesale span the WT window over multiple monitors. Now inside a single monitor move the cursor around and the WT window may flicker. !!! Assumption Zone !!! Suspected/Assumed cause of flicker: 1) The Acrylic effect strength seems to depend on the SDR brightness value. 2) For some reason having the WT window snapped causes it to think it's on the adjacent monitors 3) WT has some sort of race condition/selection issue with picking which monitor it is on (and therefore which SDR brightness value will be used) even though the mouse is just moving around inside of 1 monitor, sometimes not even over the WT window. !!! Assumption Zone !!! The easiest way for me to trigger the flicker is to snap WT to the left of monitor 2 and some other window (such as Settings) to the right of monitor 2. At this point any time I click on WT (to activate the Acrylic effect) then move my mouse to hover over Settings and back I will get flicker as it renders the Acrylic with different opaqueness (sometimes very gray, sometimes less gray). As a note it does not matter if I use the experimental renderer or not, though the experimental renderer is enabled in this video. ### Expected Behavior No flicker to occur as the mouse is moved inside the monitor. ### Actual Behavior I have a demo video of both the effect below, it also shows how it doesn't matter what the SDR sliders are just that they not be the same across the bordering monitors at play: https://user-images.githubusercontent.com/343550/170905952-1c10aec0-1e03-4c2c-891a-49829037fd20.mp4
claunia added the Issue-BugResolution-ExternalNeeds-Tag-FixProduct-Terminal labels 2026-01-31 05:47:20 +00:00
claunia commented 2026-01-31 05:47:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 6, 2022):

Wow that looks really annoying. Does that repro with any other apps that use Acrylic? The WinUI Controls Gallery app is a good example of one that has some different acrylic surfaces.

I'm not sure how much we can do on our side with this - would you mind posting Feedback via the Feedback Hub, under "Display and Graphics > Windows HD Color (HDR and WCG)"/? If you share the link here, I can make sure it gets routed to the right folks ☺️

@zadjii-msft commented on GitHub (Jun 6, 2022): Wow that looks really annoying. Does that repro with any other apps that use Acrylic? The [WinUI Controls Gallery](https://apps.microsoft.com/store/detail/winui-2-gallery/9MSVH128X2ZT) app is a good example of one that has some different acrylic surfaces. I'm not sure how much we can do on our side with this - would you mind posting Feedback via the Feedback Hub, under "Display and Graphics > Windows HD Color (HDR and WCG)"/? If you share the link here, I can make sure it gets routed to the right folks ☺️
claunia commented 2026-01-31 05:47:21 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 10, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 10, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:47:22 +00:00
Author
Owner
Copy Link

@zamadatix commented on GitHub (Jun 10, 2022):

Hey Zadjii,

Thanks for the response! I can notice some very very slight redraw issues I think are related to this in certain apps but nothing quite as flashy. Unfortunately the Arcylic samples in the WinUI controls gallery wouldn't trigger it, I think because they didn't have layering on their examples. I wonder if there are almost 2 layers of interaction going on here, one with the root issue in Acrylic and another related to the automatic focusing and some race it has with the redraw issue.

What I'll do is start with the more base issue like you suggest since I was at least able to notice something in another app. Then once that's fixed I'll see if there is still any weird behavior left in WT or if that fixes it all. Appreciate you directing this to the right folks - feedback created as https://aka.ms/AAh5pmz

@zamadatix commented on GitHub (Jun 10, 2022): Hey Zadjii, Thanks for the response! I can notice some very very slight redraw issues I think are related to this in certain apps but nothing quite as flashy. Unfortunately the Arcylic samples in the WinUI controls gallery wouldn't trigger it, I think because they didn't have layering on their examples. I wonder if there are almost 2 layers of interaction going on here, one with the root issue in Acrylic and another related to the automatic focusing and some race it has with the redraw issue. What I'll do is start with the more base issue like you suggest since I was at least able to notice something in another app. Then once that's fixed I'll see if there is still any weird behavior left in WT or if that fixes it all. Appreciate you directing this to the right folks - feedback created as https://aka.ms/AAh5pmz
claunia commented 2026-01-31 05:47:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 14, 2022):

This got promoted internally to MSFT:39958690. Looks like they're investigating on the DWM side. I don't think there's anything else for us to be able to do here on the Terminal side of things. I've followed the internal thread for updates, I'll make sure to post here if there's anything to share.

Thanks!

/dup https://task.ms/39958690

@zadjii-msft commented on GitHub (Jun 14, 2022): This got promoted internally to MSFT:39958690. Looks like they're investigating on the DWM side. I don't think there's anything else for us to be able to do here on the Terminal side of things. I've followed the internal thread for updates, I'll make sure to post here if there's anything to share. Thanks! /dup https://task.ms/39958690
claunia commented 2026-01-31 05:47:22 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 14, 2022):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Jun 14, 2022): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
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 Issue-Bug Needs-Tag-Fix Product-Terminal Resolution-External
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#17600
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?