Incorrectly generated contact button SMD traces

[differentiable]

This is part of a project to re-work a PCB featuring conductive contact buttons (if they have a better or more common name, don't hesitate to mention it).

The contact polygons were imported into the footprint for the device as dxf files, converted using the right click -> convert to polygon method, and left alone. Circular SMD pads were placed at 4 corners (for ease of use) and connected identically.

As can be seen, the geometry for the contact copper is not generated correctly when switching to 3D PCB view. This also causes the toolpath generator to follow the same geometry. There is a keepout area surrounding the entire button pad, if that is relevant (needed for the rubber gasket to deform correctly over the pad).

The pads appear to highlight correctly in the board editor, so I am not certain what went wrong with the contact geometry.

[differentiable]

I find that I have to manually use import-dxf and position each pad individually, while leaving "ghost" switches in the schematic. While there aren't that many pads, this is kind of irritating, since this is really just an unusual SMD pad pattern and warrants treatment as a device (and would make schematic updates MUCH easier).

Capture from test placement:

[jorge_garcia]

Hi @differentiable ,

This is an issue with how the 3D PCB handles the arbitrary pad shapes. @HelenChen-ElectronicsQA Could you add this thread to the existing ticket on this issue?

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

Best Regards,

[HelenChen-ElectronicsQA]

Hi @differentiable , @jorge_garcia 

So sorry for any inconvenience.

I will add this thread to existing ticket to track.

And @differentiable , Do you mind to attach the brd file in this thread and we could try it too? Thank you,

Best Regards,

Helen

[differentiable]

I do not have the .brd file available, but I don't mind providing the pad .dxf (attached).

[panpan_fan]

Hi @differentiable 

I hope you are doing well!

Today we release Fusion V2.0.18220+, and the issue should be fixed now.

Please upgrade Fusion and have a try, thanks!

Regards,

Panpan Fan