Post by atornity in godot recoil system comments

Viewing post in godot recoil system comments

glad you liked it! I see you figured it out already witch is great. The way I would do it is a bit different.

for move left/right I would use "camera.basis.x" as the move direction. for forward/backward I would use "player.basis.y.cross(camera.basis.x)".

which might look something like:

var input: Vector2 = Input.get_vector(...) # replace '...' with move input mappings

var forward_axis: Vector3 = player.basis.y.cross(camera.basis.x)

var right_axis: Vector3 = camera.basis.x

var move_vector = input.x * forward_axis + input.y * right_axis

player.move(move_vector * speed)

I personally prefer to keep the camera rotation completely separate from the player rotation but that's completely up to you of course :3

adocii1 year ago (1 edit) (+1)

I see that's very interesting. are there any benefits to keeping the rotation of the player and the camera separate?

atornity1 year ago (1 edit)

1. it allows your camera script to exist without having a reference to a player. Which might be useful sometimes.

2. camera node does not have to be a child of the player node (although it can still be if you want)

3. for first person games, it allows you to attach a legs/feet mesh to your player without it being dependent on the rotation of the camera.

4. for third person games, it allows for more smooth camera movement where the camera isn't actually attached to the player (2). It also allows the player to have a different rotation from the camera which is very common for third person games.

5. it allows you to use the same camera script for first person games and third person games. (and other types of games probably)

It's all kind of small benefits that can be easily worked around. In the end it comes down to personal preference more than anything :3

itch.io

Viewing post in godot recoil system comments