Custom pads shape not updating in 3D

[flZLV3C]

Hi every body,

I'm struggle with a problem of generation of my footprint . 

I have a 10 test point ( 2x5 ) device to design. I'm proceding according to the normal way ( create new lib etc...) but when i'm using custom pads size ( smd round 30x30, so not in the list of available shape), no 3d footprint is generating. When i'm using a normal shape, it works. 

How is it possible please and how to proceed please ? I had no issue with eagle . And strange thing is that i can see it in librairie.io .... but not on my 3d pcb.

Thanks a lot 

[flZLV3C]

One more info, i see properly in Pads sketches my 10 pads ( with the dash round line)

[flZLV3C]

wooo that's weird, i set not 100% roundness but 99 and now i can see the pads :

I did the same than in this video at 3min : https://www.youtube.com/watch?v=TFpZYzV9yy0

but with 100, i don't get 3d footprint...

[jorge_garcia]

Hi @flZLV3C ,

I hope you're doing well. This looks like a bug

@HelenChen-ElectronicsQA Could you make a ticket for this? This is a problem with how the roundness parameter is being handled in the 3D PCB.

Let me know if there's anything else I can do for you.

Best Regards,

[flZLV3C]

thank you, so let see what @HelenChen-ElectronicsQA  said 🙂

[HelenChen-ElectronicsQA]

Hi @flZLV3C , 

So sorry for my so late response!

I could reproduce this issue and need to feedback to development team to have a check. Sorry that so far I didn't find other workaround except the one you found - set roundness as 99% instead.

So sorry for any inconvenience! I will keep you be posted if we have any update about this issue.

Regards,

Helen 

[HelenChen-ElectronicsQA]

Hi @flZLV3C ,

FYI - I found if I add the part (30X30, 100% roundness) in the EAGLE schematic file, and then push to Fusion 360 via Fusion sync, then in the 3D PCB file, I could see the pad.

Regards,

Helen

[HelenChen-ElectronicsQA]

Hi @flZLV3C , @jorge_garcia ,

Hope all is well.

Good news that in the latest Fusion Production build 2.0.12157, this issue is fixed.

Please check this on latest Fusion production build and feel free to let us know if you still meet the issue.

Thanks a lot.

Best regards,

Helen