When character moves, he gets a little jittery

PriestSoryu

When the character moves, it looks like this, a little strange and sometimes it gets worse.

I've already tried all the scripts I found, from my own to Godot's documentation, but this visual problem persists.

I tested it with a community project too, and it persists.

I thought it could be my hardware, however, I have an RTX 2060 and a Ryzen 5, I don't think that's the problem. I have no idea how to solve it, does anyone have any hypotheses?

obs: I'm new to Godot, I just came from Unity

extends CharacterBody2D
var run_speed = 350

func get_input():
     velocity.x = 0
     var right = Input.is_action_pressed('ui_right')
     var left = Input.is_action_pressed('ui_left')

     if right:
	velocity.x += run_speed
     if left:
	velocity.x -= run_speed

func _physics_process(delta):
    get_input()
    move_and_slide()

where I posted the videos. I couldn't find it on any forum. Sorry

SnapCracklins

PriestSoryu post code and you're more likely to get an answer. A video is great but it's hard to determine what's up without seeing what's under the hood....

My initial thought is.... are you multiplying the movement by delta?

xyz

PriestSoryu Is vsync disabled?

PriestSoryu

SnapCracklins I posted the code too

PriestSoryu

SnapCracklins yes, it's all inside _physics_process(delta)

SnapCracklins

PriestSoryu yeah but you're not multiplying by delta. That's why you're stuttering. Multiplying the movement by delta smoothes the movement between frames. You're not multiplying the movement in the process so the movement is updated by frame-by-frame but it's not taking mind of the gap between.

Add an empty vector2 at start for your velocity variable.
You need to input your velocity into move_and_slide().

func _physics_process(delta):
    get_input()
    velocity = velocity * run_speed * delta
    velocity = move_and_slide(velocity)

PriestSoryu

xyz
No, it is enabled

xyz

PriestSoryu Profile it. If there are no drops just give the engine more to do 🙂

xyz

PriestSoryu What's your monitor's refresh rate? Your code is fine btw.

PriestSoryu

SnapCracklins
the last line gives an error.

I use godot 4.1

PriestSoryu

xyz 60hz. It's a 4K TV (temporary)

I tested with an executable from the project, the problem persists as well.

xyz

PriestSoryu Make sure that physics ticks in settings/physics/common matches the monitor refresh rate.

PriestSoryu

xyz it's like this

xyz

PriestSoryu I'm out of ideas then. Try to plug your computer into friend's monitor and vice versa to determine if the problem is indeed with monitor or hardware.

Also, as a test, try closing all other hardware accelerated viewports that may be running in your system, including ones in web browsers.

PriestSoryu

xyz I tried, the problem persists. On a friend's PC, the problem seems to be more pixel ghosting, from what I've seen.

I tried to delete everything from Godot and download it again, I created a basic project with a script pre-generated by the engine, nothing.

Godot seems like a great engine, but without a solution to this case, I believe I'll have to go back to Unity. Thanks for trying to help

Armynator

It looks like you are running your movement code in _physics_process, which is usually correct. This will cause jittering by default however, as the physics updates don't match the other game logic/render updates. I don't think there is 2D physics interpolation built into Godot 4 yet.

If that's the case I see 2 simple options:

interpolate, using this addon for example: https://github.com/lawnjelly/smoothing-addon (make sure to use the 4.X branch if you are on that version)
increase the physics update rate to at least double your render rate (not really recommended and only will make it less noticable)

PriestSoryu

Armynator I tested and nothing. So if I configured it wrong, but I don't think so, because the project that comes with it also gives some jitters

I really have no idea why this is happening on my PC. Maybe it's Windows 11? I do not know who knows

AlexanderGodot

try this one

extends CharacterBody2D
var run_speed = 35

func get_input():
velocity.x = 0
var right = Input.is_action_pressed('ui_right')
var left = Input.is_action_pressed('ui_left')

if right:
	position.x += run_speed
if left:
	position.x -= run_speed

func _process(delta: float) -> void:
get_input()

PriestSoryu

AlexanderGodot test it and it stays the same

AlexanderGodot

sorry I physically had a hard time seeing it. I tried to make it worse on mine by changing the background color to white and the player to red. I did a lot of things to make it worse, but I think I can help.
`
extends CharacterBody2D
var run_speed = 200

func get_input():
var right = Input.is_action_just_pressed('ui_right')
var left = Input.is_action_just_pressed('ui_left')

if right:
	position.x += run_speed
if left:
	position.x -= run_speed

func _process(delta: float) -> void:
get_input()`

so this should be redrawing the player to the screen in a new location each process time no ghosting and no jitters. I did a lot of things to make it worse. it was then I learned "is_action_pressed" is not just one hit but more like a bunch of them to smooth it out but "is_action_just_pressed" is more like hit once. that smooth it out means really fast draw of few a ghost till it gets to the end of the smooth. when the ghosting is not such a great distance it looks like jitters or a blurring of the player. it's just "is_action_just_pressed" is like a old school arcade button at pizza hut, it's press press press not a comfy hold.

PriestSoryu

AlexanderGodot I can't say if it's improved or not, because now to move the character I have to press the button several times, which makes everything useless.

Apparently it's only on my machine that this happens, I have no idea why. Something like this has never occurred to me in any other engine I've used, such as unity and game maker.