recently i ported the optimized code of mine from the previous game since my goal is to have many enemies rendered in one single screen, im impressed with how it turns out and my FPS remains 60 but the way this works rn kills my game a lot, i thought my code was unoptimized for a little bit but turns out 2 of these properties are not compressed like how humanoid does, moving the controller for all 100 with MovingDirection takes only about 40% while FacingDirection uses 60%
if you want to repo on this, i mostly used this as a setup first
https://create.roblox.com/docs/physics/character-controllers
after setting up the controllers, you would then spawn 100 of these, with whatever you want, note that it’s different from a traditional humanoid so both properties of ControllerManager requires Unit Vector3 which is a direction
A private message is associated with this bug report
Can you provide more details? We don’t understand what is the bug.
the problem with this is the way it replicates 2 of these properties for ControllerManager, if you see the “Recv” up right next to ping you’ll see it going up to 100 kbs which for my game could contribute to pings if one of the other parts also sends huge amount of datas, my expectation was that it’ll be as optimized as current humanoid (which trades low bandwidth with bad performance)
my goal was to render more than 100 NPCs which i managed to pass 40 since that’s my goal, these 2 APIs accept unit vector and it’s easier to work with it but seeing how this turned out after looking at the bandwidth seems worrying in the future
i tried swapping with any physics constraint like AlignOrientation and LinearVelocity but neither of these solve the issues, rn im forced to make my own humanoid system with custom physics as a replacement
