Spawned object moved delayed

CodeMiner

I'm learning and creating my fist game - space asteroid shooter. I have a problem with spawning asteroid. This is my scene cdoe

extends Node2D

onready var small = preload("res://Scenes/SmallAsteroid.tscn")

func _ready():
	var timer = Timer.new()
	timer.set_wait_time(rand_range(0, 3))
	timer.set_one_shot(false)
	timer.connect("timeout", self, "add_asteroid")
	add_child(timer)
	timer.start()

func add_asteroid():
	add_child(small.instance())

and this is my asteroid code:

extends RigidBody2D

export (int) var MAX_SPEED = 1
onready var viewportSize = get_viewport().size

var destinationPoint = Vector2.ZERO

func _ready():
	position = Vector2(rand_range(-400, 400), rand_range(-400, 400))
	destinationPoint = Vector2(rand_range(-400, 400), rand_range(-400, 400))

func _process(delta):
	position.x += destinationPoint.x * MAX_SPEED * delta
	position.y += destinationPoint.y * MAX_SPEED * delta

What is the effect in the game ?

Asteroid is spawn every 1 second, then they wait 1 second and then they move. But why they wait additional second to move ?

Bimbam

I just tried your code and am not getting the same issue.

Asteroids spawn and move immediately, nothing is stationary for any amount of time.

newmodels

The only delay I can see is maybe one frame.

Bimbam

Ah, could have something to do with applying movement directly to a RigidBody (which you are not supposed to do).

I didn't use a RigidBody node, so perhaps the quirk never showed up.

CodeMiner

I will add link to github repo evening today, or maybe I will find solution

CodeMiner

Ok here is link to repo and to specific script that move the asteroids: https://github.com/CodeMiner84/godot-space-shooter/blob/master/Scripts/SmallAsteroid.gd

Megalomaniak

Link doesn't work, if I had to guess, because the repo is not accessible.

CodeMiner

ahhh indeed, it's public now

Megalomaniak

from RigidBody2D nodes docs as per link provided by @Bimbam above:

Note: You should not change a RigidBody2D's position or linear_velocity every frame or even very often. If you need to directly affect the body's state, use _integrate_forces, which allows you to directly access the physics state.

Please also keep in mind that physics bodies manage their own transform which overwrites the ones you set. So any direct or indirect transformation (including scaling of the node or its parent) will be visible in the editor only, and immediately reset at runtime.>

If you need to override the default physics behavior or add a transformation at runtime, you can write a custom force integration. See custom_integrator.