Exported STEP file unreadable #317
Comments
|
OK, this is related to the issues with our NURBS backend. I'm afraid this may prove tricky to address as this likely not an issue with the STEP exporter itself. |
|
Thanks anymway!
…On Sat, Mar 31, 2018 at 11:48 AM, whitequark ***@***.***> wrote:
OK, this is related to the issues with our NURBS backend. I'm afraid this
may prove tricky to address as this likely not an issue with the STEP
exporter itself.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#317 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB_wAE6aUAv2BwAm3uwUgMS3oiTarCubks5tj6VcgaJpZM4TCfV_>
.
--
André Villemaire
|
|
@AndyPhil is there any way you can try this again with the latest code in master? I am unable to reproduce the problem. SolveSpace doesn't show any bad edges, and I was able to load an exported .stl in Slic3r with no problems. The website that couldn't read the stp is foreign language to me, so can't test that. |
|
Hi,
I am afraid that I don't have the files anymore. Thanks anyway!
Andre
Le mer. 19 août 2020, à 18 h 52, phkahler <notifications@github.com> a
écrit :
… @AndyPhil <https://github.com/AndyPhil> is there any way you can try this
again with the latest code in master? I am unable to reproduce the problem.
SolveSpace doesn't show any bad edges, and I was able to load an exported
.stl in Slic3r with no problems. The website that couldn't read the stp is
foreign language to me, so can't test that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#317 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP7AAEM6PHBBMDEI7BPFT3SBRJTRANCNFSM4EYJ6V7Q>
.
--
André Villemaire,
andrevillemaire@gmail.com
|
|
@AndyPhil the files are attached above. |
|
I tried with this: |
|
I've got another file causing such an issue in SolveSpace 3.1: An exported .STL file could not be read by two 3D-Printer sites. After that, I tested the generated .STL files with the import function of FreeCAD. Both differ only minimally in some 2D objects only. The defective file has an additional Sketch In Workplace and a Point and a Circle in it. (I expected the exported STL to be identical in both files because only 2D elements were added.) Please tell me when the defective files would be useful, or when I should open a new case. |
|
Thanks! I'll investigate more, and then try to put the issue in the right place... |
System information
SolveSpace version: 2.3
Operating system: MacOS High Sierra
Expected behavior
Exported STEP file should be readable
Actual behavior
STEP file was not readable by many sites
Additional information
After completing the excellent "bracket tutorial", I tried loading the resulting "Export surfaces..." step file to the Weerg site which produce automated on-line quotes (very cool). The part did not load and caused an error.
Based on the statement that Solvespace STEP files have been successful in the past, I tried to submit incrementally more complex files to find out if something in particular causes the problem. I redid the tutorial quickly and loaded an incomplete part and it loaded fine! I went back to the part from the original tutorial and deactivated the later steps (so the product is just an angle with an inside radius: no gusset and no holes) and to my surprise this part still caused an error. The two parts (try1.stp and try2.stp attached in zip) are similar (not identical) but only try1.stp causes an error.
In trying to understand the difference I looked at the step code, but .... it is too hard to understand. Last thing I did was to export the *.slt versions of these files in the hope that my slicer program would give me a hint of what is going on. Indeed the stl model was also faulty for the first try and fine for the second. The slicer program detected 12 non-manifold edges (see messages in lower right corner of two images below). This may help understand what is going on.
Archive.zip
The text was updated successfully, but these errors were encountered: