How many triangles can .stl convertor handle?

[JoBar2]

I have drawn a somewhat complicated part, consolidated into one body.  Converting to .stl file generates 13K triangles, however not all are exported to the .stl file on my computer.  A portion of the converted body is simply missing, and I have noticed that more is missing as the part becomes more detailed and larger.  What are the limits?

[TheCADWhisperer]

@JoBar2 

Can you File>Export your *.f3d file to your local drive and then Attach it here to a Reply?

Also attach the  resulting *.stl file

I will make significant wager that the issue has nothing to do with any triangles limit.

Does Ctrl b (CMD b on Mac) return any issues?

Are there any unresolved issues highlighted in your Timeline?

[JoBar2]

Thanks for your help. I am really baffled. The .stl file preview looks O.K. in F360. However the Cura slicer shows missing information from the root of the wing to a couple inches toward the tip. The slicer is set to slice for my Creality Ender 3 pro printer.

Thanks again,

Joel Barlow

[TrippyLighting]

Please share your design!

[TheCADWhisperer]

---

@JoBar2 wrote:
wing… …tip. 

---

@JoBar2 

You did not answer my questions.

Q1. Are there any unresolved issues highlighted in yellow or red in the Timeline?

Q2. Does Ctr b return any issues?

Q3. Can you File>Export your *.f3d file to your local drive and then Attach it here to a Reply?

Q4. Can you Attach the resulting *.stl file here?

Base only on the two words wing and tip I will make wager that there are issues with the construction of the geometry.

[JoBar2]

I am somewhat embarrassed. The problem was not the model geometry nor the .stl file generated by F360. Rather it was a corrupted Cura slicer. I switched to the Prusa slicer and it generated perfect g-code. I am embarrassed because I should have done the simple check of saving the .stl file generated by F360, followed by inserting that file as a mesh file for further examination. When I did this and saw no difference, I had to conclude, correctly, that the problem lay with the slicer (in my defense, I did check the slicer on another, smaller model and it seemed O.K.).

At any rate, thank you for your time and interest.

Regards,

Joel Barlow

[JoBar2]

I am somewhat embarrassed. The problem was not the model geometry nor the .stl file generated by F360. Rather it was a corrupted Cura slicer. I switched to the Prusa slicer and it generated perfect g-code. I am embarrassed because I should have done the simple check of saving the .stl file generated by F360, followed by inserting that file as a mesh file for further examination. When I did this and saw no difference, I had to conclude, correctly, that the problem lay with the slicer (in my defense, I did check the slicer on another, smaller model and it seemed O.K.).

At any rate, thank you for your time and interest.

Regards,

Joel Barlow