Видео

i got most of it working great in my game, who i have run into an issue, where if a juggle to fast on stairs or not even fast just move up and down, the camera compleatly miss alings it self, to the point of looking inside walls objects, idk whats happening with it COULD be because my general base player controller is different but idk because the movment works fine only the camera that bugs

Thank you so so so much

So this video is already deprecated due to the experimental nature of Godot, rotate_x is no longer a supported method. It is now rotate(), E.G. $Camera3D.rotate(Vector3(1, 0, 0), -event.relative.y * look_sensitivity) would have been nice, if they slowly phased out old methods, instead of dropping them next update lmao

Hey this tutorial has been exactly what i have been looking for thank you sir, i just have a question. Im porting this to 2D and when you set the expected motion variable to multiply delta by x and z, you say this is a 'forward' motion but I thought that the Z axis is the one which controls back and forth movement and the X is for left or right, can anyone help clarify? I appreciate it

great explanation, and another useful way to understand the basis is to think of it like defining where the xyz axes point to. This is useful if you use a sum of unit vectors to define vectors like you do in math; so eg. (1,2,3) would be 1i + 2j + 3k, where ijk are the xyz axes. The basis actually defines what these ijk vectors mean, so eg. if they aren't scaled nor rotated (in sync with the global coordinate system), then i would be (1,0,0), j would be (0,1,0) and z (0,0,1).

Thanks! :)

how do i turn while jumping with just mouse movement? i dont want to hold strafe keys while doing this

I'm a little confused as to how the air_cap, air_accel and air_move_speed variables are affecting the air strafing. Right now it feels like I can accelerate way too fast and turn way too far without a speed penalty.

If you plan to use Stairs inside of a GridMap3D node, you can swap out CSGMesh3D with GridMap or add it as a 3rd check instead like this: and (down_check_result.get_collider().is_class("StaticBody3D") or down_check_result.get_collider().is_class("GridMap") or down_check_result.get_collider().is_class("CSGShape3D"))):

works flawlessly! i also strict height of collision with [if self.global_position.y - get_slide_collision(clsns).get_position(cldrs).y < 0.9:] so i got no issues with walking on little objects

Very Geat tutorial. I works very good for me. Also, I have noticed when I try to walk up the stairs while im sided by two walls and face to the wall slightly i will stop moving. If I face staight i will work but being some angles off it will not. Do you know why this is happening and how I could fix it? If you dont no problem. And thank you for the tutorial it realy helped me.

I want to limit the players bhop speed but keep the speed in air uncapped so surfing etc isn't effected. The player should still be able to exceed the max speed cap in air through strafing but be set back to the threshold after touching the ground. Tried to implement it myself but it felt unsmooth as the change in speed was really noticeable. Dont want the player to go to fast.

Hi . Could this addon have feature optionally creation: 1 generate rooms without connections to main net? 2 generate main net within designated 3D area (sphere or similar shape) 3 generate hidden corridors and rooms I want to make some kind of Asteroid Base and have some empty space cells outside the main body of the asteroid formation. And inspect asteroid from outside and like "it could be secret room somewhere in this area" and when dig my way (dynamically geo-modification) to it to have some loot.

super clear explanation, best one I've seen so far!

i was using your tutorial to help with the stairs. i saw the _physics_proccess function and from fear that my code was missing something important i got into writing it down. Well my stupid but realized that this function is the exact same as the one i already have. Always preread before typing it down ig

This is a similar method to what I'm working on. Any progress?

Thanks for this. I used it for the GMTK game jam.

im trying to get this code to stop working if the player is above or on top of the object because if i stand on an object they will start to get impulses until the object like explodes and i go flying off of it lol UPDATE: put this after push_dir for more better accurate results without glitches and launching in the air if abs(push_dir.y) > 0.1: # Adjust this threshold if needed continue

major issue with the non-jolt physics here: landing on top of the beginning edge of a prop gives the player's velocity as a torque on said prop because the character is stepping up with its horizontal speed unchanged. It's pretty easy to move heavy af objects using this method. I kind of want to keep it, but it goes away with any hitbox with a flat bottom, so I may just give up and use a cylinder hitbox.

I noticed an issue the other day when implementing this: uncrouching in tight spaces does NOT retain crouch speed. I'm commenting this without actually knowing a solution, gonna look for it now.

If I wanted to make strafing and back-stepping at two different speeds than the forward movement, what would be your method to change the code? I did it my own way, but I don't believe it's anywhere near the ideal method (I changed the accel, decel, and speed values based on the inputs in the get_move_speed function. I also have a walk variable, making the code lengthy with 12 elif statements.) On the bright side, the way I did it allows for a highly refined movement system (I thought changing the friction would be redundant, but I'm thinking about changing the jump height.)

High quality content. Thanks

This gave me a lot of inspiration, I'm using a very different algorithm for procedural generation with UE5. However, the verticality is amazing, and I really want to make it a part of my design one way or another.

you said the word "prefab" . I wonder do you have a background in architecture or construction?

I've noticed two issues for devs wanting specifically good controller support. The controller look is the easiest to fix, just make sure that the turn direction is always the same as input. This is the specific changes I made to the code: - - - - - - - - var target_look = Input.get_vector("look_left", "look_right", "look_up", "look_down") # set _cur_controller_look in target_look's basis var _cur_look_at_target = target_look.normalized() * target_look.normalized().dot(_cur_controller_look) if target_look.length() < _cur_look_at_target.length(): _cur_controller_look = target_look else: _cur_controller_look = _cur_look_at_target.lerp(target_look, controller_aim_accel*delta) - - - - - - - - The first line takes away the normalized function call for target_look to allow for slight turns with the stick. The _cur_look_at_target is the component of _cur_controller_lool that is in the direction of the player's stick aim. I may have not done this in the best way, but it works nonetheless. The if statement is only changed by using _cur_look_at_target instead of _cur_controller_look for the comparison and lerp call. All this change does is ensure that the aim is always in the right direction, making tight and micro aim more consistent and less laggy. As for the controller move, the first change I made in _physics_process(delta) was similar to the look change in that I removed the normalized call, but I also added an if statement to make sure that the input is normalized when above a length of 1 to keep keyboard input the same: - - - - - - - - var input_dir = Input.get_vector("move_left", "move_right", "move_forward", "move_backward") if input_dir.length() > 1: input_dir = input_dir.normalized() - - - - - - - - As for the actual physics, I found that the grounded movement was the only actually problematic code, and it took me a while to figure out what felt best. First, the speed cap needed to be scaled to move input, but the input ended up having worse deadzones than before. What ended up being the issue there was the ground_decel variable, specifically when used to calculate the control then drop then new_speed variables. What I ultimately did was just remove the variable when there is movement input. Sounds bad, but it ultimately gets replaced with self.velocity.length(), so it works as intended at higher velocity while still stopping the player on a dime when letting go of move input. Here's the specific code I changed in _handle_ground_physics(delta): - - - - - - - - var add_speed_til_cap = (get_move_speed() * wish_dir.length()) - cur_speed_in_wish_dir . . . var new_ground_decel := 0.0 if wish_dir.length() <= 0: new_ground_decel = ground_decel var control = max(self.velocity.length(), new_ground_decel) - - - - - - - - It really isn't the most elegant solution, but I just wanted a quick and effective one for my needs. All these changes makes the controller input feel like it was actually built to work with controller. p.s. I also found an issue with the stair step functionality in a later video where the controller will stop on stairs that run up along a ledge or even if it has a railing as if the check is happening above that ledge/railing, but I haven't looked into a solution ,yet, nor whether you already fixed it in a comment.

9:47 the acronym you were looking for was constructive solid geometry ;)

How would I go about removing b-hopping if I didn't want my game to have it?

since this is an FPS tutorial series, will there ever be a weapon system, or will it just be movement related?

Is there any way for me to directly copy and paste all the code because it’s taking me way to long to write it down

I’m guessing it would work the same for 3rd person?

Great tutorial, The only problem I have is when ever I land after surfing or run into a wall while bhoping my character gets stuck in MOTION_MODE_FALLING.

39:45 I know you have updated tutorials but it seems like this is still your solution. Since I don't need full on surfing in my project, I'm gonna omit this. Definitely find a new solution if you can though, I can easily imagine a bug that gets you stuck in floating mode. Look up the Red Letter Day skip in Half-Life 2 if you want to understand why this can be a SMALL issue. Fast Edit: It's not explicitly Red Letter Day I guess. Watch a Half-Life 2 speed run, it's very early on. You're looking for them to jump off a roof onto a street that should definitely kill the player, and then they'll rub up against a car for a little bit. Then something MAGICAL happens.

I was stuck on this for ages, the main reason was the tonemap and the viewport size. Your method of reversing the transform was so much better than mine, i was using a node3d to track the players position local to the portal but did not work out so great. Unfortunately while this looks amazing in flat 3d, in vr the shader is ran twice in one frame causing a weird duplicate effect, i am yet to figure out a solution but this is amazing work keep it up

wish_dir = self.global_tranform.basis * Vector3(-input_dir.x, 0., -input_dir.y)

I've been having an issue where godot does not recognise the the function get_move_speed() , despite it being used in the advanced movement + friction section of the video, do you know why this could be happening and do you have any advice that could help? Thanks

This video is an answer to my prayers. 🙏 Thank you.

This is easily the best first person character controller tutorial for godot on RUclips, seriously! You have no idea how helpful this was, cheers.

Very interesting!

Bro can u pls give tutorial on arcade bike and car physics with code 😢 in Godot pls im a beginner and struggling.

An extra version that only contains the important code would be helpful. This way you would have to remove the noclip code etc. in a cumbersome way

If you try to create your own implementation, based on this video you may get weird culling artifacts. The problem is that AABB (bounding box) is incorrect, since the default “box” has no height, because the original plane mesh didn’t have any. To fix the issues you will need to create a new AABB and assign it to the “custom_aabb” property of each of the meshes. You can simply copy the default AABB, but set the vertical (Y) size to the max possible height, of the terrain that you are generating.

The SeparationRayShape3D solution has sounded preposterous to me for a long time, but... recently I noticed that Thief has used this method (well, 99% similar), and it actually never really bothered people much. There are of course a few issues, but it's not as bad as I thought, and for some games it's not really a problem at all. For example, I'm considering using it for horror games that don't require much ground precision. I just need to learn how to make it stick to the floor when climbing down steps, as well as how to smooth the camera. This method actually has a couple of upsides: it's simple (I think), and it prevents climbing on wall baseboards, and things of that nature. If I had a dollar for every time I had to create clip brushes in maps I made to prevent players from inadvertently climbing onto such things...

wow it is so good

Amazing tutorial! I didn't even consider Shapecasts or using signals for the components! Personally, I made InteractableComponent inherit Area3D so I can choose a custom hitbox for the interact zone which doesn't have to be the object's solid collision (small items on the ground may have no collision but large interact zones).

thanks loved learning this!

I'm looking to have one size room that's open no walls with stuff in them, put together to make one big endless room but two floors. If I could use you add on that would be great but what should I be looking for to learn how to do this.

Thanks, this worked great and was exactly what I needed. No other good answers for this that I could find.

trash!

how would you go about placing interactable doors between rooms? again great work

Great tutorial! Thank you! It helped me a lot. Only left to fix animation issues due to my 3d person controller