#quick question
1 messages · Page 1 of 1 (latest)
nice, that's great for my game
so only parts that move will check for touches so this means unanchored part
but there still might be a very small improvement when a moving part gets close to anchored parts as the part no longer needs to check them parts
but I'm not 100% sure how Roblox does it so it might even be possible that Roblox still scans all parts close to a moving part even if it has touched set to false
if all your parts in your game are anchored then setting touch to false will have no effect on performance
weird, once I've set both CanTouch and CanQuery to false, the 'orange lines '[ctrl + f6] were much lower on average
not all my parts are in game are anchored, but most are
so it does seems like it helps reducing lags
The few moving parts will have to detect touches to anchored parts
Hi devs! Here’s a quick overview of a new collision property for BaseParts. BasePart.CanTouch lets your determine if the part will trigger Touched/TouchEnded events on other BaseParts with TouchTransmitters. All BaseParts have CanTouch set to True by default. A BasePart's Touched or TouchEnded event will only fire if otherPart has CanTouch se...
From this post it says you must turn off cantouch and cancollide in order to see a small performance benefit
Makes sense because even if cantouch is turned off it will still need to detect touches to handle collisions