Mouse glitch on Windows 10 RS3 (version 1709 Fall creators update)

[airdjing]

This situation causes a mouse glitch when running moonlight-chrome on newly released Windows 10 1709 (RS3, Fall creators update)

I tested various situations in my own way.
It occurs when only client OS is Windows 10 1709.
And the rest does not matter whether it is a client any chrome version and server's any GFE version.

Example videos

• Problem
  https://youtu.be/Ei5wEsJv3lY (Wireless Network, Win 10 1709)
  https://youtu.be/YKtl0H_S8hY (Wired, Win 10 1709)

• No Problem on Win10 RS2 (Wired, Win 10 1703)
  https://youtu.be/PSSomRPvkkU

• LOCAL CLIENT vs VNC vs MOONLIGHT (Wireless Network, Win 10 1709)
  https://youtu.be/pnQEUvYuyZ8

• No Problem on Android (Wireless)
  https://youtu.be/hnCkmvd79sE

Is the solution only a rollback to 1703?

[nhtones]

Also seeing similar behaviour - latest moonlight chrome extension.

[MagFlux]

This looks to be the same problem as seen in issues #335 and #324. Tagging them here for reference.

[airdjing]

@MagFlux
I think this is not a physical problem with a mouse input or a network.
Because I tested only change OS on the same PC, same network connection, same input controls
then result is different.
and same client's chrome version, same server's GFE version and same server's geforce driver version too.

This is my tested system settings.

• Server
  Windows 10 x64 1709
  NVIDIA 388.00 Display Adapter Driver (980ti)
  GFE 3.10.0

• Client 1 (Wireless Network, Lenovo Bluetooth mouse, Touch pad)
  Intel Graphics v20.19.15.4531 (HD 5300)
  Chrome 62.0.3202.62
  Moonlight v0.7.4
  Windows 10 x64 1703 - Test Result : No problem
  Windows 10 x64 1709 (Clean Install) - Test Result : Problem

• Client 2 (Wired Gigabit Network, Logitech Wired Mouse)
  NVIDIA 388.00 Display Adapter Driver (1050)
  Chrome 62.0.3202.62
  Moonlight v0.7.4
  Windows 10 x64 1703 - Test Result : No problem
  Windows 10 x64 1709 (Upgraded from 1703) - Test Result : Problem

[johnblaze00]

no its a problem if the client is on 1709, 1703 works fine, other OS work fine. I have been gaming with my macbook pro lately as its basically unplayable on my windows 1709 desktop and it wont let me revert back for some dumb reason even though i didnt remove the previous install or delete the "windows.old" folder... got to wait for these guys to patch the moonlight client on windows before I can start playing again on my windows machines.

[defcon1186]

Same issue here, and yes, I'm on 1709 version recently updated... #358

[llajas]

I am also experiencing this exact issue. Just like the video, it's only apparent I try and move my mouse while simultaneously holding/pressing a button on the mouse itself. i.e.: Holding right mouse to aim down the sights/scope in an FPS while looking around, or just simply holding left mouse to auto-fire is next to impossible if I try and look around at the exact same time.

Both client & server are on the new Fall Creators Update (Build 1709) of Windows 10. I currently don't have the ability to roll back from 1709 easily, but the issue wasn't present when using a friends computer running Windows 7, so it's definitely something isolated to Windows 10 v1709, from my testing.

[cgutman]

Here is a build with a workaround for Fall Creators Update. It's not perfect, but it ignores most of the errant mouse events. I don't feel comfortable rolling the fix out in the official build, because it can accidentally mark valid movements as errant and create problems where there were none before. https://drive.google.com/open?id=1NhdQ2AFss1Y8RRXbal9HDSjnAwO_90hO

I filed a bug on Chrome for investigation as this bug affects all users of Pointer Lock, not just Moonlight. Feel free to star the bug, but don't comment unless you have some technical analysis to add (since it sends everyone on the ticket an email). https://bugs.chromium.org/p/chromium/issues/detail?id=784122

[airdjing]

@cgutman 0.75(rs3hack) version you provided works pretty well. I'll use this until chrome's bugs get fixed.
Moonlight is an important application in my life.
I highly appreciate for your hard work. Thank you.

[MagFlux]

@cgutman Thanks for putting out this hotfix! Solves the problem I was seeing, working quite well. Thanks again for taking the time to look into this and determine a root cause.

[llajas]

@cgutman Thanks for the quick patch! It feels like there is a slight delay when compared to running the official release on a Pre-Creators update box, but it is much better now than where it was at first.

[nebiont]

@cgutman Thank you so much for the custom build, it's working perfectly! Hopefully a fix is implemented into Chrome soon.

[nicholson101]

Hotfix isn't working for me. Still getting the mouse jumps :-(

[JustAnOpossum]

@cgutman Thank you so much. At times there are still jumps, but for the most part, it working great.

[airdjing]

Today chrome Updated to 63.0.3239.84 version.
But problem still exists.

[simonzeiger]

@cgutman Can I ask how you went about fixing this bug? I have a web gl fps game that is having trouble in chrome. I am really stuck on what to do.