Also, setting dragScale=0 won't affect performance that much since drag calculations are the same except the force never gets applied, but calculateDrag=false means that it's excluded from drag entirely. As well as causing parts behind it to get drag, this also will improve performance (mostly load times) of builds if you set it on most parts and only leave a few parts that define your drag model on.
dragScale 0 makes the "drag value * the drag scale" so drag scale "1" is the drag for that part multiplied by 1, I think at least.
.
drag calc false is different it doesn't calculate the drag for that part at all, it calculates the drag for the part behind it instead, it's great for high part builds as it makes them less laggy
Also, setting
dragScale=0
won't affect performance that much since drag calculations are the same except the force never gets applied, butcalculateDrag=false
means that it's excluded from drag entirely. As well as causing parts behind it to get drag, this also will improve performance (mostly load times) of builds if you set it on most parts and only leave a few parts that define your drag model on.@Aldriech ok give me
@rexzion 9 robux is all I can give
@Aldriech np now pay me
@rexzion @DarthAbhinav thank you!
dragScale 0 makes the "drag value * the drag scale" so drag scale "1" is the drag for that part multiplied by 1, I think at least.
.
drag calc false is different it doesn't calculate the drag for that part at all, it calculates the drag for the part behind it instead, it's great for high part builds as it makes them less laggy
No, the former multiplies drag by 0, the latter ensures that there's no lag due to drag by turning off the entire drag calculations entirely.
ackshully no