STEP export to Rhino got broken after F360 updated? File attached.

[anton.kuptsovEJSSW]

My workflow is often about exporting from Fusion to Step and further adjustment in Rhino.

This week I noticed that all fillets got broken in a very specific way - it build some extra geometry for filleted edges as if it were a torus object with OD= Filleted Radius.

This is the Fusion file http://a360.co/2yn3SBR

This is what you get in Rhino 5 after exporting from Fusion to STEP and opening in Rhino.

[anton.kuptsovEJSSW]

thank you so much for checking this issue

[HughesTooling]

---

@innovatenate wrote:

I just received an update from our development team. After some investigating, they have determined that the issue is not in the Autodesk translators. There is a Rhino import bug/weakness exposed in Rhino 5, but the good news is its slated to be fixed in 6.

I was informed that some preliminary testing in a Rhino 6 beta (codename Serengeti) showed improvements.

See this thread as an example in the Rhino forum.

https://discourse.mcneel.com/t/step-file-from-creo/48815/2

I hope this helps!

Thanks,

---

@innovatenate How come I could export clean models a couple of months ago and it has stopped working then? Seems the usual blame the other guy excuse!

Mark

[innovatenate]

@HughesTooling This isn't a pass the buck thing, I'm not pointing fingers. CAD Translation is like 10 moving targets that all have to be hit at one time by 10 different people. As progress is made, it's very common for tools to develop issues in the read or writing of particular formats. This a price of progress thing. 

Solidworks, SimLab composer, Keyshot and others had trouble importing torus surfaces when edges crossed the "seam" of the torus. While addressing this issue solved a lot of problems for other software, the fix reveals an issue where some torus surfaces are not imported correctly into Rhino 5. The results of investigation is that Rhino needs to make some changes in order to read files correctly. The development team looked into a solution, but it means writing files incorrectly to compensate, which is flawed. It would be like changing the rules of arithmetic so that one student in a class gets a good score.  

Does that make more sense?

[anton.kuptsovEJSSW]

is that possible make a drop-down for export: 1) "normal STEP" 2) "weird STEP for Rhino5 users"  (which are many)

I know that's not ideal AT ALL, but it might let us solve and forget.

[Anonymous]

Hi there,

Finally found that thread after many research.

Im having this issue on all my models and it is so annoying. I use Rhino to stagged my scene and to render with Maxwell Rende.

Can someone confirm that this issue is fix with Rhino 6, I was not planning on buying the upgrade but this is such an time consuming and annoying issue that I would be fine spending $$ for that.

Let me know.

Best

[HughesTooling]

@Anonymous There was a problem importing cylindrical holes but it's fixed in the latest Rhino v6 SR. I've tested a couple of files with tori that fail to import into V5 and V6 looks good. See this thread for the problem with v6 and round holes. Have you tried the Rhino V6 demo, don't know if you'll be able to download the service release candidate while you run the demo.

Mark