Movement is Hard

Рет қаралды 992

Күн бұрын

Пікірлер: 10

@DSoulless 3 ай бұрын

Something that's always ticked me off is when gamers and companies but mainly gamers get mad at game studios for taking to long to develop game it's a long, painful, and tiring process to right code and constantly have to test over and over each time you add a new line of code to make sure it works and didn't break any of your previous lines of code it sucks because most studios are given deadlines they have to meet and most of the time they can't meet them and sometimes they can but they didn't have the time to test, fix bugs, and perfect the code and mechanics and they end up disappointing their community's because they just don't have the time especially with the requirements of games now adays and that's why indie devs thrive as thy don't have those absurd requirements and deadlines as they are their own bosses

@bobbywalden9818 3 ай бұрын

Genuinely impressed with how much detail is never really considered in game dev, even for the simple concept of movement. REALLY makes you appreciate the tools that those other programs provide. Great video!

@Axisok 3 ай бұрын

It's much easier to get direction inputs by using var input_dir = Input.get_vector("move_left", "move_right", "move_forward", "move_back"), which combines all directions and limits the magnitude to 1 all in a single line. To translate it into world coordinates, I think all you have to do is var input_v = input_dir.x * transform.basis.x + input_dir.y * transform.basis.z, different variable because that's a Vector3 and the other was a Vector2. I'd also avoid using speed for acceleration and instead have a velocity variable, since speed is a float variable with no sense of direction. To accelerate, we add input_v * acceleration * delta, keeping in mind that acceleration is expressed in m/s². If you don't plan on ever letting the player move faster than move speed, all you need to do is limit the velocity magnitude (with Vector3.limit_length(float)) to move speed after adding acceleration. For friction/deceleration, add an opposing force at the beginning of the frame that tries to bring velocity closer to 0 if the player is in contact with the ground. CharacterBody3D already has a velocity variable, which is what you should use for moving around (along with move_and_slide()). Not sure if it's the best way to do it, I only played with Godot very casually so I wouldn't know. Still, movement is easy, at least for simple stuff like that.

@RoyaltyInTraining. 3 ай бұрын

The linear algebra courses in college genuinely helped me get a really good intuition for all this stuff Edit: I would encourage you to look into building quaternions from euler angles. Quaternions themselves are actually quite often constructed from them in games, since using their four axes directrly is so utterly unintuitive. As long as you limit yourself to standard FPS camera controls in two axes and never attempt to concatenate euler rotations without converting to quaternions first, you will never run into gimbal lock issues. You need to look out for the order of operations your engine uses, and you might have to choose that on a case by case basis.

@necoluga7950 3 ай бұрын

Yeh lol i studdy math and once i started programing games and concepts such as vectors are intuitively aplyed in alot of places.

@goofydudeguya 3 ай бұрын

Thanks for the input! I understand that it would be very beneficial to eventually utilize quaternions in 3D games. The idea of converting eulers to quats sound like a much better way of using them then trying to understand their application directly. 😅 P.S. Please bear with me since I don't have any formal education in these higher math concepts. I'm running off of self-taught experience and stuff from high school LOL.