Forums

Bug at startup, stuck mouse cursor

• JRedstar 8 Posts

  Sun, Jul 18 2021 9:07 AM

  This would be on the desktop version (1.71.1.219362_D)
  
  Upon launch the mouse cursor gets stuck in the middle of the screen. Have to use Task Manager to exit the game. this happens alot, almost every time I launch the game. Usually after about 5 or 6 launches it will work normal again

  OS Name Microsoft Windows 10 Pro

  Version 10.0.19042 Build 19042

  System Manufacturer ASUS

  Processor Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz, 3792 Mhz, 8 Core(s), 16 Logical Processor(s)

  BIOS Version/Date American Megatrends Inc. 1410, 9/4/2020

  SMBIOS Version 3.2

  Embedded Controller Version 255.255

  BIOS Mode UEFI

  BaseBoard Manufacturer ASUSTeK COMPUTER INC.

  BaseBoard Product PRIME Z490-P

  BaseBoard Version Rev 1.xx

  Platform Role Desktop

  Secure Boot State Off

  Name NVIDIA GeForce GTX 1080

  PNP Device ID PCI\VEN_10DE&DEV_1B80&SUBSYS_859B1043&REV_A1\4&38AB2860&0&0008

  Adapter Type NVIDIA GeForce GTX 1080, NVIDIA compatible

• borntobesting 9,623 Posts

  Sun, Jul 18 2021 11:05 AM

  Check Scott's Tips in the Community Help section of the forums. I think he addressed this some time ago, 

• ScottHope 10,092 Posts

  Sun, Jul 18 2021 12:57 PM

  Thanks Joe.  ; )

  You could try a reset JR. Click. Make sure you have your WGT login to hand as doing this will log you out of the game.

• devilgunner 17 Posts

  Sun, Jul 18 2021 1:25 PM

  I'm having the same issue that the OP had and I tried the reset and a reinstall and the problem hasn't been solved. Any other ideas?

• ScottHope 10,092 Posts

  Sun, Jul 18 2021 11:15 PM

  Try a different mouse.
  Plug mouse into a different USB port.
  New battery if using wireless mouse.

• ChrisDeGarmo 23 Posts

  Sat, Aug 7 2021 6:40 PM

  JRedstar:

  This would be on the desktop version (1.71.1.219362_D)
  
  Upon launch the mouse cursor gets stuck in the middle of the screen. Have to use Task Manager to exit the game. this happens alot, almost every time I launch the game. Usually after about 5 or 6 launches it will work normal again

  OS Name Microsoft Windows 10 Pro

  Version 10.0.19042 Build 19042

  System Manufacturer ASUS

  Processor Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz, 3792 Mhz, 8 Core(s), 16 Logical Processor(s)

  BIOS Version/Date American Megatrends Inc. 1410, 9/4/2020

  SMBIOS Version 3.2

  Embedded Controller Version 255.255

  BIOS Mode UEFI

  BaseBoard Manufacturer ASUSTeK COMPUTER INC.

  BaseBoard Product PRIME Z490-P

  BaseBoard Version Rev 1.xx

  Platform Role Desktop

  Secure Boot State Off

  Name NVIDIA GeForce GTX 1080

  PNP Device ID PCI\VEN_10DE&DEV_1B80&SUBSYS_859B1043&REV_A1\4&38AB2860&0&0008

  Adapter Type NVIDIA GeForce GTX 1080, NVIDIA compatible

  Likely culprit is some other type of USB controller plugged in currently, or the 'ghost' driver of same still making the system think it's plugged in.

  Power down. Unplug ALL USB devices. Add your keyboard and mouse back if they are USB. Restart. If the problem persists with only keyboard/mouse combo, then you might have an old stuck USB driver. You might get lucky and find it in add/remove, or you might need to dig through Device Manager manually, or you might need a 3rd party cleaner.

  If your cursor is 'rubber banding' (every time you move it away from center, it pops back), then the above is pretty much guaranteed your problem. It's a programming error in WGT in that it sees your mouse AND the other installed 'controller' and is simultaneously 'reading' both device positions. When your mouse moves the cursor, the 'other controller' is still centered, so it rubber bands back.

  Things like Flightsim yolks, rudder pedals, joysticks and game controllers are all likely suspects, and you might have even forgotten they are still plugged in.

  Hope this helps anyone

• JRedstar 8 Posts

  Mon, Aug 9 2021 10:56 AM

  the info here was useful, in that it gave me a simpler idea to try. I use a wireless mouse with a dongle (not bluetooth) and I just pulled out the dongle, put it back in, problem solved