There have been some
grievances about the
jumping mouse cursor issue but I think I finally figured out what causes it.
3dmm snaps the cursor to the center when you move it outside the window, which is a common technique for tracking the mouse cursor and prevents the cursor from hitting the bounds of the screen or whatever. However, Windows 10 is so "responsive" that when 3dmm goes to grab the next mouse position, it sometimes doesn't get the newly "snapped" position it set before, and so there are incremental issues while dragging. Like in this video:
The fix I came up with was to add some milliseconds of idle time after each call to the Windows API SetCursorPos function (in User32.dll) to give time for Windows to dispatch the events.
Download it here.
-To use it, you must have 3dmm/v3dmm already running. Then just run it and it should patch successfully. The caveat atm is you must run the utility again if you close the 3dmm window. (I don't know yet how to make the patch effective on harddisk as the offsets to the DLLs will vary each time you start up 3dmm.)