Ooh ok

Yeah I will try with the tween later, ty

tweens are just some basic math

a linear tween is a tween with a function of

f(x) = x

, where

x

is usually time

I accidently turned on the property hints (or whatever they are called) and they look like this:

although it usually does some more math so that when

f(x)

is 0, its actually your "start value" and 1 is your "end value"

inlay hints

yeah but they are always messed up for me

try saving the file? the position might rely on the lsp which only triggers on save

and when I try to edit those lines, it jumps my cursor all over the place.

It's been saved

Thanks but that's not my problem so much as the fact that it's showing gibberish 😛

just wanted to share before I disabled them again

ahhhh i see

When something like that is behaving strangely or wrong, I find it odd that I haven't heard about it from anyone else, so I want to at least put it out there in case people had the same issue and just disabled and forgot or in case I'm somehow the only one

I added

rotational_velocity

, but now it doesn't stop rotating when the x velocity is 0

haxe
if (FlxG.mouse.justPressed)
        {
            if (FlxG.mouse.x > plr.x)
                if (FlxG.mouse.y > plr.y)
                {
                    plr.get_body().push(-PUSH_X, -PUSH_Y, true, VELOCITY);
                    plr.get_body().rotational_velocity = -PUSH_X;
                }
                else
                {
                    plr.get_body().push(-PUSH_X, PUSH_Y, true, VELOCITY);
                    plr.get_body().rotational_velocity = -PUSH_X;
                }
            else if (FlxG.mouse.x < plr.x)
            {
                if (FlxG.mouse.y > plr.y)
                {
                    plr.get_body().push(PUSH_X, -PUSH_Y, true, VELOCITY);
                    plr.get_body().rotational_velocity = PUSH_X;
                }
                else
                {
                    plr.get_body().push(PUSH_X, PUSH_Y, true, VELOCITY);
                    plr.get_body().rotational_velocity = PUSH_X;
                }
            }
        }

I'm just simply adding some velocity when the cursor is clicked, (I know I can write these if statements in a short amount of lines but whatever)

I'm sorry I can't record a video now for some reason, so when I click a button, the sprite moves like that

and when it lands, there is still rotational velocity, and that's not what I expect

(the square is still rotating)

Yeah @most-eve-98431 - went and had more of a look - . I think it just gives you 0, 2 or 4 subsamples. I'm assuming this all drives GL MSAA configuration.

I don't think echo has rotational collision resolution

oh 💀

It really just checks overlaps and moves them apart

okay thanks for clarifying that, but I think that's possible with flixel's built-in physics though iirc?

No

You can't even rotate colliders in flixel yet

mmm

I see