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

Rendering bugs when NVIDIA ShadowPlay is enabled #14874

New Issue
Closed
opened 2026-01-31 04:21:53 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:21:53 +00:00
Owner
Copy Link

Originally created by @bnb on GitHub (Aug 16, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

Nvidia GeForce Experience 3.23.0.74

Steps to reproduce

  • Open Terminal
  • Run a few commands to make the window scroll any amount
  • Old ShadowPlay UI rendering is attached to where it rendered

Examples:
image

image

Expected Behavior

  • ShadowPlay UI shouldn't be rendered a bunch of times

Actual Behavior

  • ShaodwPlay UI is rendered a bunch of times.
Originally created by @bnb on GitHub (Aug 16, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software Nvidia GeForce Experience 3.23.0.74 ### Steps to reproduce - Open Terminal - Run a few commands to make the window scroll any amount - Old ShadowPlay UI rendering is attached to where it rendered Examples: ![image](https://user-images.githubusercontent.com/502396/129592134-a6110122-7507-4c1a-bc40-2a67baa83603.png) ![image](https://user-images.githubusercontent.com/502396/129592148-6172cc0f-4014-4fa7-8e56-8ec5d2231060.png) ### Expected Behavior - ShadowPlay UI shouldn't be rendered a bunch of times ### Actual Behavior - ShaodwPlay UI is rendered a bunch of times.
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 04:21:53 +00:00
claunia commented 2026-01-31 04:21:55 +00:00
Author
Owner
Copy Link

@bnb commented on GitHub (Aug 16, 2021):

I don't totally believe this is a problem that is sqaurely on the Terminal team's shoulders, but if you use Nvidia GeForce Experience - which is how Nvidia manages their driver updates for their GPUs - this will be enabled by default and thus will be something a lot of users who have an Nvidia GPU experience.

@bnb commented on GitHub (Aug 16, 2021): I don't totally believe this is a problem that is sqaurely on the Terminal team's shoulders, but if you use Nvidia GeForce Experience - which is how Nvidia manages their driver updates for their GPUs - this will be enabled by default and thus will be something a lot of users who have an Nvidia GPU experience.
claunia commented 2026-01-31 04:21:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 16, 2021):

Probably best filed with the WinUI folks since the UI is inherited by them.

That's pretty unlikely - I'd reckon that the element of the Terminal that this Nvidia UI is attaching to is probably our SwapChainPanel, and we're responsible for rendering the content of that. However, nvidia's software does seem to have an immense amount of difficulty with the Terminal (#649, reddit thread).

I'd recommend reporting this upstream at wherever nvidia bugs go. They're definitely doing something weird in how they try to determine what is or isn't a game.

@zadjii-msft commented on GitHub (Aug 16, 2021): > Probably best filed with the WinUI folks since the UI is inherited by them. That's pretty unlikely - I'd reckon that the element of the Terminal that this Nvidia UI is attaching to is probably our SwapChainPanel, and we're responsible for rendering the content of that. However, nvidia's software does seem to have an immense amount of difficulty with the Terminal (#649, [reddit thread](https://www.reddit.com/r/techsupport/comments/lwqwrj/geforce_experience_detecting_applications_as_games/)). I'd recommend reporting this upstream at _wherever nvidia bugs go_. They're definitely doing something weird in how they try to determine what is or isn't a game.
claunia commented 2026-01-31 04:21:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 26, 2022):

I'm closing this out on our side. If Nvidia wants to come back and tell us what we can do to opt out of this, I'm all for it. At the time though, this seems like something they'll need to fix on their end.

(feel free to continue discussion of workarounds below)

@zadjii-msft commented on GitHub (Jul 26, 2022): I'm closing this out on our side. If Nvidia wants to come back and tell us what we can do to opt out of this, I'm all for it. At the time though, this seems like something they'll need to fix on their end. (feel free to continue discussion of workarounds below)
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 Needs-Tag-Fix Needs-Triage 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#14874
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?