Have you seen the stamina of wolves when they are on the hunt? This post is important to me. My hunger got me out in another outing and brought another bone for you all to chew on. I managed to process 3 important files. They look pretty, below. These are just portions.
which is produced by https://drive.google.com/file/d/1X4Ts_X ... sp=sharing
and https://drive.google.com/file/d/1E27JiW ... sp=sharing
which is produced by https://drive.google.com/file/d/1QixH6z ... sp=sharing
and https://drive.google.com/file/d/19V_mur ... sp=sharing
which is produced by https://drive.google.com/file/d/1mP71UB ... sp=sharing
and https://drive.google.com/file/d/1ldTUv7 ... sp=sharing
I kept all the layers red by the scad file so that you can see that more complicated parts are still working in FC with numerous layers and a lot of intersecting geometry.
The scad files will be fetched by FC0.192, however, I do not know if the rotate extrude will work correctly, if not, you'll have to install the newer importCSG.py and the other one.
however, this advance just dragged me into another pit. Assume that I want them to be exactly that, that you see. Easy, just make a solid, select it, click export step ... bingo!! Right? Well, the step export of the first file when brought back to FC looks just as it is seen in the screen shots below. I went out to hunt again but just managed to find carrion and hard bones. This one won't yield.
The step exports appear to have "bled" geometry inward as seen in the image on the top of the second set. Note the gap in between and the "bled" geometry. Note also in the second image, geometry that shouldn't be there in the first place intersecting awkwardly with actual desired geometry. The FC looks perfect and there is no logical reason for the hidden geometry of the FC file to intersect the seen geometry in its awkward embodiment.
The second file, (InsertCradle) is part of another structure. When I attempt a fetch of the exported step file back into FC, FC dies. Resuscitation is required.
The portion you see in the second image from the top down is fetched correctly by FC as seen in the image. The step files when imported back into freecad look as shown below:
https://drive.google.com/file/d/1nXQtmU ... sp=sharing
Note the partial rotate extrude being ignored in the generated step file.
Out of speculation i suspect that this may be an outgrow of the issue with the parsed rotate extrude. The parts that I see in the fetched Step file show 360 degrees circular geometry where it is only say, 100. I would have not expected that the algorithm that makes the conversion between FC and Step would require proper parsing of that but maybe, it does.
The third file, (base) which is also just a portion of the original file has thrown me back into issues I thought I had overcome.
One good thing is that I can render a single piece of geometry in openscad and pass that single piece to FC so that I can work my way up to try to figure the identity of the bug. This one could amount to a prehistoric dragonfly the size of an eagle. I need an entomologist.
The third image from the top down shows both, the original two 2D images and the resulting union of extrusions of each. This one was working at a time but it got possessed. If in the boolean union I put the rectangle first, I obtain the rectangle. I chewed on this one like a dog after a hunger strike.
The bone is there for you to chew on.