Cursor occasionally locks into centre of screen while in freecam

[bredo228]

Describe the issue.

Occasionally when in freecam (F6), the cursor will snap into the centre of the screen and not be released until you open your dash.

This makes actions such as panning / tilting the camera impossible.

To Reproduce

Enter freecam mode and right click in an attempt to pan the third person camera. Notice that occasionally it will snap to the centre of the screen and not allow for movement.

Expected behavior

Cursor to not snap into centre of the screen, freecam movement to work consistently.

Screenshots

Github wouldn't let me upload this:
https://youtu.be/E5MgxnbaVas

Resonite Version Number

Beta 2024.11.12.1329 (Prerelease)

What Platforms does this occur on?

Windows

What headset if any do you use?

No response

Log Files

ERIS - 2024.11.12.1329 - 2024-11-13 21_00_46.log

Additional Context

This seems to occur more when loading into worlds

Reporters

bredo

[epicEaston197]

This is not a pre release problem this has been a problem for months that I've been planning on reporting for a while now

[shiftyscales]

@bredo228 - It is not entirely clear what I am looking for in the video you had posted- you specify panning / tilting the camera is impossible- but you also note that the issue resolves after the dash has been opened if I'm understanding correctly?

It might help if you turn on the input debugger (found in the Misc. section of the setting page) when recording so it is apparent what you are inputting vs. what is seen on the recording.

Are there any other conditions that resolve the issue, e.g. changing camera state to first / third-person and back? Or is it just opening the dash? How often does the issue occur?

Enter freecam mode and right click in an attempt to pan the third person camera.

You also need to be holding the control key to turn / move the camera while navigating in freecam. Control + right mouse button + mouse movement / movement keys. After you've initiated it, you can release control or the right mouse button.

I can't seem to replicate the issue as you described it in your replication steps? As long as I'm holding control things seem like they work every single time?

[epicEaston197]

This is not an issue that can really be replicated it just kinda happens and most of the time I need to restart my entire client to fix my free cam respawning the user does not fix it

[bredo228]

Issue is I can't pan the camera with the mouse - movement with the WASD keys works fine.

I'm not having much luck reliably replicating this myself - have managed to get a video of it occurring while the input debug is open though.

Seems to mainly happen for me on loading stuff for the first time - this occurrence was on a fresh cache / database.

Releasing control doesn't seem to release the mouse, tried opening the context menu and was able to move my mouse in the context menu but that didn't release the mouse. Opening the dash seems to be a reliable way of releasing the mouse.

Switching back into first person seems to work fine

ERIS - 2024.11.12.1329 - 2024-11-14 16_33_49.log

https://youtu.be/7dpwmz90DDQ

[shiftyscales]

@bredo228 - Looking at your video- I see that when you're trying to move it is registering as CameraOrbit- this leads me to believe that you used Alt + Right Click instead of Control + Right Click and haven't yet selected a focus object (Control + F) and thus have no object selected with which to orbit around.

https://wiki.resonite.com/Basic_Controls#Desktop_Controls

[epicEaston197]

@bredo228 - Looking at your video- I see that when you're trying to move it is registering as

Using Alt + Right Click Is a very deliberate action I have the free cam down to muscle memory there is no way I've clicked Alt + Right Click When going into free cam I've always used control + Right Click

[bredo228]

@bredo228 - Looking at your video- I see that when you're trying to move it is registering as CameraOrbit- this leads me to believe that you used Alt + Right Click instead of Control + Right Click and haven't yet selected a focus object (Control + F) and thus have no object selected with which to orbit around.

https://wiki.resonite.com/Basic_Controls#Desktop_Controls

I never tried to use Alt + Right Click when recording that video - it was all Control + Right Click.

Wasn't trying to focus on anything either

[shiftyscales]

What keyboard are y'all using? Is it NKRO? I'm curious if it's a case of the keyboard sending a wrong / false input while multiple keys are held. Does the issue occur more consistently if you hold additional keyboard keys? It may also be helpful to have an input overlay while recording to check for the presence of erroneous key presses.

[bredo228]

What keyboard are y'all using? Is it NKRO? I'm curious if it's a case of the keyboard sending a wrong / false input while multiple keys are held. Does the issue occur more consistently if you hold additional keyboard keys? It may also be helpful to have an input overlay while recording to check for the presence of erroneous key presses.

I'm using a Keychron V1, unsure if it's NKRO or not. Can try getting a recording of the issue with a keyboard overlay at some stage.

[shiftyscales]

Is it being used wired, or wireless, @bredo228? I looked- it up- they apparently removed that documentation on their site, but a reddit post highlighted a Wayback Machine capture that suggests most models are 5 or 6KRO when used wireless.

Keychron have updated their website and have removed all reference to NKRO but the link below is a comparison chart that used to be on their website that showed that the k and c series have NKRO when wired and 6KRO wireless (K series only). the K pro and Q series have NKRO for both wireless and wired.

All keychron keyboards ship in 6KRO mode and you need to press fn+N to get to NKRO, at least this worked for my k4 pro.

https://www.reddit.com/r/Keychron/comments/17zmfaw/comment/ka0arfp/

https://web.archive.org/web/20201215083102/https://www.keychron.com/blogs/news/difference-among-keychron-keyboards

[bredo228]

Is it being used wired, or wireless, @bredo228? I looked- it up- they apparently removed that documentation on their site, but a reddit post highlighted a Wayback Machine capture that suggests most models are 5 or 6KRO when used wireless.

Keychron have updated their website and have removed all reference to NKRO but the link below is a comparison chart that used to be on their website that showed that the k and c series have NKRO when wired and 6KRO wireless (K series only). the K pro and Q series have NKRO for both wireless and wired.
All keychron keyboards ship in 6KRO mode and you need to press fn+N to get to NKRO, at least this worked for my k4 pro.

https://www.reddit.com/r/Keychron/comments/17zmfaw/comment/ka0arfp/

https://web.archive.org/web/20201215083102/https://www.keychron.com/blogs/news/difference-among-keychron-keyboards

I'm running my keyboard wired - mine's not a model with wireless. Will see if that NKRO setting makes a difference when I get the chance.