It seems FC 1.0.1 has a similar issue as FC1.0.0, exporting step files with 100% transparency, at least in some case.
An other issue is present when exporting some parts with Local coordinate system Local_CS
giving
<Import> ExportOCAF2.cpp(574): Local_CS_387 set default color
pyException: Traceback (most recent call last):
File "<string>", line 6, in <module>
<class 'OSError'>: Access violation
These are not kSU problems, but the FC core, unfortunately already from FC0.22 onward…
For FC1.0.0 I have partially circumvent the issues, but this has to be done for the new 1.0.1 release.
I don’t know for the file of the example, but you have to check the step file with a different CAD i.e. CADAssistant, not with FC.
This is because the issue is not only in writing step file, but also in reading transparent step objects.
The issue is milestoned for 1.1 (note not the same as 1.0.1). I guess someone could ask on the issue if there is a chance it could be pulled back into a 1.0.2 bugfix release, but I’m not sure the FreeCAD dev processes and how they decide on that kind of thing.
I have just pushed a new release that circumvents the issues for FC 1.0.0 and FC 1.0.1 ONLY.
(these issues must be solved in the 3D exporting FC kernel, added in introducing the material handling system, completely reworked in FC 1.0).
The exporting to ‘step’ MUST be done with the following buttons of kSU WB:
|
With these tools, the step file will avoid transparency issues and the blocking export pyException.
Just update kSU WB through FC Tools → Addon manager