How do I implement context-based steering AI in 3d?: Page 2

How do I implement context-based steering AI in 3d?

Audiobellum

@fire7side

That looks cool. Even though I don’t think there is nothing wrong with your code, I have a hard time understanding it and therefore I can’t make changes to it that would help me. It’s a possibility that I could have placed the wrong directions in the direction variables. Still, I feel like I'll have a hard time solving this problem in the future, if it were to arise again, if I don't know what I'm doing now. I have other questions about your code but, for now, could you test the code for my raycast_generator on your end to so what could be going wrong?

fire7side

I'll try to take a look like tomorrow or something. I'm a little bit burned out on it.

Audiobellum

@fire7side

Hi, it's me again. So I was working on an alternative solution that is incredibly simple, noob friendly and only required one ray cast( So it's less taxing on the hardware). Here is what came up with: extends KinematicBody

onready var raycast = $RayCast;onready var eyes = $Eyes
onready var anim_player = $AnimationPlayer; var target

export var sweep = 0;var sweep_range = 90; var ray_length = -5
var health = 100;var speed = 5;var turning_speed = 10
var direction = Vector3();var fall = Vector3()
var gravity = 9.8

func _ready():
	yield(owner,"ready")
	target = owner.point

func _process(delta):
	if health < 50:queue_free()
	patrolling()
	if not is_on_floor():fall.y -= gravity * delta #Code for gravity.

func move_foward(speed = 7):
	direction -= transform.basis.z;direction = direction.normalized()
	move_and_slide(direction * speed, Vector3.UP,true)

func sweeping():
	sweep = wrapi(sweep + 30,-sweep_range,sweep_range)
	raycast.rotation_degrees.y = sweep

func patrolling():
	move_foward(speed)
	if not raycast.is_colliding():sweeping()
	else:avoid_obstacle()
	move_and_slide(fall, Vector3.UP)

func avoid_obstacle():
	if raycast.rotation_degrees.y < 0:rotate_y(deg2rad(turning_speed))
	elif raycast.rotation_degrees.y >= 0:rotate_y(deg2rad(-turning_speed))

Now here is what it looks like in action:

Now the biggest problem with my approach is that I haven't figured out how to make my "AI" chase down a target while avoiding obstacles. If I don't find a way to make the enemy avoid obstacles while chasing down a target, I might have to scrap this idea. I've just started brainstorming on how to solve this problem but, I also want to ask what do you think. Do you know of a simpler solution on how to get the enemies to avoid obstacles while chasing down a target?

Audiobellum

@fire7side

Hmm...I think I've found it. Check this function out:

func chasing():
	var distance = transform.origin.distance_to(target.transform.origin)
	if target != null and distance > 1:
		move_foward(speed)
	if not raycast.is_colliding():
		if target != null:look_at(Vector3(translation.x,target.translation.y,translation.z),Vector3.UP)
		sweeping()
	else:avoid_obstacle()

Edit: I was wrong. :/

Edit again: Okay, so I made a small adjustment to my avoid_obstacle() script. I hope it will help. It goes like this:

func avoid_obstacle():
	if raycast.rotation_degrees.y < 0:
		rotate_y(deg2rad(turning_speed))
		direction -= transform.basis.z
	elif raycast.rotation_degrees.y >= 0:
		rotate_y(deg2rad(-turning_speed))
		direction += transform.basis.z

fire7side

Let me know if you get it working so it moves to a target and avoids enemies. Yeah, 8 raycasts isn't bad, but if you have a lot of ai it would add up. There are probably a lot of ways of solving it, but I don't know how just one would be enough unless it was doing a sweep and that's basically the same thing. I'm kind of working on a game where I can actually try it out in a little bit. I wonder why it's not used much? I know the pathfinding from Godot is established, but it requires baking and probably wouldn't work in an open world. Although it is much more accurate for things like maze situations. Anyway, it was interesting looking at that solution and I learned some new things.

Audiobellum

@fire7side

I think I'm dangerous close to finding a solution to the problem but, it involves having some sort of variable that sorts information about where the player( or target) is relative to the target. After that, I can have that information constantly updating other variables that need to be updated. I'll be back to show you what I have working so far and why it doesn't work all the time; I'll even back more video evidence. I think that both of us are on to something great but, I think you might have the solution. I suspect that the solution involves the Dot Product function but, I don't fully understand it or what it does, so I can't say for certain. See you tomorrow.

Audiobellum

@fire7side

Hi I'm back. Sorry for taking so long to return; I was fighting my internet connection the entire day and it almost won. Here is a video demonstrating my AI chasing a target while avoiding obstacles:

Now the AI is far from perfect and I wish I could even show some footage of it failing. However, I'm tired now. Instead, I'll settle for telling you the limitations of this AI tomorrow. I'll also ask about the limitations of your AI as well, to see to what extend the limitations overlap and how they can be solved.

fire7side

One thing that occurred to me is I might have an oblong object, like a car, which probably won't work, or will need modification. To tell the truth though, I decided to just use a plain path follow in my airplane game because I decided to do a reverse tower defense game, where the monsters are sort of towers and the airplane has to take them out before they shoot all the cars with xray vision. But yeah, I didn't test it much beyond that little video. Have to wait for another project. I still may use it on the monsters. Have them travel a little bit.

« Previous Page