Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Screen flicker after any input with new renderer enabled #13173

Closed
ChrHorn opened this issue May 25, 2022 · 4 comments
Closed

Screen flicker after any input with new renderer enabled #13173

ChrHorn opened this issue May 25, 2022 · 4 comments
Labels
Area-AtlasEngine Help Wanted We encourage anyone to jump in on these. Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Priority-2 A description (P2) Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.

Comments

@ChrHorn
Copy link

ChrHorn commented May 25, 2022 •
edited
Loading

Windows Terminal version

1.14.1432.0

Windows build number

10.0.19043.0

Other Software

GPU: Intel® HD Graphics 520 (Driver Version: 30.0.101.1340)

Steps to reproduce

  1. Enable experimental text rendering engine
  2. Disable acrylic material
  3. Choose Campbell colorscheme
  4. Place the terminal windows in front of a dark background
  5. Observe delayed flickering after typing a character

Expected Behavior

No flickering

Actual Behavior

This might be related to #4528 but is also a bit different.

I only have this issue with the new renderer and disabled acrylic material. Enabling acrylic, even with the slider set to 100, fixes the issue.

The flickering is only visible with certain scheme/background combinations.
@ChrHorn ChrHorn added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 25, 2022
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 25, 2022
@zadjii-msft zadjii-msft added Help Wanted We encourage anyone to jump in on these. Product-Terminal The new Windows Terminal. Priority-2 A description (P2) Area-AtlasEngine labels May 25, 2022
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label May 25, 2022
@zadjii-msft zadjii-msft added this to the 22H2 milestone May 25, 2022
@zadjii-msft zadjii-msft modified the milestones: 22H2, Terminal v1.17 Aug 19, 2022
@zadjii-msft zadjii-msft removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Aug 19, 2022
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Aug 19, 2022
@thoellrich
Copy link

I'm seeing exactly the same behavior: with AtlasEngine enabled, there is a some serious flickering. Disabling AtlasEngine fixes the problem.

Windows Terminal Version: 1.16.2524.0

Edition Windows 11 Pro
Version 21H2
OS build 22000.978
Experience Windows Feature Experience Pack 1000.22000.978.0

@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jan 11, 2023
@lhecker
Copy link
Member

lhecker commented Apr 12, 2023 •
edited
Loading

I get the feeling that this is an MPO bug in the driver, but we'll see if #14959 fixes this, because it handles swap chains a bit differently. Edit: If you could record a video of this happening, it would be super helpful for us!

@zadjii-msft
Copy link
Member

@ChrHorn We think this should be fixed with the version of the renderer in Terminal Preview 1.18. Can you confirm if that's fixed it/?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jul 5, 2023
@zadjii-msft zadjii-msft added the Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. label Jul 5, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Jul 5, 2023
@microsoft-github-policy-service
Copy link
Contributor

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.

@microsoft-github-policy-service microsoft-github-policy-service bot removed this from the Terminal v1.18 milestone Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-AtlasEngine Help Wanted We encourage anyone to jump in on these. Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Priority-2 A description (P2) Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lhecker @thoellrich @carlos-zamora @ChrHorn @zadjii-msft