Actually, I figured it out. I unintentionally limited the results from the mousemovementX reads. Fixed it. I went from getting only 2 full rotations to about 5 now before hitting the skids. That oughta do it.
desktop width of 1920 / 360 degrees = 5.3 rotations
Yes, it hits -50 on the left and will go no further and then width - 50 on the right and stops. I can get five rotations now after fixing my error. And, yeh, I'm on a Mac.
desktop width of 1920 / 360 degrees = 5.3 rotations
(02-13-2024, 07:42 PM)DSMan195276 Wrote: What platform are you using? I ask because on Windows I believe it should already work as you're describing, it should continue to report the relative movement regardless of the actual cursor position. On Linux and Mac OS the support is currently a bit more limited and it will get stuck like you're suggesting (which is something that will hopefully be fixed in the future).
To clarify, you're saying that `_MouseMovementX` starts returning 0 when the mouse hits the edge of the screen even if you're still moving the mouse in that direction?
Yes, it hits -50 on the left and will go no further and then width - 50 on the right and stops. I can get five rotations now after fixing my error. And, yeh, I'm on a Mac.