Weird camera movement in the map editor

[NoType1]

Describe the bug
The freecam has very weird and snappy movement. So if you try to move your camera, it feels as if it is being snapped into place instead of moving smoothly (like it used to be)

To reproduce

Steps to reproduce the behaviour:

1. Go to local map editor (it can be in a server as well)
2. Move camera around when its in the freecam mode

Expected behaviour
A properly functioning freecam with no snappy movement. (I'm reporting this on the behalf of lots of other mappers, including myself)
The bug does not occur when you press F for the cursor mode.

Version
MTA 1.5.6 Latest build.
OS: Windows 10, 8.1 and 7

Additional context
I hope that someone can find a fix for this. It is very frustrating, and totally demotivating.
This has all started after the latest update.

[NoType1]

Here's a screenshot of my settings

[Aqu1L]

I've got the same problem, reinstalling MTA & GTA didnt help.
+More mappers have this problem :c

[Wolfee-J]

Set FPS limit to 60, at-least for me 30 FPS has been slower then normal with the latest updates.

[NoType1]

Set FPS limit to 60, at-least for me 30 FPS has been slower then normal with the latest updates.

Sadly that doesn't work either..
I have reinstalled my mouse drivers, people have reinstalled MTA and GTA SA. Nothing seems to work.

[moon91210]

I can confirm the camera is broken. All the mappers I talk to have the same problem, they're all on different computers and servers too. Everytime I want to help out my buddy with a map I get reminded that the camera is broken and that I just can't work with it at all.

[Wolfee-J]

Would you mind trying this - https://github.com/CodyJL/Editor-2 and seeing if the camera movement is the same? (narrows down if it's related to MTAs editor or something internal)

[moon91210]

Cody, your camera behaved the same when I tested your resource. Are you using the freecam resource by any chance? That's what the mta editor is using.

[Wolfee-J]

I was just verifying there wasn't a recent update with the editor because this uses a modify version of 'Freecam'. I will look into what is causing the delay and report back.

[NoType1]

Your camera also behaved the same for me. Did you have any luck in finding the bug?

[Wolfee-J]

I believe this - #643 (comment) is related.

[Deltanic]

That issue is a graphical glitch and has nothing to do with this. This issue is is related to imprecision in onClientCursorMove. In fact, I would argue the current situation might be a hack since there is no better alternative. Dumping the values of aX and aY of the code here at a constant mouse moving rate yields a sequence similar to the following:
3, 4, 3, 3, 4, 3, 10, 3, 4, 0, 3, 3, 4, 10, 4, 3
Obviously, these outliers cause the glitchy feel to the freecam.

Also related: the onClientMouseMove event is called more frequently than onClientRender. This may cause some jitter too, since onClientMouseMove could be called twice per frame, causing the camera to update twice before it is visibly rendered.

My guess is that the outliers within onClientCursorMove are caused by irregular repositioning of the cursor, allowing the mouse to move further away from the screen center before it is recentered. Not sure what the cause of that is, though.

Is it perhaps technically viable to implement a function that is able to get the mouse movement speed without relying on the repositioning, possibly as a control state? Such a function would inherit the mouse sensitivity from the game, and allow use in onClientRender, effectively solving both issues.

[MegadreamsBE]

Proper interpolation could smooth things out then (consistent timing between moving between two camera positions).

[Wolfee-J]

I'm creating a new freecam system at the moment. However the screen tearing is still related because it makes the issue stand out a whole lot more then it initially would have.

…

On Sun, Dec 9, 2018, 10:21 PM MegadreamsBE ***@***.*** wrote: Proper interpolation could smooth things out then (consistent timing between two camera positions). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/multitheftauto/mtasa-resources/issues/134#issuecomment-445651543>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AmWIt0kHocbKiuQWCHKaji69H6n1cmQMks5u3dNUgaJpZM4Y9d_-> .

[Deltanic]

Just because it makes it more annoying doesn't mean the issues are related to one another. One is a graphical issue, the other is an input issue.