How small does it have to be for me to test it?
Edit: I think the difference here is the huge arc, I 5000+ why I could not force a BO with my tests.
What if we did the truncation before we render it in Ground Control so that way we could see if there were going to be issues in the preview of the file instead of them cropping up when we run it?
From a normal programming experience, I would hate that stuff just got truncated.
Either give a suggestion/recommendation, like a prompt, asking if the work is large or small. Based on the input, truncate or not.
Just my 2 cents.
Itās not a matter of being large or small, itās a matter that we are hoping to
get maslow accurate to 0.4mm (currently around 1-2mm), so specifying positions
to 6 decimal places does no good, it doesnāt produce a more accurate result, it
just takes more space to transmit (and then get ignored)
k
I think a āPre - Launchā check makes sense. With a dialog with buttons some thing like " we have detected some problems with your file. You could update the file, run it as is with possible problems, or we can try to fix it. How do you want to proceed?" Iāve seen this in 3D printing where the file wasnāt complete.
Thank you
Before I go to bed at 4:11 and because I canāt upload on git I will dump it here, just not to forget,
For my own reminder 80!
I saw the (beautiful) finished versionā¦does that mean you were able to make it not run away?