USD export you lose FR4

USD export you lose FR4

JohnLauer_Adom
Participant Participant
344 Views
2 Replies
Message 1 of 3

USD export you lose FR4

JohnLauer_Adom
Participant
Participant

For a 3D PCB like this...

johnQM7EF_3-1746880086890.png

 

When you try to export to USD

johnQM7EF_0-1746879179796.png

 

You get this warning in the export dialog:

johnQM7EF_1-1746879195454.png

 

This error is a significant problem when exporting a PCB because it turns the green FR4 into a black material. The problem is worse because with the mapping Fusion chose to use, other items use Steel Satin too, so there's nothing uniquely identifiable about the FR4 layer anymore so you can't even create a script to remap back to FR4 afterwards.

 

My suggestion would be to at least map it to a supported appearance in a USD that is close to the green color and give it a name that can be run through a script to remap to an alternate material on the back-end.

 

This is how it looks in Blender. The FR4 turns black.

johnQM7EF_2-1746879987711.png

 

Of course another problem that's been going on forever is you don't see the silkscreen legend either because Fusion doesn't export the canvas to a USD. This would be another welcome feature.

 

 

John Lauer, CEO, Adom Industries | Fusion bridge (free, open source): wiki.adom.inc/adom/fusion-bridge
345 Views
2 Replies
Replies (2)
Message 2 of 3

jorge_garcia
Autodesk
Autodesk

Hi @JohnLauer_Adom,

 

I hope you're doing well. This seems like a general limitation of the USD export in Fusion. It seems like the decals don't go out in the export.

 

I'll take this to developers to see who is in charge of this and what can be done.

 

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

 

Best Regards,



​Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes
Message 3 of 3

colbyMZFJ8
Observer
Observer

Hi @JohnLauer_Adom ,

I just discovered today that this has been fixed. I couldn't seem to find any information about when it was fixed, but it seems to be good to go now.