General Discussions

My entire message dissapeared after being redirected to some random website which I assume was some sort of DDOS protection or did some mod delete it? Wtf...

Attempt n2:

i.imgur.com/cxu2WJX.jpg
i.imgur.com/V440qsZ.jpg
i.imgur.com/ltxUDiL.jpg
Not my images, found online.

Win10 64 bit, RX480, 16GB RAM.

The only thing that fixes it is adding trails to the mouse pointer but it makes it feel slow and doesn't work in video games unless its running on windowed mode. I have an SSD so rebooting is not a real problem but sometimes it happens mid-game.

I'm using latest drivers for the RX480 installed properly with driver sweeper and such but this doesn't matter because its been happening before I updated.

I keep reading how this is an AMD driver issue and has been present for a long time but: Why isn't there mass uproar/Why do I seem to be the only one who has this and secondly, I have only ever owned ATI/AMD cards and never had this issue until very recently.

Thanks a lot PLEASE help me if you can.

[Edited by OnlyLagKillsMe, 9/18/2016 7:36:07 PM]

I remember having this problem back on my old PC which had the old 5770 GPU. There's no real fix IIRC except for furiously shaking the mouse all over the screen or rebooting. Also try rolling back to a previous version of the GPU drivers, but do a clean install. I also assume you've tried switching back and forth between cursor styles in control panel?

I don't know what cursor styles mean. As I said, adding pointer trails fixes it but there's two things which makes this not a solution at all: Makes the cursor feel very lag-like and you cannot do it in Dota if the game is running in fullscreen.

Control panel > Mouse > Pointers tab > Scheme dropdown menu. I haven't played LoL for a while but check if it has an option to disable Mouse Hardware Acceleration in Options.

I do not play this lol and this has nothing to do with an ingame setting because it occurs in the desktop environment

edit: tried changing the scheme, doesn't work. adding pointer trails remains the only way to mitigate the issue absent a system restart

[Edited by OnlyLagKillsMe, 9/19/2016 11:28:47 AM]