I create these types of problems a lot. The why is best reserved for another post. This component has one face that is not coplanar (see GIF). I have turned on color by axis, turned off length snapping, show hidden geometry and set display precision to 1/64". The face is off normal by 10 degrees and bottom angles are 40 degrees (for context).
Is there a way to resolve these types of problems using native SU tools? In the past I believe I found FredoScale to be useful with these types of issues. In some cases, just re-creating the component solved the problem. What techniques have you found useful?
You might think that the two end lines being the same coordinate at each end of the line would mean it should be coplanar, but the slope of the bottom line means theyâre not. This picture is a similar face shown from the front and side, and you can see that the two long edges are not parallel. Your long edges are also not parallel, but are closer than my example.
Generally I find it best to avoid creating the non-coplanar edges in the first place. If you followed the basic steps in the video of the step stool, you wouldnât create the non-coplanar edges.
Thanks, looks to be viable solution. I just canât follow all the steps. I get lost at the bottom of the geometry, after selecting rotated rectangle. Not sure what the bottom reference point.
Thank you, @Fredo6 (for everything) , I knew that function, but here is a particular case, because the semicircle must be extruded in another direction compared to the base.
Slower, worked. Thanks. I have now added âRotated Rectangleâ to my workflow. Now, I just need to determine why/how I am creating these unintended non-coplanar faces.
Cutlist extensions use the bounding box of an object to get the dimensions (as if the part is to be cut from a rectangular board). The bounding box always aligns with a group or componentâs axes, so if the contents are askew with respect to the axes the bounding box wonât be the tightest fit.
So, if I change the axes to be coplanar with letâs say, the face, the report will be more accurate? And does this occur with all the cut list extensions?
I canât claim to have checked every existing cutlist extension, but all the ones I have looked at use the bounding box, which always aligns with the component/groupâs axes.
Only from the sequence. As in the video you linked to, I created the leg in the vertical position and made the component before I rotated it to the desired angle. This means the componentâs axes are automatically aligned so the bounding box fits tightly.
You could change the axis orientation on the component but thereâs no need to do that with the method I showed. Just rotate the component after creating it.
The why is best reserved for another post. This component has one face that is not coplanar (see GIF). I have turned on color by axis, turned off length snapping, show hidden geometry and set display precision to 1/64". The face is off normal by 10 degrees and bottom angles are 40 degrees (for context).
