ODB++ export, Track missing.

Keep in mind that this could be a problem with the ODB Viewer app. Try a different viewer before concluding that the problem is with CS. I am not saying that I know this is the problem in your case, but we have had a similar problem where arc traces were not represented in VUV and had the wrong widths in GerbView, but came through properly in CAD applications.

I have try in Valor and got same result.

IIRC, Valor is the oldest ODB viewer. I suggest that you check the STEP output from CS in a CAD app. If it looks OK there, the problem probably is the viewer, since ODB packages up STEP files. Again, this is just a way of checking for problems with viewers.

IIRC, Valor is the oldest ODB viewer. I suggest that you check the STEP output from CS in a CAD app. If it looks OK there, the problem probably is the viewer, since ODB packages up STEP files. Again, this is just a way of checking for problems with viewers.

I have add my ODB++,

If someone can have a look...

Please send your STEP output.

I have add the TGZ.

I have now an error using this TGZ.

Yes, I have reported bugs in the ODB++ package output of CS. Uppercase file and folder names must be converted to lower case before opening in ODB++ applications like viewers. Regarding your missing traces: Just send the .STEP files from the STEP output, NOT the ODB++ package. If those are missing the traces, we can be sure that CS fails to add them to the model. Otherwise, the problem could still be with viewing them within an ODB++ package.

Here they are

You have sent the STP portion of the ODB++ output package, which is not useful. Use the STEP command to generate a .STEP file.

Here is the step file.

I don't understand the link between ODB++ and Step file.

Here is the step file.

I don't understand the link between ODB++ and Step file.

Your STEP file has just 13 component bodies on a circuit board object.... no traces:

ODB++ package includes all CAMfiles created by CS. (At least, it includes all CAMfiles that you specify by configuring 'ODB output'.) This includes pick and place, NC drill, Gerber, Schematic, BOM, and the STEP solid models. .STEP is a solid model format that many CAD apps can import and export. Yes, there is STEP data in the ODB package, but it is compressed and repackaged in a way that makes it difficult to inspect without an ODB viewer. Since I was thinking that your problem COULD be ODB viewer incompatibilities, I suggested looking at the actual non-ODB STEP output. When we do, it also lacks traces.

It looks to me like either, 1) CS fails to include traces in the ODB package and this is a CS bug, OR, 2) You have not configured your ODB output in CS so that traces get included.

Choose the ODB Output setup on this command bar:

Here is a typical ODB output setup:

Be sure to check all the layers used in your layout.