Bug 93732 - SW cursor flicker in-game
Summary: SW cursor flicker in-game
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: 11.0
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-16 12:33 UTC by Thomas Martitz
Modified: 2019-09-18 20:42 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
glxinfo (97.81 KB, text/plain)
2016-01-16 12:33 UTC, Thomas Martitz
Details

Description Thomas Martitz 2016-01-16 12:33:30 UTC
Created attachment 121072 [details]
glxinfo

I've got a GeForce 650 Ti, and when I'm using the SW cursor (either manually through xorg.conf, or enforced in a Reverse PRIME setup), the cursor begins to flicker heavily in the Dota 2 game.

It seems that not only the cursor flickers heavily but also clicking is harder (as if the click didn't work when the cursor is invisible).

I do not experience this with HW cursor or on the desktop or with the game in windowed mode.

This is on GNOME 3 which disables compositing in full-screen applications.

X -version

X.Org X Server 1.18.0
Release Date: 2015-11-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.3.3-2-ARCH x86_64 
Current Operating System: Linux thomas-nb 4.3.3-2-ARCH #1 SMP PREEMPT Wed Dec 23 20:09:18 CET 2015 x86_64
Kernel command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img root=/dev/sda2 rw nouveau.pstate=1 nouveau.War00C800_0=1 nouveau.config=War00C800_0=1
Build Date: 16 January 2016  01:12:20PM
Comment 1 GitLab Migration User 2019-09-18 20:42:06 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1096.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.