Closed superfashi closed 1 year ago
There's a potential problem here (and with current production) of when user sets bottomRadius=0 because they want a cone. Due to back compat, our system will currently think that is a full cylinder.
We should change the place where we store top and bottom radius to _vGeomData.z
and _vGeomData.w
respectively so that if both _vGeomData.z==0 && _vGeomData.w==0
, we know it is a regular cylinder and should just use _vGeomData.x
. Otherwise, we would use topRadius=_vGeomData.z
and bottomRadius=_vGeomData.w
There's a potential problem here (and with current production) of when user sets bottomRadius=0 because they want a cone. Due to back compat, our system will currently think that is a full cylinder.
We should change the place where we store top and bottom radius to
_vGeomData.z
and_vGeomData.w
respectively so that if both_vGeomData.z==0 && _vGeomData.w==0
, we know it is a regular cylinder and should just use_vGeomData.x
. Otherwise, we would use topRadius=_vGeomData.z
and bottomRadius=_vGeomData.w
Good idea, I’ll implement this.
@rdiankov Added support for cone.
Closed by #1288
This PR adds
GetCylinderTopRadius
andGetCylinderBottomRadius
toGeometryInfo
Python binding.Also adds support to Cone (when top or bottom radius is 0)