If you modify HiddenParts logic, then yes.
This project is basically a cut-down version of my camera system in-game.
I did use viewmodels, though, not real character hands.
really?, I’m trying to understand the motivation behind these patterns in the module, because many of them look like micro-optimizations that actually hurt maintainability without producing worthy results.
Luau already optimizes method lookup and inline caching, so replacing normal property access with function pointer indirection doesn’t realistically improve performance. It mostly just makes the code extremely difficult to read and debug
I’ve run multiple benchmarks and the pattern used here consistently ends up around 6–20% faster in hot paths. Luau does perform some optimizations, but it does not magically eliminate the cost of every access pattern, especially when interacting with userdata rather than primitive types.
The entire goal of FPX is to stay lightweight and efficient, prioritizing predictable execution over syntactic convenience.
That’s subjective. For people familiar with the pattern it is perfectly readable, and the structure is intentionally simple.
If the design direction of FPX is not something you like, that’s fine. The module is built with a specific set of priorities in mind.
However, if you have concrete suggestions that improve performance while keeping the same design goals, I’m open to hearing them.
FPX now fully supports proper server-authoritative movement with input prediction, smoothing, and synchronized movement replication across platforms.
This update also fixes Roblox silently changing Thumbstick1 behavior, which previously affected WASD input handling. Movement input is now handled through a separate dedicated binding for consistent cross-platform behavior.
Additional networking optimizations were implemented, including higher precision movement transfer using packed I24 interpolation instead of standard F32 decimal transfer for normalized -1 → 1 input ranges.
Result:
More stable movement replication
Better precision
Reduced bandwidth usage
Smoother server-authoritative control
Consistent platform behavior
FPX continues pushing toward maximum performance with minimum overhead.
Provide more information
This could be the problem of server authority input misprediction itself also
I cannot know what is going on from vague wording
Installation
Requirements
Workspace
StarterPlayer
Performance first
Server authority support
True cross-platform input
Clean delta handling (impulse vs continuous input)
Minimal integration effort
Thank you for this resource this is very nice and easy to work with