The title explains it does parts (such as details) can collide off create less lag?
I need to know this i would think in theory it would since roblox wouldnt need to be using any engines on the part to make it so you can walk on it.
I can’t confirm, though I think that it would still have the same lag hence it’s a brick and has to be loaded into the game just not able to be walked on.
No, because a physics touch calculation is still made for CanCollide. However, turning CanTouch off would improve performance slightly but likely only for densely packed areas of objects. I’m not sure by how much, it’s hardly noticeable.
Disable CanTouch, CanQuery and CanCollide always when you aren’t going to ever interact with the instance and when it’ll (it’ll as in its collision) never be used by the server.
If all three are disabled the instance is ignored by the part of the engine that calculates collisions, which will improve your average frames per second. The more instances you do this to, the more frames you’ll be saving.
(Also this was confirmed by a staff member on the CanQuery DevForum post, I don’t have a link to it unfortunately!)
Ok sorry for late response and thanks! Because i have alot of parts in one area that are for details and the player cant get to it so thanks!
Thank you. I always thought that simply removing the CanCollide property would do the job.