Hopefully Blizzard will add a MouseGetX(int player) function in some later release. There is absolutely no reason why this should not be added. Stuff like CameraForceMouseRelative already causes the mouse position to be tracked, the only problem is that the camera moves too. The best solution I have found so far is to set the mouse sensitivity very low so that the camera doesn't move much after using CameraForceMouseRelative. Then, I manually recenter the camera and use how much the camera move to compute the mouse movement. This is works okay at low speeds, but if your centered position moves quickly, then performance degrades. Honestly, it would be so simple to have a trigger do the exact same thing as CameraForceMouseRelative, just not have the camera move and update some value instead.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hopefully Blizzard will add a MouseGetX(int player) function in some later release. There is absolutely no reason why this should not be added. Stuff like CameraForceMouseRelative already causes the mouse position to be tracked, the only problem is that the camera moves too. The best solution I have found so far is to set the mouse sensitivity very low so that the camera doesn't move much after using CameraForceMouseRelative. Then, I manually recenter the camera and use how much the camera move to compute the mouse movement. This is works okay at low speeds, but if your centered position moves quickly, then performance degrades. Honestly, it would be so simple to have a trigger do the exact same thing as CameraForceMouseRelative, just not have the camera move and update some value instead.