Mouse cursor freezing and flickering ingame (Anno 1800)

[:E ! FuX]

Hello there,

my setup is the following (everything is connected wired):
Client: Raspberry Pi 4 B (4GB RAM) with fresh default Raspbian OS and only steamlink app installed with a wired mouse and keyboard.
Host: Win10, AMD Ryzen 7 3700X, 32GB RAM, Geforce 1060.

I can connect fine and some games seem to work fine (did just some short testing) but when starting "Anno 1800" at first everything seems fine but whenever I hover over a "usable" menu item the mouse curser freezes and flickers heavily (no input from mouse or keyboard is registered and even the performance overlay freezes completely). As soon as I move the mouse off this menu item on my host PC everything is back to normal and I can move the mouse on the Steamlink client again. On my host PC the game runs fine and shows a smooth "breathing" white overlay over the cursor when it is hovering a usable menu or ingame item.

The logfile is pasted here: https://paste2.org/kJKnGcMm

I tried the current release and the beta version of both steam on my host PC and the steam link app. (Host has "NVFBC" and general "Nvidia encoding" active and on the client "HEVC" is disabled - but i tried all different variations with the same result).
Only "HEVC" is absolutely not working for me. As soon as I activate it in steamlink and connect to my PC the screen shows a broken welcome screen (upper two thirds are black and performance graph is only showing some partial numbers out of place). Do I have to install anything on the Raspberry or change a host PC setting for HEVC?

Thank you!

[:E ! FuX]

Alright, I got HEVC working now (I already used the beta but changed video ram setting on the Pi and installed 1-2 more libraries for HEVC support - don't know what exactly did the trick but now its fine).
Tested several other games and all seem to work fine, but I can't get Anno 1800 to work. The issue is still exactly the same. The game offers no mouse related settings. Already tried all other graphics options (DX11 or DX12, fullscreen or windowed). The issue is still exactly the same.

[slouken]

Nice catch, this is fixed in the latest beta build.

Thanks!

[:E ! FuX]

Thank you very much for fixing this bug on such short notice. I just tested it and it works perfectly fine :)