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

Retro effect not working on certain/older systems #5927

New Issue
Closed
opened 2026-01-31 00:25:34 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 00:25:34 +00:00
Owner
Copy Link

Originally created by @GrumpyDemus on GitHub (Jan 15, 2020).

Environment

Windows build number:  10.0.18362.535
Windows Terminal version (if applicable): 0.8.10091.0

DxDiag.txt
I attached the DxDiag file, because I think it has something to do with the version of windows or the graphics driver/card.
I can't update to a newer version of windows because it is not my system.

Steps to reproduce

Disclaimer: This works as intended on my personal system, so it is definitely system dependent

Try out the new retro effect: "experimental.retroTerminalEffect": true

Expected behavior

The cool retro effect should appear

Actual behavior

The retro effect does not appear

Originally created by @GrumpyDemus on GitHub (Jan 15, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362.535 Windows Terminal version (if applicable): 0.8.10091.0 ``` [DxDiag.txt](https://github.com/microsoft/terminal/files/4063844/DxDiag.txt) I attached the DxDiag file, because I think it has something to do with the version of windows or the graphics driver/card. I can't update to a newer version of windows because it is not my system. # Steps to reproduce <!-- A description of how to trigger this bug. --> **Disclaimer: This works as intended on my personal system, so it is definitely system dependent** Try out the new retro effect: `"experimental.retroTerminalEffect": true` # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The cool retro effect should appear # Actual behavior <!-- What's actually happening? --> The retro effect does not appear
claunia commented 2026-01-31 00:25:36 +00:00
Author
Owner
Copy Link

@EdgarVaguencia commented on GitHub (Jan 15, 2020):

Is required any minimum display drivers version?

The information of my drivers computer

Display Devices

Card name: Intel(R) HD Graphics
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics (Core i3)
DAC type: Internal
Display Memory: 1696 MB
Dedicated Memory: 64 MB
Shared Memory: 1632 MB
Current Mode: 1366 x 768 (32 bit) (60Hz)
Native Mode: 1366 x 768(p) (60.031Hz)
Driver Name: igdumd64.dll,igd10umd64.dll
Driver File Version: 8.15.0010.2900 (English)
Driver Version: 8.15.10.2900
DDI Version: 10
Feature Levels: 10_0,9_1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 25/11/2012 06:00:00 p. m., 8369024 bytes

@EdgarVaguencia commented on GitHub (Jan 15, 2020): Is required any minimum display drivers version? The information of my drivers computer --------------- Display Devices --------------- Card name: Intel(R) HD Graphics Manufacturer: Intel Corporation Chip type: Intel(R) HD Graphics (Core i3) DAC type: Internal Display Memory: 1696 MB Dedicated Memory: 64 MB Shared Memory: 1632 MB Current Mode: 1366 x 768 (32 bit) (60Hz) Native Mode: 1366 x 768(p) (60.031Hz) Driver Name: igdumd64.dll,igd10umd64.dll Driver File Version: 8.15.0010.2900 (English) Driver Version: 8.15.10.2900 DDI Version: 10 Feature Levels: 10_0,9_1 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 25/11/2012 06:00:00 p. m., 8369024 bytes
claunia commented 2026-01-31 00:25:36 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 16, 2020):

Hey @ironyman, do you have any idea what the requirements actually are for the retro shaders?

@DHowett-MSFT commented on GitHub (Jan 16, 2020): Hey @ironyman, do you have any idea what the requirements actually are for the retro shaders?
claunia commented 2026-01-31 00:25:36 +00:00
Author
Owner
Copy Link

@lon3wolf commented on GitHub (Jan 16, 2020):

It worked for me after I spawned a new tab, make sure to check that too. Somehow, It doesn't apply on the existing tab and requires a new tab to be opened.

@lon3wolf commented on GitHub (Jan 16, 2020): It worked for me after I spawned a new tab, make sure to check that too. Somehow, It doesn't apply on the existing tab and requires a new tab to be opened.
claunia commented 2026-01-31 00:25:36 +00:00
Author
Owner
Copy Link

@ironyman commented on GitHub (Jan 17, 2020):

I'm not sure. I know that the shader requires some version of direct3d. If the hardware supports d3d11 then the version of pixel shader we requested should be supported. Is there a way to get the output of LOG_HR_MSG or does there need to be a debugger attached?

@ironyman commented on GitHub (Jan 17, 2020): I'm not sure. I know that the shader requires some version of direct3d. If the hardware supports d3d11 then the version of pixel shader we requested should be supported. Is there a way to get the output of LOG_HR_MSG or does there need to be a debugger attached?
claunia commented 2026-01-31 00:25:36 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 17, 2020):

Alas, a debugger must be attached.

@DHowett-MSFT commented on GitHub (Jan 17, 2020): Alas, a debugger must be attached.
claunia commented 2026-01-31 00:25:36 +00:00
Author
Owner
Copy Link

@GrumpyDemus commented on GitHub (Jan 17, 2020):

It worked for me after I spawned a new tab, make sure to check that too. Somehow, It doesn't apply on the existing tab and requires a new tab to be opened.

Yes I tried that. Also restarting the terminal and rebooting the system didn't help.
I guess the graphics card is just too old. (2009)
It officially only supports up to DX10/OpenGL3 (https://www.nvidia.com/object/product_quadro_nvs_295_us.html)

So if I understood @ironyman correctly you need DX11 support for the shaders to work

@GrumpyDemus commented on GitHub (Jan 17, 2020): > It worked for me after I spawned a new tab, make sure to check that too. Somehow, It doesn't apply on the existing tab and requires a new tab to be opened. Yes I tried that. Also restarting the terminal and rebooting the system didn't help. I guess the graphics card is just too old. (2009) It officially only supports up to DX10/OpenGL3 (https://www.nvidia.com/object/product_quadro_nvs_295_us.html) So if I understood @ironyman correctly you need DX11 support for the shaders to work
claunia commented 2026-01-31 00:25:37 +00:00
Author
Owner
Copy Link

@ironyman commented on GitHub (Jan 17, 2020):

So if I understood @ironyman correctly you need DX11 support for the shaders to work

Yes. Mainly because I randomly picked shader model 5 (ps_5_0 and vs_5_0) and that requires d3d11.

https://docs.microsoft.com/en-us/windows/win32/direct3dhlsl/specifying-compiler-targets

We can try to change the shaders to target shader model 4. It should just be a matter of changing the target in shader compile call because I don't think we're using any shader model 5 features. That should let us support d3d10 machines.

It's weird that dxdiag thinks directx 12 is supported?

@ironyman commented on GitHub (Jan 17, 2020): > So if I understood @ironyman correctly you need DX11 support for the shaders to work Yes. Mainly because I randomly picked shader model 5 (ps_5_0 and vs_5_0) and that requires d3d11. https://docs.microsoft.com/en-us/windows/win32/direct3dhlsl/specifying-compiler-targets We can try to change the shaders to target shader model 4. It should just be a matter of changing the target in shader compile call because I don't think we're using any shader model 5 features. That should let us support d3d10 machines. It's weird that dxdiag thinks directx 12 is supported?
claunia commented 2026-01-31 00:25:37 +00:00
Author
Owner
Copy Link

@lennybacon commented on GitHub (Apr 8, 2021):

Probably related. The retroTerminalEffect has no visual affect but produces high CPU load in my Windows 10 VMs with a RDP or Hyper-V connection.

@lennybacon commented on GitHub (Apr 8, 2021): Probably related. The `retroTerminalEffect` has no visual affect but produces high CPU load in my Windows 10 VMs with a RDP or Hyper-V connection.
claunia commented 2026-01-31 00:25:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 22, 2022):

@GrumpyDemus you still seeing this? We have gotten surprisingly few reports of this over the last few years so I'm kinda hoping this is something that was machine dependent. That, and we're bumping the min version required for the Terminal to 19041, maybe the issue was OS version dependent. Anyways, if this is resolved, I'd love to get it cleaned off the backlog.

I totally wouldn't expect it to work in VMs at all - idk if hyperv really supports GPU scenarios in VMs like that. IIRC there's another closed thread about that.

@zadjii-msft commented on GitHub (Feb 22, 2022): @GrumpyDemus you still seeing this? We have gotten surprisingly few reports of this over the last few years so I'm kinda hoping this is something that was machine dependent. That, and we're bumping the min version required for the Terminal to 19041, maybe the issue was OS version dependent. Anyways, if this is resolved, I'd love to get it cleaned off the backlog. I totally wouldn't expect it to work in VMs at all - idk if hyperv really supports GPU scenarios in VMs like that. IIRC there's another closed thread about that.
claunia commented 2026-01-31 00:25:37 +00:00
Author
Owner
Copy Link

@lennybacon commented on GitHub (Feb 22, 2022):

There are visual effects but the CPU is still very very high as soon as the window is focused. Running a VM on 19041.

image

image

@lennybacon commented on GitHub (Feb 22, 2022): There are visual effects but the CPU is still very very high as soon as the window is focused. Running a VM on 19041. ![image](https://user-images.githubusercontent.com/272164/155163224-9332b801-1ceb-4cf6-80df-8220eef6c019.png) ![image](https://user-images.githubusercontent.com/272164/155163177-82cb1bcb-edf6-48ae-aa21-da5c0f4ede33.png)
claunia commented 2026-01-31 00:25:38 +00:00
Author
Owner
Copy Link

@GrumpyDemus commented on GitHub (Feb 22, 2022):

@GrumpyDemus you still seeing this? We have gotten surprisingly few reports of this over the last few years so I'm kinda hoping this is something that was machine dependent. That, and we're bumping the min version required for the Terminal to 19041, maybe the issue was OS version dependent. Anyways, if this is resolved, I'd love to get it cleaned off the backlog.

@zadjii-msft as @ironyman mentioned, the shader needs d3d11 support and the graphics card in that system only supports up to d3d10, therefore the shader won't work I suppose.
The affected system isn't in use anymore, so it doesn't matter (for me at least).

@GrumpyDemus commented on GitHub (Feb 22, 2022): > @GrumpyDemus you still seeing this? We have gotten surprisingly few reports of this over the last few years so I'm kinda hoping this is something that was machine dependent. That, and we're bumping the min version required for the Terminal to 19041, maybe the issue was OS version dependent. Anyways, if this is resolved, I'd love to get it cleaned off the backlog. @zadjii-msft as @ironyman mentioned, the shader needs d3d11 support and the graphics card in that system only supports up to d3d10, therefore the shader won't work I suppose. The affected system isn't in use anymore, so it doesn't matter (for me at least).
claunia commented 2026-01-31 00:25:38 +00:00
Author
Owner
Copy Link

@OstiumAxioma commented on GitHub (Nov 19, 2023):

@zadjii-msft Just want to report to this post that my machine is dx12 supported, but CTR effect only showed up for once in my terminal. And when I close the window and reopen it, it's gone. The setting for retro effect remains open. Which is really weird for me.

@OstiumAxioma commented on GitHub (Nov 19, 2023): @zadjii-msft Just want to report to this post that my machine is dx12 supported, but CTR effect only showed up for once in my terminal. And when I close the window and reopen it, it's gone. The setting for retro effect remains open. Which is really weird for me.
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 Needs-Attention Needs-Repro Needs-Tag-Fix 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#5927
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?