Yes, I think mouse movement does that and it’s dumb. Gamepads should not be doing that, I think… but who knows, JME inconsistently self-multiplies tpf sometimes.
High frame rates mean very small tpf which can cause math to be weird. So turning on vsync for full screen may help you. It’s an option in the settings dialog that pops up at app startup.
Note that Lemur’s InputMapper does not premultiply anything by tpf and also provides per input sensitivity scaling. (InputMapper can be used even if you don’t want to use the rest of Lemur.)
So then you could properly use tpf in your movement code and also set sensitivity differently for joystick than for mouse, etc…
Lemur wiki:
InputMapper javadoc:
http://jmonkeyengine-contributions.github.io/Lemur/javadoc/Lemur/com/simsilica/lemur/input/InputMapper.html
Lemur gem on using the input mapper: