starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Disabling Video Output on High Refresh Rate Monitor #11066

New Issue
Closed
opened 2026-01-31 02:37:46 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:37:46 +00:00
Owner
Copy Link

Originally created by @cweinst1 on GitHub (Oct 18, 2020).

Environment

Microsoft Windows [Version 10.0.18363.1139]
Windows Terminal v.1.3.2651.0

Steps to reproduce

Open Windows Terminal whiile using High Refresh Rate (HRR) Monitor.
(My monitor is an Acer XF250Q, which is 1080p and 240 Hz)

I have tried turning off G-Sync Compatibility, limiting my HRR monitor's application refresh rate to < 60 Hz, and turning off other unnecessary settings in the Nvidia Control Panel, with no luck. Furthermore, I have tried switching from display port to HDMI, and switched around cables and ports.

Expected behavior

The application opens like normal and without impacting any video output.

Actual behavior

The application opens, but my HRR monitor (I am using two monitors) goes black as if disconnected. Changing the focus to another windows (whether by ALT-TABing or moving my mouse to my second monitor and clicking away) restores the output to my HRR monitor. Refocusing on WT causes my HRR monitor's display to turn black again.

Originally created by @cweinst1 on GitHub (Oct 18, 2020). # Environment Microsoft Windows [Version 10.0.18363.1139] Windows Terminal v.1.3.2651.0 # Steps to reproduce Open Windows Terminal whiile using High Refresh Rate (HRR) Monitor. (My monitor is an Acer XF250Q, which is 1080p and 240 Hz) I have tried turning off G-Sync Compatibility, limiting my HRR monitor's application refresh rate to < 60 Hz, and turning off other unnecessary settings in the Nvidia Control Panel, with no luck. Furthermore, I have tried switching from display port to HDMI, and switched around cables and ports. # Expected behavior The application opens like normal and without impacting any video output. # Actual behavior The application opens, but my HRR monitor (I am using two monitors) goes black as if disconnected. Changing the focus to another windows (whether by ALT-TABing or moving my mouse to my second monitor and clicking away) restores the output to my HRR monitor. Refocusing on WT causes my HRR monitor's display to turn black again.
claunia commented 2026-01-31 02:37:47 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 23, 2020):

What video card and driver version are you using? WT isn't doing anything it's not supposed to with its graphics pipeline, so this is rather concerning.

@DHowett commented on GitHub (Oct 23, 2020): What video card and driver version are you using? WT isn't doing anything it's not supposed to with its graphics pipeline, so this is rather concerning.
claunia commented 2026-01-31 02:37:47 +00:00
Author
Owner
Copy Link

@cweinst1 commented on GitHub (Oct 23, 2020):

What video card and driver version are you using? WT isn't doing anything it's not supposed to with its graphics pipeline, so this is rather concerning.

I have an NVIDIA 2070 with driver version 456.38.

I have experienced this exact issue before with some old games and a very old media player once, so I always thought it was a compatibility issue between the older applications and the newer NVIDIA drivers. However, this was the first time I have not been able to fix the issue by manually setting the application's FPS to 60 in the NVIDIA control panel.

@cweinst1 commented on GitHub (Oct 23, 2020): > > > What video card and driver version are you using? WT isn't doing anything it's not supposed to with its graphics pipeline, so this is rather concerning. I have an NVIDIA 2070 with driver version 456.38. I have experienced this exact issue before with some old games and a very old media player once, so I always thought it was a compatibility issue between the older applications and the newer NVIDIA drivers. However, this was the first time I have not been able to fix the issue by manually setting the application's FPS to 60 in the NVIDIA control panel.
claunia commented 2026-01-31 02:37:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 23, 2020):

I'm gonna summon @miniksa and @lhecker to this thread, since they've got a bit more experience with weird rendering edge cases, and might have a vague idea of what to investigate next

@zadjii-msft commented on GitHub (Oct 23, 2020): I'm gonna summon @miniksa and @lhecker to this thread, since they've got a bit more experience with weird rendering edge cases, and might have a vague idea of what to investigate next
claunia commented 2026-01-31 02:37:47 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 23, 2020):

@cweinst1 Do you have G-Sync for windowed applications enabled? Does your setting look like this?
image

I've had such issues before and it was caused by a too long Mini-DP cable. But you said that you swapped the cable for a HDMI one, which should rule that out... My gut feeling is that this is an issue with your particular monitor, but obviously I can't prove that.

@lhecker commented on GitHub (Oct 23, 2020): @cweinst1 Do you have G-Sync for windowed applications enabled? Does your setting look like this? ![image](https://user-images.githubusercontent.com/2256941/89332321-80f07400-d693-11ea-9434-4ae6eb6a1142.png) I've had such issues before and it was caused by a too long Mini-DP cable. But you said that you swapped the cable for a HDMI one, which should rule that out... My gut feeling is that this is an issue with your particular monitor, but obviously I can't prove that.
claunia commented 2026-01-31 02:37:48 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 27, 2020):

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 (Oct 27, 2020): 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 02:37:48 +00:00
Author
Owner
Copy Link

@cweinst1 commented on GitHub (Nov 10, 2020):

@lhecker
Sorry for the long delay, I have been busy with finals and overlooked this email.

Yes, I do have G-Sync for Windowed Applications enabled; I can disable this and see if this solves the issue.

I was worried that it was my particular monitor, though I don't have a second HRR monitor to check. Hopefully this resolves the issue. Thank you!

@cweinst1 commented on GitHub (Nov 10, 2020): @lhecker Sorry for the long delay, I have been busy with finals and overlooked this email. Yes, I do have G-Sync for Windowed Applications enabled; I can disable this and see if this solves the issue. I was worried that it was my particular monitor, though I don't have a second HRR monitor to check. Hopefully this resolves the issue. Thank you!
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 Needs-Attention Needs-Tag-Fix Needs-Triage 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#11066
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?