I’m guessing the speed difference is from the deceleration always being applied in the behavior after you set the velocity.
So at 60fps the speed after deceleration is applied would be:
300-5000/60 = 216.66
And at 144fps:
300-5000/144 = 265.28
And at unlimited it could in theory approach much closer to 300.
Which seems to match with what you’re seeing where 144fps makes it go faster.
You could try setting the deceleration to 0 when you’re pressing buttons, and set it back to 5000 otherwise. Or maybe you could utilize the simulate control action, since I’m pretty sure deceleration isn’t applied when you tell the behavior a control is pressed.
I guess we could suggest to have deceleration disabled any frame we set the velocity from the behavior itself, but I don’t think that’s a good idea and would result in many more issues so I’d do one of the other two ideas.