Why the print of global_position changes my body behaviour?

Help Programming
1

Godot Version

Godot 4.3

Question

Hi everyone! I am trying to move a RigidBody2D over a Path2D. However, I get a very strange behavior. When I print the global_position of my collider all seems to work fine. However, If I don’t do that, the collider seems to be still. Any clue?

I have a Node that has 2 childs: a Path2D and a RigidBody2D that has an animated sprite and a collisionShape2D.
Here the function:

func _process(delta: float) -> void:
	pathFollow.progress_ratio += current_direction * delta * speed/100
	if(pathFollow.progress_ratio == 0 || pathFollow.progress_ratio == 1):
		current_direction *= -1
		$Body/AnimatedSprite2D.flip_h = !$Body/AnimatedSprite2D.flip_h 
	body.position = pathFollow.position
	print("body position ", body.position)
	print("collision shape ", $Body/CollisionShape2D.get_global_position())

If I comment out the second print (last line) the collisionShape seems to remain still. Shouldn’t the get_global_position() be const? Thank you!

2

That line should not have any impact on the movement of your shape.
The only thing I can think of is that the print statement eats a few blips of time and maybe allows a screen refresh or something like that.

1 Like
3

Is your RigidBody2D frozen?

Manually moving a physics body can cause issues for the physics server. So my first thought is that it is kinda working my coincidence when that print line exists.

I’m doing a similar thing (in 3D) and I have:

  1. RemoteTransform3D as a child of a PathFollow3D
  2. RemoteTransform3D has it’s remote path set to a RigidBody3D
  3. RigidBody3D has props:
    3.1 freeze = true
    3.2 freeze mode = RigidBody3D.FREEZE_MODE_KINEMATIC
    3.3 top level = true

This seems to be allowing me to move the RigidBody3D around the path without any issues.

Not sure if this is helpful, but thought I’d mention as it sounds like you are trying to accomplish the same thing I’ve done.

1 Like
4

Hi! My RigidBody2D is not frozen. However, I agree that the issues are due to the wrong way I’m moving the body :frowning: I solved the issue using a CharacterBody2D (and later still, not using path2D for this feature :smiley: ).
Thank you, I will be more careful when moving stuff!

1 Like