Mouse / system lag when terminal is focused #5231

@Cry0nicS commented on GitHub (Nov 27, 2019):

@zadjii-msft You are correct! Setting "useAcrylic" : false fixed the problem. (I guess removing the property altogether has the same effect).

Is there like a list of parameters to be used for optimal usage (so that I avoid similar issues in the future)?

@Cry0nicS commented on GitHub (Nov 27, 2019): @zadjii-msft You are correct! Setting `"useAcrylic" : false` fixed the problem. (I guess removing the property altogether has the same effect). Is there like a list of parameters to be used for optimal usage (so that I avoid similar issues in the future)?

claunia commented

@DHowett-MSFT commented on GitHub (Nov 30, 2019):

There isn't such a list. Sorry!

This is likely among the reasons that the platform team keeps warning us about using acrylic on large surfaces. 😄

@DHowett-MSFT commented on GitHub (Nov 30, 2019): There isn't such a list. Sorry! This is likely among the reasons that the platform team keeps warning us about using acrylic on large surfaces. :smile:

claunia commented

@Cry0nicS commented on GitHub (Dec 5, 2019):

@zadjii-msft Can I re-open this? The issue still persists, the only difference is that now behavior disappears if I focus out of the terminal and back on it.

The only changes I made in profiles.json are the following:

    "profiles":
    [
        { 
	     "guid" : "{14ad203f-52cc-4110-90d6-d96e0f41b64d}", 
            "name" : "Git Bash", 
            "commandline" : "C:/Program Files/Git/bin/bash.exe --login", 
            "hidden": false,
            "startingDirectory" : "d:/Projects/GosuGamers/development-environment/environments",
            "closeOnExit": true,
            "colorScheme" : "MaterialOcean",
            "fontFace" : "Source Code Pro", 
            "fontSize" : 13, 
            "icon": "C:\\Program Files\\Git\\mingw64\\share\\git\\git-for-windows.ico",
            "padding" : "20, 20, 20, 20",
            "useAcrylic": false
        }
    ],

    // Add custom color schemes to this array
    "schemes": [
		{
			"name":  "MaterialOcean",
			"black":  "#546e7a",
			"red":  "#ff5370",
			"green":  "#c3e88d",
			"yellow":  "#ffcb6b",
			"blue":  "#82aaff",
			"purple":  "#c792ea",
			"cyan":  "#89ddff",
			"white":  "#ffffff",
			"brightBlack":  "#546e7a",
			"brightRed":  "#ff5370",
			"brightGreen":  "#c3e88d",
			"brightYellow":  "#ffcb6b",
			"brightBlue":  "#82aaff",
			"brightPurple":  "#c792ea",
			"brightCyan":  "#89ddff",
			"brightWhite":  "#ffffff",
			"background":  "#0f111a",
			"foreground":  "#8f93a2"
		}
	]

@Cry0nicS commented on GitHub (Dec 5, 2019): @zadjii-msft Can I re-open this? The issue still persists, the only difference is that now behavior disappears if I focus out of the terminal and back on it. The only changes I made in profiles.json are the following: ```json "profiles": [ { "guid" : "{14ad203f-52cc-4110-90d6-d96e0f41b64d}", "name" : "Git Bash", "commandline" : "C:/Program Files/Git/bin/bash.exe --login", "hidden": false, "startingDirectory" : "d:/Projects/GosuGamers/development-environment/environments", "closeOnExit": true, "colorScheme" : "MaterialOcean", "fontFace" : "Source Code Pro", "fontSize" : 13, "icon": "C:\\Program Files\\Git\\mingw64\\share\\git\\git-for-windows.ico", "padding" : "20, 20, 20, 20", "useAcrylic": false } ], // Add custom color schemes to this array "schemes": [ { "name": "MaterialOcean", "black": "#546e7a", "red": "#ff5370", "green": "#c3e88d", "yellow": "#ffcb6b", "blue": "#82aaff", "purple": "#c792ea", "cyan": "#89ddff", "white": "#ffffff", "brightBlack": "#546e7a", "brightRed": "#ff5370", "brightGreen": "#c3e88d", "brightYellow": "#ffcb6b", "brightBlue": "#82aaff", "brightPurple": "#c792ea", "brightCyan": "#89ddff", "brightWhite": "#ffffff", "background": "#0f111a", "foreground": "#8f93a2" } ] ```

claunia commented

@zadjii-msft commented on GitHub (Dec 5, 2019):

@Cry0nicS Sure, if disabling acrylic didn't seem to fix your problem then there must be something else at work here.

@zadjii-msft commented on GitHub (Dec 5, 2019): @Cry0nicS Sure, if disabling acrylic didn't seem to fix your problem then there must be something else at work here.

claunia commented

@DHowett-MSFT commented on GitHub (Dec 5, 2019):

This is curious. Would you mind sharing some more information about your system? What sort of graphics hardware have you got, what's your display size and topology, etc.?

@DHowett-MSFT commented on GitHub (Dec 5, 2019): This is curious. Would you mind sharing some more information about your system? What sort of graphics hardware have you got, what's your display size and topology, etc.?

claunia commented

@Cry0nicS commented on GitHub (Dec 5, 2019):

@DHowett I have a tri-monitor setup. 2x 23" Dell (1080p) + main 27" Dell (1440p). These are powered by an nVidia RTX2080 (driver: 8.1.940.0), one SSD, and 32GB Ram.

The issue seems to be much more significant on the 27" monitor.
On the other two, smaller, monitors everything seems almost fine.

@Cry0nicS commented on GitHub (Dec 5, 2019): @DHowett I have a tri-monitor setup. 2x 23" Dell (1080p) + main 27" Dell (1440p). These are powered by an nVidia RTX2080 (driver: 8.1.940.0), one SSD, and 32GB Ram. The issue seems to be much more significant on the 27" monitor. On the other two, smaller, monitors everything seems almost fine.

claunia commented

@zadjii-msft commented on GitHub (Dec 5, 2019):

@Cry0nicS Any chance the dell monitor is at a different framerate than the other monitors?

@zadjii-msft commented on GitHub (Dec 5, 2019): @Cry0nicS Any chance the dell monitor is at a different framerate than the other monitors?

claunia commented

@Cry0nicS commented on GitHub (Dec 5, 2019):

@zadjii-msft yes it is. 144hz (compared to the 59 for the other two)

@Cry0nicS commented on GitHub (Dec 5, 2019): @zadjii-msft yes it is. 144hz (compared to the 59 for the other two)

claunia commented

@zadjii-msft commented on GitHub (Dec 5, 2019):

I'm not psychic I swear, #3857 just came in suggesting the same thing was responsible 😜

@zadjii-msft commented on GitHub (Dec 5, 2019): I'm not psychic I swear, #3857 just came in suggesting the same thing was responsible 😜

claunia commented

@DHowett-MSFT commented on GitHub (Dec 9, 2019):

This looks like it might be a /dupe of #649. Thanks for the report!

@DHowett-MSFT commented on GitHub (Dec 9, 2019): This looks like it might be a /dupe of #649. Thanks for the report!

claunia commented

@ghost commented on GitHub (Dec 9, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Dec 9, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

claunia commented