How to move the player while also allowing forces to affect it





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







7












$begingroup$


For now, that's how I move the player:



rb.velocity = Vector2.right * input.x;


And I affect him a force while he is damaged by an entity:



rb.AddForce(Vector2.right * force);


It works fine, until I try to move while I'm damaged by an entity.
Since my velocity = input.x while I move, I can't affect any forces to it.
I've tried to summarize velocity:



rb.velocity+=Vector2.right * input.x;


But then I need to clamp the speed and if I clamp it, my force which is affected to player is also clamped.



How can I resolve this problem?










share|improve this question











$endgroup$



















    7












    $begingroup$


    For now, that's how I move the player:



    rb.velocity = Vector2.right * input.x;


    And I affect him a force while he is damaged by an entity:



    rb.AddForce(Vector2.right * force);


    It works fine, until I try to move while I'm damaged by an entity.
    Since my velocity = input.x while I move, I can't affect any forces to it.
    I've tried to summarize velocity:



    rb.velocity+=Vector2.right * input.x;


    But then I need to clamp the speed and if I clamp it, my force which is affected to player is also clamped.



    How can I resolve this problem?










    share|improve this question











    $endgroup$















      7












      7








      7


      6



      $begingroup$


      For now, that's how I move the player:



      rb.velocity = Vector2.right * input.x;


      And I affect him a force while he is damaged by an entity:



      rb.AddForce(Vector2.right * force);


      It works fine, until I try to move while I'm damaged by an entity.
      Since my velocity = input.x while I move, I can't affect any forces to it.
      I've tried to summarize velocity:



      rb.velocity+=Vector2.right * input.x;


      But then I need to clamp the speed and if I clamp it, my force which is affected to player is also clamped.



      How can I resolve this problem?










      share|improve this question











      $endgroup$




      For now, that's how I move the player:



      rb.velocity = Vector2.right * input.x;


      And I affect him a force while he is damaged by an entity:



      rb.AddForce(Vector2.right * force);


      It works fine, until I try to move while I'm damaged by an entity.
      Since my velocity = input.x while I move, I can't affect any forces to it.
      I've tried to summarize velocity:



      rb.velocity+=Vector2.right * input.x;


      But then I need to clamp the speed and if I clamp it, my force which is affected to player is also clamped.



      How can I resolve this problem?







      unity 2d physics rigidbody






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday









      Alex Myers

      343110




      343110










      asked yesterday









      Basea BasiliaBasea Basilia

      5216




      5216






















          3 Answers
          3






          active

          oldest

          votes


















          5












          $begingroup$

          You're on the right track! This is something that usually the controller is responsible for. When you jump in a platformer you use a "isGrounded" variable to change how the controls behave while in the air right? You need a similar state for isKnockback. In most games when a player is knocked back, they have control striped from them for a certain amount of time. That or you treat it like being airborn where instead of setting velocity it will just apply a force to adjust the velocity. How you want to implement that control is a design choice, but there is no real physics based answer. The true physics based answer is implementing locomotion in the character's legs and that's not really useful for game physics. Another solution could be instead of applying a force, is to work with knockback at a velocity level like your movement. Apply a velocity, and reduce it by some amount each fixed update to simulate a knockback like effect. This is another common solution in the industry.



          Edit: Just to credit the other answers here, they mention making your movement acceleration / force based. This is also an option, depending on the kind of motion you want. This approach is far more intuitive but gives you a lesser degree of control. It all depends on what you want, and it's important you make that decision early (or experiment if you're not sure) because it will impact decisions further down the line. If you want to see how crazy some platforming code can get, Matt released the code for Madeline from Celeste. They use a different engine (framework actually) but you can get the jist of how many variables and pseudo physics were used to achieve that feel. https://github.com/NoelFB/Celeste/blob/master/Source/Player/Player.cs






          share|improve this answer











          $endgroup$













          • $begingroup$
            Thank you, it's done by check true isKnockback when force is applied and check false when player will collide with ground next time, it works very fine
            $endgroup$
            – Basea Basilia
            yesterday










          • $begingroup$
            Glad to hear it. In general don't be afraid to fake physics in your games. Lots of engines have these awesome realistic physics, but in many game scenarios people just end up faking most of it :)
            $endgroup$
            – gjh33
            yesterday



















          9












          $begingroup$

          I created a little demo game a few days ago which demonstrates different ways to move a player-character. It might help you to better understand which way of moving is the right one for your particular game.



          In general, you should use rigidbody.AddForce whenever feasible. It automatically takes care of managing multiple overlapping forces and ensures that the transfer of momentum on collisions is physically correct.



          If you don't want your character to be able to accelerate indefinitely, increase the "Linear Drag" value of the rigidbody. The drag force increases quadratically with the velocity, so at some point it will cancel out the acceleration and effectively limit the maximum speed. A larger drag value will result in shorter acceleration and deceleration times, making the controls feel more "tight", but also greatly limit the effect of collisions.



          If you want the character to have tight controls but also be affected by collisions, you could handle this the way the answer by gjh33 suggests. Have two different states in your player-controller. A regular state where the rigidbody has high drag and the player has full control force, and a "just got hit" state where you reduce the drag and the control force temporarily in order to make the character fly around in a temporary state of uncontrolled helplessness.



          I am looking forward to playing your game.






          share|improve this answer











          $endgroup$





















            4












            $begingroup$

            Myself, I like to solve this by thinking of all player movement as acceleration-based.



            I choose a target velocity using whatever complicated control logic I like, then ask the player avatar to accelerate toward that target, while respecting maximum acceleration rates I set.



            Then, depending on the avatar's state (on ground, on ice, in the air, in a knockback state), I can change those acceleration rates to make the control input have a sharper or less pronounced impact.



            Rigidbody2D body;

            void AccelerateTowards(Vector2 targetVelocity, float maxAccel, float maxDecel) {
            // Compute desired velocity change.
            var velocity = body.velocity;
            var deltaV = targetVelocity - velocity;

            // Convert our velocity change to a desired acceleration,
            // aiming to complete the change in a single time step.

            // (For best consistency, call this in FixedUpdate,
            // and deltaTime will automatically give fixedDeltaTime)
            var accel = deltaV / Time.deltaTime;

            // Choose an acceleration limit depending on whether we're
            // accelerating further in a similar direction, or braking.
            var limit = Dot(deltaV, velocity) > 0f ? maxAccel : maxDecel;

            // Enforce our acceleration limit, so we never exceed it.
            var force = body.mass * Vector2.ClampMagnitude(accel, limit);

            // Apply the computed force to our body.
            body.AddForce(force, ForceMode2D.Force);
            }


            Separating acceleration & deceleration rates like this lets me give a sharper braking force, which tends to help the controls feel tight & responsive when stopping or changing directions, while keeping a smooth acceleration for getting up to speed. It also lets you penalize braking specifically when on ice or being knocked back.



            We can make a control state parameters object to hold the max speed, acceleration, and deceleration rates for our air, ground, ice, knockback states etc. and use this to adjust our control handling very flexibly:



            // Choose our current speed / acceleration parameters based on our state.
            var controlState = GetCurrentControlState();

            // Compute desired velocity.
            var velocity = GetDesiredVelocityFromInput(controlState.maxSpeed);

            // Try our best to reach that velocity, with our current parameters.
            AccelerateTowards(
            velocity,
            controlState.maxAccel,
            controlState.maxDecel
            );





            share|improve this answer











            $endgroup$













            • $begingroup$
              does deltatime automatically give fixedDeltaTime in fixedUpdate loop? That's really cool! I know I used to have to code around that, do you know when they added that?
              $endgroup$
              – gjh33
              yesterday










            • $begingroup$
              I looked into it you're right. That's very useful. I don't remember that being a thing when I started working in unity, definitely makes reusing functions in different update loops way easier.
              $endgroup$
              – gjh33
              yesterday












            Your Answer





            StackExchange.ifUsing("editor", function () {
            return StackExchange.using("mathjaxEditing", function () {
            StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
            StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
            });
            });
            }, "mathjax-editing");

            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "53"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgamedev.stackexchange.com%2fquestions%2f169839%2fhow-to-move-the-player-while-also-allowing-forces-to-affect-it%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            5












            $begingroup$

            You're on the right track! This is something that usually the controller is responsible for. When you jump in a platformer you use a "isGrounded" variable to change how the controls behave while in the air right? You need a similar state for isKnockback. In most games when a player is knocked back, they have control striped from them for a certain amount of time. That or you treat it like being airborn where instead of setting velocity it will just apply a force to adjust the velocity. How you want to implement that control is a design choice, but there is no real physics based answer. The true physics based answer is implementing locomotion in the character's legs and that's not really useful for game physics. Another solution could be instead of applying a force, is to work with knockback at a velocity level like your movement. Apply a velocity, and reduce it by some amount each fixed update to simulate a knockback like effect. This is another common solution in the industry.



            Edit: Just to credit the other answers here, they mention making your movement acceleration / force based. This is also an option, depending on the kind of motion you want. This approach is far more intuitive but gives you a lesser degree of control. It all depends on what you want, and it's important you make that decision early (or experiment if you're not sure) because it will impact decisions further down the line. If you want to see how crazy some platforming code can get, Matt released the code for Madeline from Celeste. They use a different engine (framework actually) but you can get the jist of how many variables and pseudo physics were used to achieve that feel. https://github.com/NoelFB/Celeste/blob/master/Source/Player/Player.cs






            share|improve this answer











            $endgroup$













            • $begingroup$
              Thank you, it's done by check true isKnockback when force is applied and check false when player will collide with ground next time, it works very fine
              $endgroup$
              – Basea Basilia
              yesterday










            • $begingroup$
              Glad to hear it. In general don't be afraid to fake physics in your games. Lots of engines have these awesome realistic physics, but in many game scenarios people just end up faking most of it :)
              $endgroup$
              – gjh33
              yesterday
















            5












            $begingroup$

            You're on the right track! This is something that usually the controller is responsible for. When you jump in a platformer you use a "isGrounded" variable to change how the controls behave while in the air right? You need a similar state for isKnockback. In most games when a player is knocked back, they have control striped from them for a certain amount of time. That or you treat it like being airborn where instead of setting velocity it will just apply a force to adjust the velocity. How you want to implement that control is a design choice, but there is no real physics based answer. The true physics based answer is implementing locomotion in the character's legs and that's not really useful for game physics. Another solution could be instead of applying a force, is to work with knockback at a velocity level like your movement. Apply a velocity, and reduce it by some amount each fixed update to simulate a knockback like effect. This is another common solution in the industry.



            Edit: Just to credit the other answers here, they mention making your movement acceleration / force based. This is also an option, depending on the kind of motion you want. This approach is far more intuitive but gives you a lesser degree of control. It all depends on what you want, and it's important you make that decision early (or experiment if you're not sure) because it will impact decisions further down the line. If you want to see how crazy some platforming code can get, Matt released the code for Madeline from Celeste. They use a different engine (framework actually) but you can get the jist of how many variables and pseudo physics were used to achieve that feel. https://github.com/NoelFB/Celeste/blob/master/Source/Player/Player.cs






            share|improve this answer











            $endgroup$













            • $begingroup$
              Thank you, it's done by check true isKnockback when force is applied and check false when player will collide with ground next time, it works very fine
              $endgroup$
              – Basea Basilia
              yesterday










            • $begingroup$
              Glad to hear it. In general don't be afraid to fake physics in your games. Lots of engines have these awesome realistic physics, but in many game scenarios people just end up faking most of it :)
              $endgroup$
              – gjh33
              yesterday














            5












            5








            5





            $begingroup$

            You're on the right track! This is something that usually the controller is responsible for. When you jump in a platformer you use a "isGrounded" variable to change how the controls behave while in the air right? You need a similar state for isKnockback. In most games when a player is knocked back, they have control striped from them for a certain amount of time. That or you treat it like being airborn where instead of setting velocity it will just apply a force to adjust the velocity. How you want to implement that control is a design choice, but there is no real physics based answer. The true physics based answer is implementing locomotion in the character's legs and that's not really useful for game physics. Another solution could be instead of applying a force, is to work with knockback at a velocity level like your movement. Apply a velocity, and reduce it by some amount each fixed update to simulate a knockback like effect. This is another common solution in the industry.



            Edit: Just to credit the other answers here, they mention making your movement acceleration / force based. This is also an option, depending on the kind of motion you want. This approach is far more intuitive but gives you a lesser degree of control. It all depends on what you want, and it's important you make that decision early (or experiment if you're not sure) because it will impact decisions further down the line. If you want to see how crazy some platforming code can get, Matt released the code for Madeline from Celeste. They use a different engine (framework actually) but you can get the jist of how many variables and pseudo physics were used to achieve that feel. https://github.com/NoelFB/Celeste/blob/master/Source/Player/Player.cs






            share|improve this answer











            $endgroup$



            You're on the right track! This is something that usually the controller is responsible for. When you jump in a platformer you use a "isGrounded" variable to change how the controls behave while in the air right? You need a similar state for isKnockback. In most games when a player is knocked back, they have control striped from them for a certain amount of time. That or you treat it like being airborn where instead of setting velocity it will just apply a force to adjust the velocity. How you want to implement that control is a design choice, but there is no real physics based answer. The true physics based answer is implementing locomotion in the character's legs and that's not really useful for game physics. Another solution could be instead of applying a force, is to work with knockback at a velocity level like your movement. Apply a velocity, and reduce it by some amount each fixed update to simulate a knockback like effect. This is another common solution in the industry.



            Edit: Just to credit the other answers here, they mention making your movement acceleration / force based. This is also an option, depending on the kind of motion you want. This approach is far more intuitive but gives you a lesser degree of control. It all depends on what you want, and it's important you make that decision early (or experiment if you're not sure) because it will impact decisions further down the line. If you want to see how crazy some platforming code can get, Matt released the code for Madeline from Celeste. They use a different engine (framework actually) but you can get the jist of how many variables and pseudo physics were used to achieve that feel. https://github.com/NoelFB/Celeste/blob/master/Source/Player/Player.cs







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited yesterday

























            answered yesterday









            gjh33gjh33

            2664




            2664












            • $begingroup$
              Thank you, it's done by check true isKnockback when force is applied and check false when player will collide with ground next time, it works very fine
              $endgroup$
              – Basea Basilia
              yesterday










            • $begingroup$
              Glad to hear it. In general don't be afraid to fake physics in your games. Lots of engines have these awesome realistic physics, but in many game scenarios people just end up faking most of it :)
              $endgroup$
              – gjh33
              yesterday


















            • $begingroup$
              Thank you, it's done by check true isKnockback when force is applied and check false when player will collide with ground next time, it works very fine
              $endgroup$
              – Basea Basilia
              yesterday










            • $begingroup$
              Glad to hear it. In general don't be afraid to fake physics in your games. Lots of engines have these awesome realistic physics, but in many game scenarios people just end up faking most of it :)
              $endgroup$
              – gjh33
              yesterday
















            $begingroup$
            Thank you, it's done by check true isKnockback when force is applied and check false when player will collide with ground next time, it works very fine
            $endgroup$
            – Basea Basilia
            yesterday




            $begingroup$
            Thank you, it's done by check true isKnockback when force is applied and check false when player will collide with ground next time, it works very fine
            $endgroup$
            – Basea Basilia
            yesterday












            $begingroup$
            Glad to hear it. In general don't be afraid to fake physics in your games. Lots of engines have these awesome realistic physics, but in many game scenarios people just end up faking most of it :)
            $endgroup$
            – gjh33
            yesterday




            $begingroup$
            Glad to hear it. In general don't be afraid to fake physics in your games. Lots of engines have these awesome realistic physics, but in many game scenarios people just end up faking most of it :)
            $endgroup$
            – gjh33
            yesterday













            9












            $begingroup$

            I created a little demo game a few days ago which demonstrates different ways to move a player-character. It might help you to better understand which way of moving is the right one for your particular game.



            In general, you should use rigidbody.AddForce whenever feasible. It automatically takes care of managing multiple overlapping forces and ensures that the transfer of momentum on collisions is physically correct.



            If you don't want your character to be able to accelerate indefinitely, increase the "Linear Drag" value of the rigidbody. The drag force increases quadratically with the velocity, so at some point it will cancel out the acceleration and effectively limit the maximum speed. A larger drag value will result in shorter acceleration and deceleration times, making the controls feel more "tight", but also greatly limit the effect of collisions.



            If you want the character to have tight controls but also be affected by collisions, you could handle this the way the answer by gjh33 suggests. Have two different states in your player-controller. A regular state where the rigidbody has high drag and the player has full control force, and a "just got hit" state where you reduce the drag and the control force temporarily in order to make the character fly around in a temporary state of uncontrolled helplessness.



            I am looking forward to playing your game.






            share|improve this answer











            $endgroup$


















              9












              $begingroup$

              I created a little demo game a few days ago which demonstrates different ways to move a player-character. It might help you to better understand which way of moving is the right one for your particular game.



              In general, you should use rigidbody.AddForce whenever feasible. It automatically takes care of managing multiple overlapping forces and ensures that the transfer of momentum on collisions is physically correct.



              If you don't want your character to be able to accelerate indefinitely, increase the "Linear Drag" value of the rigidbody. The drag force increases quadratically with the velocity, so at some point it will cancel out the acceleration and effectively limit the maximum speed. A larger drag value will result in shorter acceleration and deceleration times, making the controls feel more "tight", but also greatly limit the effect of collisions.



              If you want the character to have tight controls but also be affected by collisions, you could handle this the way the answer by gjh33 suggests. Have two different states in your player-controller. A regular state where the rigidbody has high drag and the player has full control force, and a "just got hit" state where you reduce the drag and the control force temporarily in order to make the character fly around in a temporary state of uncontrolled helplessness.



              I am looking forward to playing your game.






              share|improve this answer











              $endgroup$
















                9












                9








                9





                $begingroup$

                I created a little demo game a few days ago which demonstrates different ways to move a player-character. It might help you to better understand which way of moving is the right one for your particular game.



                In general, you should use rigidbody.AddForce whenever feasible. It automatically takes care of managing multiple overlapping forces and ensures that the transfer of momentum on collisions is physically correct.



                If you don't want your character to be able to accelerate indefinitely, increase the "Linear Drag" value of the rigidbody. The drag force increases quadratically with the velocity, so at some point it will cancel out the acceleration and effectively limit the maximum speed. A larger drag value will result in shorter acceleration and deceleration times, making the controls feel more "tight", but also greatly limit the effect of collisions.



                If you want the character to have tight controls but also be affected by collisions, you could handle this the way the answer by gjh33 suggests. Have two different states in your player-controller. A regular state where the rigidbody has high drag and the player has full control force, and a "just got hit" state where you reduce the drag and the control force temporarily in order to make the character fly around in a temporary state of uncontrolled helplessness.



                I am looking forward to playing your game.






                share|improve this answer











                $endgroup$



                I created a little demo game a few days ago which demonstrates different ways to move a player-character. It might help you to better understand which way of moving is the right one for your particular game.



                In general, you should use rigidbody.AddForce whenever feasible. It automatically takes care of managing multiple overlapping forces and ensures that the transfer of momentum on collisions is physically correct.



                If you don't want your character to be able to accelerate indefinitely, increase the "Linear Drag" value of the rigidbody. The drag force increases quadratically with the velocity, so at some point it will cancel out the acceleration and effectively limit the maximum speed. A larger drag value will result in shorter acceleration and deceleration times, making the controls feel more "tight", but also greatly limit the effect of collisions.



                If you want the character to have tight controls but also be affected by collisions, you could handle this the way the answer by gjh33 suggests. Have two different states in your player-controller. A regular state where the rigidbody has high drag and the player has full control force, and a "just got hit" state where you reduce the drag and the control force temporarily in order to make the character fly around in a temporary state of uncontrolled helplessness.



                I am looking forward to playing your game.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited yesterday

























                answered yesterday









                PhilippPhilipp

                81.9k20193243




                81.9k20193243























                    4












                    $begingroup$

                    Myself, I like to solve this by thinking of all player movement as acceleration-based.



                    I choose a target velocity using whatever complicated control logic I like, then ask the player avatar to accelerate toward that target, while respecting maximum acceleration rates I set.



                    Then, depending on the avatar's state (on ground, on ice, in the air, in a knockback state), I can change those acceleration rates to make the control input have a sharper or less pronounced impact.



                    Rigidbody2D body;

                    void AccelerateTowards(Vector2 targetVelocity, float maxAccel, float maxDecel) {
                    // Compute desired velocity change.
                    var velocity = body.velocity;
                    var deltaV = targetVelocity - velocity;

                    // Convert our velocity change to a desired acceleration,
                    // aiming to complete the change in a single time step.

                    // (For best consistency, call this in FixedUpdate,
                    // and deltaTime will automatically give fixedDeltaTime)
                    var accel = deltaV / Time.deltaTime;

                    // Choose an acceleration limit depending on whether we're
                    // accelerating further in a similar direction, or braking.
                    var limit = Dot(deltaV, velocity) > 0f ? maxAccel : maxDecel;

                    // Enforce our acceleration limit, so we never exceed it.
                    var force = body.mass * Vector2.ClampMagnitude(accel, limit);

                    // Apply the computed force to our body.
                    body.AddForce(force, ForceMode2D.Force);
                    }


                    Separating acceleration & deceleration rates like this lets me give a sharper braking force, which tends to help the controls feel tight & responsive when stopping or changing directions, while keeping a smooth acceleration for getting up to speed. It also lets you penalize braking specifically when on ice or being knocked back.



                    We can make a control state parameters object to hold the max speed, acceleration, and deceleration rates for our air, ground, ice, knockback states etc. and use this to adjust our control handling very flexibly:



                    // Choose our current speed / acceleration parameters based on our state.
                    var controlState = GetCurrentControlState();

                    // Compute desired velocity.
                    var velocity = GetDesiredVelocityFromInput(controlState.maxSpeed);

                    // Try our best to reach that velocity, with our current parameters.
                    AccelerateTowards(
                    velocity,
                    controlState.maxAccel,
                    controlState.maxDecel
                    );





                    share|improve this answer











                    $endgroup$













                    • $begingroup$
                      does deltatime automatically give fixedDeltaTime in fixedUpdate loop? That's really cool! I know I used to have to code around that, do you know when they added that?
                      $endgroup$
                      – gjh33
                      yesterday










                    • $begingroup$
                      I looked into it you're right. That's very useful. I don't remember that being a thing when I started working in unity, definitely makes reusing functions in different update loops way easier.
                      $endgroup$
                      – gjh33
                      yesterday
















                    4












                    $begingroup$

                    Myself, I like to solve this by thinking of all player movement as acceleration-based.



                    I choose a target velocity using whatever complicated control logic I like, then ask the player avatar to accelerate toward that target, while respecting maximum acceleration rates I set.



                    Then, depending on the avatar's state (on ground, on ice, in the air, in a knockback state), I can change those acceleration rates to make the control input have a sharper or less pronounced impact.



                    Rigidbody2D body;

                    void AccelerateTowards(Vector2 targetVelocity, float maxAccel, float maxDecel) {
                    // Compute desired velocity change.
                    var velocity = body.velocity;
                    var deltaV = targetVelocity - velocity;

                    // Convert our velocity change to a desired acceleration,
                    // aiming to complete the change in a single time step.

                    // (For best consistency, call this in FixedUpdate,
                    // and deltaTime will automatically give fixedDeltaTime)
                    var accel = deltaV / Time.deltaTime;

                    // Choose an acceleration limit depending on whether we're
                    // accelerating further in a similar direction, or braking.
                    var limit = Dot(deltaV, velocity) > 0f ? maxAccel : maxDecel;

                    // Enforce our acceleration limit, so we never exceed it.
                    var force = body.mass * Vector2.ClampMagnitude(accel, limit);

                    // Apply the computed force to our body.
                    body.AddForce(force, ForceMode2D.Force);
                    }


                    Separating acceleration & deceleration rates like this lets me give a sharper braking force, which tends to help the controls feel tight & responsive when stopping or changing directions, while keeping a smooth acceleration for getting up to speed. It also lets you penalize braking specifically when on ice or being knocked back.



                    We can make a control state parameters object to hold the max speed, acceleration, and deceleration rates for our air, ground, ice, knockback states etc. and use this to adjust our control handling very flexibly:



                    // Choose our current speed / acceleration parameters based on our state.
                    var controlState = GetCurrentControlState();

                    // Compute desired velocity.
                    var velocity = GetDesiredVelocityFromInput(controlState.maxSpeed);

                    // Try our best to reach that velocity, with our current parameters.
                    AccelerateTowards(
                    velocity,
                    controlState.maxAccel,
                    controlState.maxDecel
                    );





                    share|improve this answer











                    $endgroup$













                    • $begingroup$
                      does deltatime automatically give fixedDeltaTime in fixedUpdate loop? That's really cool! I know I used to have to code around that, do you know when they added that?
                      $endgroup$
                      – gjh33
                      yesterday










                    • $begingroup$
                      I looked into it you're right. That's very useful. I don't remember that being a thing when I started working in unity, definitely makes reusing functions in different update loops way easier.
                      $endgroup$
                      – gjh33
                      yesterday














                    4












                    4








                    4





                    $begingroup$

                    Myself, I like to solve this by thinking of all player movement as acceleration-based.



                    I choose a target velocity using whatever complicated control logic I like, then ask the player avatar to accelerate toward that target, while respecting maximum acceleration rates I set.



                    Then, depending on the avatar's state (on ground, on ice, in the air, in a knockback state), I can change those acceleration rates to make the control input have a sharper or less pronounced impact.



                    Rigidbody2D body;

                    void AccelerateTowards(Vector2 targetVelocity, float maxAccel, float maxDecel) {
                    // Compute desired velocity change.
                    var velocity = body.velocity;
                    var deltaV = targetVelocity - velocity;

                    // Convert our velocity change to a desired acceleration,
                    // aiming to complete the change in a single time step.

                    // (For best consistency, call this in FixedUpdate,
                    // and deltaTime will automatically give fixedDeltaTime)
                    var accel = deltaV / Time.deltaTime;

                    // Choose an acceleration limit depending on whether we're
                    // accelerating further in a similar direction, or braking.
                    var limit = Dot(deltaV, velocity) > 0f ? maxAccel : maxDecel;

                    // Enforce our acceleration limit, so we never exceed it.
                    var force = body.mass * Vector2.ClampMagnitude(accel, limit);

                    // Apply the computed force to our body.
                    body.AddForce(force, ForceMode2D.Force);
                    }


                    Separating acceleration & deceleration rates like this lets me give a sharper braking force, which tends to help the controls feel tight & responsive when stopping or changing directions, while keeping a smooth acceleration for getting up to speed. It also lets you penalize braking specifically when on ice or being knocked back.



                    We can make a control state parameters object to hold the max speed, acceleration, and deceleration rates for our air, ground, ice, knockback states etc. and use this to adjust our control handling very flexibly:



                    // Choose our current speed / acceleration parameters based on our state.
                    var controlState = GetCurrentControlState();

                    // Compute desired velocity.
                    var velocity = GetDesiredVelocityFromInput(controlState.maxSpeed);

                    // Try our best to reach that velocity, with our current parameters.
                    AccelerateTowards(
                    velocity,
                    controlState.maxAccel,
                    controlState.maxDecel
                    );





                    share|improve this answer











                    $endgroup$



                    Myself, I like to solve this by thinking of all player movement as acceleration-based.



                    I choose a target velocity using whatever complicated control logic I like, then ask the player avatar to accelerate toward that target, while respecting maximum acceleration rates I set.



                    Then, depending on the avatar's state (on ground, on ice, in the air, in a knockback state), I can change those acceleration rates to make the control input have a sharper or less pronounced impact.



                    Rigidbody2D body;

                    void AccelerateTowards(Vector2 targetVelocity, float maxAccel, float maxDecel) {
                    // Compute desired velocity change.
                    var velocity = body.velocity;
                    var deltaV = targetVelocity - velocity;

                    // Convert our velocity change to a desired acceleration,
                    // aiming to complete the change in a single time step.

                    // (For best consistency, call this in FixedUpdate,
                    // and deltaTime will automatically give fixedDeltaTime)
                    var accel = deltaV / Time.deltaTime;

                    // Choose an acceleration limit depending on whether we're
                    // accelerating further in a similar direction, or braking.
                    var limit = Dot(deltaV, velocity) > 0f ? maxAccel : maxDecel;

                    // Enforce our acceleration limit, so we never exceed it.
                    var force = body.mass * Vector2.ClampMagnitude(accel, limit);

                    // Apply the computed force to our body.
                    body.AddForce(force, ForceMode2D.Force);
                    }


                    Separating acceleration & deceleration rates like this lets me give a sharper braking force, which tends to help the controls feel tight & responsive when stopping or changing directions, while keeping a smooth acceleration for getting up to speed. It also lets you penalize braking specifically when on ice or being knocked back.



                    We can make a control state parameters object to hold the max speed, acceleration, and deceleration rates for our air, ground, ice, knockback states etc. and use this to adjust our control handling very flexibly:



                    // Choose our current speed / acceleration parameters based on our state.
                    var controlState = GetCurrentControlState();

                    // Compute desired velocity.
                    var velocity = GetDesiredVelocityFromInput(controlState.maxSpeed);

                    // Try our best to reach that velocity, with our current parameters.
                    AccelerateTowards(
                    velocity,
                    controlState.maxAccel,
                    controlState.maxDecel
                    );






                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited yesterday

























                    answered yesterday









                    DMGregoryDMGregory

                    64.7k16115180




                    64.7k16115180












                    • $begingroup$
                      does deltatime automatically give fixedDeltaTime in fixedUpdate loop? That's really cool! I know I used to have to code around that, do you know when they added that?
                      $endgroup$
                      – gjh33
                      yesterday










                    • $begingroup$
                      I looked into it you're right. That's very useful. I don't remember that being a thing when I started working in unity, definitely makes reusing functions in different update loops way easier.
                      $endgroup$
                      – gjh33
                      yesterday


















                    • $begingroup$
                      does deltatime automatically give fixedDeltaTime in fixedUpdate loop? That's really cool! I know I used to have to code around that, do you know when they added that?
                      $endgroup$
                      – gjh33
                      yesterday










                    • $begingroup$
                      I looked into it you're right. That's very useful. I don't remember that being a thing when I started working in unity, definitely makes reusing functions in different update loops way easier.
                      $endgroup$
                      – gjh33
                      yesterday
















                    $begingroup$
                    does deltatime automatically give fixedDeltaTime in fixedUpdate loop? That's really cool! I know I used to have to code around that, do you know when they added that?
                    $endgroup$
                    – gjh33
                    yesterday




                    $begingroup$
                    does deltatime automatically give fixedDeltaTime in fixedUpdate loop? That's really cool! I know I used to have to code around that, do you know when they added that?
                    $endgroup$
                    – gjh33
                    yesterday












                    $begingroup$
                    I looked into it you're right. That's very useful. I don't remember that being a thing when I started working in unity, definitely makes reusing functions in different update loops way easier.
                    $endgroup$
                    – gjh33
                    yesterday




                    $begingroup$
                    I looked into it you're right. That's very useful. I don't remember that being a thing when I started working in unity, definitely makes reusing functions in different update loops way easier.
                    $endgroup$
                    – gjh33
                    yesterday


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Game Development Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    Use MathJax to format equations. MathJax reference.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgamedev.stackexchange.com%2fquestions%2f169839%2fhow-to-move-the-player-while-also-allowing-forces-to-affect-it%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

                    He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

                    Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029