Fusion G2 fillet not really G2 in Alias ...

[cekuhnen]

So I opened a model I did int Fusion in Alias and it seems the G2 option is only G0 everwhere not not even G1 or G2.

G1 check:

G2 Check:

So I am curious about what the G2 code really is.

[jeff_strater]

I'll take a look at this, and let you know what I find.

Jeff Strater (Fusion development)

[cekuhnen]

Please do.

It seems to be that also with a simple loft the curtvature is not perfect.

Fusion Result: to my understanding at least along the G2 edge the combs should be meeting but they dont.

Here the Alias version where I realigned the loft surface in the middle.

here is another Fusion Alias compairson: the combs in Alias do not match. I am not sure if that is the import STEP problem or if the Fusion model

is acually not correct. I also noticed Fusion makes pretty heavy meshes including maybe way too many spans into simple surfaces. Not sure if that could

cause this.

but after having align the surface again in Alias the combs are better.

[jeff_strater]

How are you taking designs to Alias? Via STEP?

[cekuhnen]

yes - is there a better format?


- - -

*Claas Kuhnen*


*(715) 309-9795*
*www.ckbrd.de*
*info@ckbrd.de*

[jeff_strater]

no, not that I know of. Just validating your workflow. Thanks!

[cekuhnen]

you are welcome

let me know if I did something wrong here.

but I assumed with G2 it all should show up the same in Alias
- - -

*Claas Kuhnen*


*(715) 309-9795*
*www.ckbrd.de*
*info@ckbrd.de*

[jeff_strater · Accepted solution]

Thanks, Claas, for bringing this to our attention.

The upshot is: The problem is in our translation from Fusion -> STEP - we are losing a bit of accuracy in approximating our internal procedural surfaces with generic Nurbs surfaces, and this shows up as the continuity problems that you are seeing. Inside Fusion, G2 does mean G2, but the translation is biting us.

We are working on a fix. Stay tuned.

Thanks,

Jeff Strater (Fusion development)

[cekuhnen]

thats great to hear that at least inside Fusion it works right.

Looking forward to the export fix.



Claas
- - -

*Claas Kuhnen*


*(715) 309-9795*
*www.ckbrd.de*
*info@ckbrd.de*

[cekuhnen]

there is more going on - export parts are completely missing!!!

[Anonymous]

Hi

I'm primarily a Rhino user. I convinced the company I work for to buy Fusion 360. To handle all the things Rhino struggles with. Fillets is one of those things. I'm dismayed that this conversion issue has yet to be fixed. It's really important that I get proper G2  degree 5 fillets. 

[promm]

@Anonymous,

In your attached image are you representing a model that was made in Rhino or a model that was made in Fusion 360 and imported into Rhino?  We are looking into how our fillets handle G2 weighting, there may be some changes we can do to improve the overall shape.

Regards,

Mike Prom 

[Anonymous]

With the Fusion example the box was modeled in Rhino. Then opened as a stp. file in Fusion. It was then filleted in Fusion and exported as stp. file. Finally opened again in Rhino for the comparison. 

The company I work bought Fusion 360 to do the things Rhino struggles with. Fillets are one of those things. So this is a common workflow for us.