3D Print Environment STL Export Custom options defaults to ignore bug

[andy.zhuBM4FW]

When using the 3D Print environment and attempting to set a custom STL mesh resolution within the options window all options default to ignore which results in poor export quality, irrespective of what value I set. This limits me to the high preset which is insufficient for SLA printing as it results in visible mesh faceting on the printed object.
This is occurring on two different computers, so I don't believe it's an install issue.
I have been working around it by exporting as OBJ and then converting it externally. Funnily the resolution option for exporting OBJ works.

I use Windows 10 17763 and I use Inventor 2020.

[MoshiurRashid]

Well, generally, I use meshmixer for these kind of issues.

Try Autodesk Meshmixer

[andy.zhuBM4FW]

I'm not quite sure how meshmixer would help, could you explain your workflow? I don't think meshmixer supports inventor files directly.

[johnsonshiue]

Hi Andy,

I see the issue now. The option persists as last used on a per session basis. Once you restart Inventor, the last used option will be reset to system default. If I recall correctly, most of the Export options behave this way. I think you would like it to always persist last used, but it does not work that way.

Many thanks!

[mcgyvr]

Do you need to use the 3d print environment? What about just exporting to stl file right from the regular part environment? That "resolution" setting doesn't seem to be effected by whatever this bug is and stays persistent 

[andy.zhuBM4FW]

While it would be nice to have persistent resolution profiles between sessions, I was more referring to the fact that during or between restarting Inventor, the custom profile doesn't function at all. Opening the resolution window in the 3D print environment and setting a custom resolution with the same values as the profile "high" results in a mesh quality equivalent to "brep". Opening the resolution window again in the same session shows that while "Custom" is still selected, all the set values have changed to "Ignore".

[andy.zhuBM4FW]

I typically used the 3D print environment to orient the part while exporting since the gcode processors I use for my 3D printers have poor orientation controls. Apart from that it's just bad habits and the fact I didn't know. 🙂

[mcgyvr]

---

@andy.zhuBM4FW wrote:

I typically used the 3D print environment to orient the part while exporting since the gcode processors I use for my 3D printers have poor orientation controls. Apart from that it's just bad habits and the fact I didn't know. 🙂

---

What printer/Slicer?

I've been using Cura and there is even a plugin to open native Inventor files directly.. I don't even need to export to stl anymore.. Works great

Cura supports quite a bit of 3rd party printers if you don't have an Ultimaker..

https://ultimaker.com/en/resources/20510-support-3rd-party-printers

[andy.zhuBM4FW]

I use Cura with a generic reprap FDM printer and Asura (manufacturer slicer with Cura engine) with my Peopoly Moai SLA printer. While I can use Cura for the Moai, it lacks the projection calibration which corrects for convex distortion and dimensional accuracy. Asura is not great and only allows for rotation in 5 degree increments with no auto orientation for object faces. Regarding the Inventor plugin, I've actually got it installed and it's never occured to me to open a ipt in cura.Unfortunately it seems that it still uses the high setting when converting an ipt file, which is fine for FDM, but not great for SLA. This is to say that the SLA machine that I have should really have some form of path smoothing, it's not really possible to approximate a circle with lines without an absurdly large gcode file.

[sundars]

Hi @andy.zhuBM4FW and everyone,

I just came across this post and was not aware of this issue before. I was able to reproduce this issue and we have fixed this issue internally. It's a shame we didnt catch it before. Barring no hiccups, we will try to roll this fix out for the next next update of Inventor 2021. I know Andy reported this against 2020 - but i dont have any ETA for versions older than 2021. If I get more information I will provide an update.

Thanks and our apologies.

-shiva