Hi Mr Jpbaehr13,
The surface artefacts are created when the rendering engine processes the coplanar surfaces. The graphics calculation path involves triangulation of surfaces and shading them (applying an appearance). In the process, input data precision reduction and changing calculation domain from real numbers to integers make the whole process fast and resource-efficient. Along the way, the necessary rounding's will go two ways, and the effect will be seen as the image artefact, which is when two or more tessellated triangles are almost coplanar.
It is a very rough explanation.
Go back to the real story.
The removed half-tree still resides in the design ... but it is hidden. Removing means in the F360 context ... hide. The actual object data can not be REMOVED ... because it supports all the children objects derived from it.
So, after upgrading our conciseness, we can streamline the chop-chop process and still have a happy whistle time … but with a touch more thinking.
The simplified file is attached.
In the context of the problem ... Tree (F360) was not a villain ... the chopper was!

WARNING:
I modified the sketch a little ... thus repeat the above process yourself to make sure that all is right!
Regards
MichaelT
MichaelT