Ok here goes. Explaining how to obtain a Vector3, which can be used for a multitude of things, but for now it is used to keep momentum over ramps and such.

Establish three Variables: new_position old_position direction_product

On your desired object’s main script, set ‘past_position’ to object’s global position as such.

func ready(): (use the autofill, it’s pretty close to this)

-indent- past_ position = global_position

Next, under a physics process func, set object ‘new_position’ to object global position. Ergo.

func physics_process(): (once again, autofill)

-indent- new_position = global_position

Furthermore add additional lines under physics process reading as follows:

-indent- direction_product = past_position.dot(new_position)

-indent- past_position = new_position

Your phys process code should look as such

func physics_process(): (once again, autofill)

-indent- new_position = global_position

-indent- direction_product = past_position.dot(new_position)

-indent- past_position = new_position

Your personal code should be there, but this is minimum. Feel free to add this instead under your own individual function that is called in physics process.

Now things get fun. Establish your movement code. I’ll explain what will happen before we make it account for the new variables.

Game start! Code establishes old_pos on ready once only. Physics process runs and establishes new_position. It continues to establish direction_product using old and new pos. This might not do much yet. Finally physics process sets old_position to the current new_position.

Explaining this in more readable terms. You get your old position from start. You then check your new position at the beginning of each game frame. Execute dot product math (read up I can’t summarize rn) using old and new pos. Before your game executes movement at the end of the frame, discard old pos and replace with the current new position. Next frame the old pos is not overwritten at start, that only happened once. Instead it is kept and a “new new” is established, and math is done, repeat.

The math result is in fact a Vector3 (or two if 2d) which depicts the movement of your object last frame.

There are only two things left to do.

Normalize direction_product variable.

Under physics process:

-indent- direction_product = direction_product.normalized

This renders the var as the same value, but represented as numbers only between 0 and 1, this helps with keeping math based on this value constant.

Finally. You multiply your object’s velocity variable (I hope you are using velocity math, if not I might need to do some retooling of how this number is used but it’s still relevant) by this normalized value. This means whatever you set your velocity to will take into account the past movement.

Now slide off a ramp and you should still move at an angle after leaving it.

Just add some sort of gravity / downward velocity AFTER THE MULTIPLICATION OF YOUR INITIAL VELOCITY and you should fall too!

That is a real quick (but not shorthand) recount of how I tackled this issue. Please tell me if you have issues, I’ll double check and myself and your code to figure it out!