Open Proxy-99 opened 3 months ago
The spherical colshape requires a bit bigger radius than the circular one. Otherwise, there is a high chance of the miss in some of the edge conditions.
My opinion is that instead of this PR it's better to extend the circle colshape and add function setColCircleHeight
(as it has already done for polygons).
The spherical colshape requires a bit bigger radius than the circular one. Otherwise, there is a high chance of the miss in some of the edge conditions.
the problem will need types of col which can fit into the drawn shapes correctly
and the ColCircle has no height limit it goes to infinity
see
The spherical colshape requires a bit bigger radius than the circular one. Otherwise, there is a high chance of the miss in some of the edge conditions.
the problem will need types of col which can fit into the drawn shapes correctly of ring and arrow and cylinder
and the ColCircle has no height limit it goes to infinity
see #3435
Yeah, I see. But currently this PR is rather a temporary patch, not the comprehensive solution.
@tederis I have used ColTube instead of of sphere, I did some math calculations to try to adjust the size so far I think it's good with sizes like 300 and 500 it still not perfect
@tederis I have used ColTube instead of of sphere, I did some math calculations to try to adjust the size so far I think it's good with sizes like 300 and 500 it still not perfect
Looks pretty accurate. So maybe it's better to stick with tubes? Radiuses bigger than 100 are used rarely.
I don't think that a collision must 100% match the corresponding visual part. As was mentioned above collisions are a bit larger in SA. So you can simplify the formula.
Fixes #516 #331 #3435 #870 using tubes for both client and server by trying to adjust the size to fit the visual and focuses on improving accuracy this PR should improve isElementWithinMarker detect