Turning off EnableFluidForces and CanTouch, minimizing CustomPhysicalProperties

[Vungielek (Bubusch_42)]

I would like to quickly ask about Physical properties like EnableFluidForces and CanTouch, and CustomPhysicalProperties.

EnableFluidForces activates aerodynamical forces etc. on a part, and CanTouch logs touches in the part, so that you can use methods like :Touched etc.

So, if i turn off these properties on a lets say, anchored part, will my game be atleast a bit faster? Have anyone tried such actions? Also, will setting every CustomPhysicalProperty on 0, or an integer, like 1, also make compiling and loading the game faster?

Looking forward to hearing from you all Roblox devs.

[7elevvn]

CanTouch is most likely the only one that would have a benefit, but I’m sure that benefit would be extremely small and probably not even noticeable

[GamEditoPro]

.CanTouch property affects game a lot. Disable it everywhere it’s unneeded.
.EnableFluidForces property affects only unanchored parts. Due to extra calculations, it affects performance a lot, and if you don’t need it, disable it on that parts. Having it true/false on anchored parts won’t make any diffirence.
.CustomPhysicalProperties instead of consuming performance consumes memory. If it’s not set, then it uses material/custom material parameters. If it set - then it will use some for each part. Even if there’s 100 same CustomPhysicalProperties, they each will consume memory. In this case, it would be better to create material variant to handle that.