Maybe should process trees in _physics_process() instead of in _process() about addons-btree HOT 7 CLOSED

Another approach is let the user define it. For example:

# btree.gd

export(int, '_physics_process', '_process') var run_on = 0

func _physics_process(delta):
	if run_on == 0:
		tree_process(delta)
	
func _process(delta):
	if run_on == 1:
		tree_process(delta)

from addons-btree.

Most of the time we use btree as decisions maker. the actual physics stuff is must decouple from ai stuff. Running ai at the same rate as physics is not necessary. If it a must to query from physics the query must perform in physics tick and saved as cached. Also Godot fixed step is not fixed at all. If you have heavy physics simulation the step maybe drop from actual step.

from addons-btree.

I was wondering of it because I found a bug in the https://github.com/fian46/demo-btree.
If you walk fast at same direction that you fire, the bullet will collide with the own player.
In this case, your tasks seems to be dependent of physics calculations.
When I tested with btree running on _physics_process () the bug doesn't happen.
But perhaps there is another way to solve this problem.

from addons-btree.

What do you think about the idea of letting the user choose? We could make the option run_on = '_process' by default

from addons-btree.

It is not a bug the implementations is not complete. But sure if you think it is necessary to give user options for choose the best setup.

from addons-btree.

Submitted a PR #9

from addons-btree.

Merged

from addons-btree.