Closed mojca closed 1 year ago
Currently VRML export is based on VTK and it uses VTK-based normal calculation. In 7.6 it is possible to use the normals from OCCT. This line would have to be modified.
So long story short - let's wait till 7.6 is merged and try to fix it there.
If I understand correctly: someone needs to finalize support for Open CASCADE version 7.6.0 in CadQuery and then you'll be able to test an alternative approach to export to VRML and see if it works better? (It's not totally unambiguous what version 7.6 refers to.) Thank you for checking this out.
Indeed, [OCCT/OCP] 7.6. See: https://github.com/CadQuery/cadquery/pull/1156
@mojca could you check if #1167 solves this issue?
What is the best way to install CadQuery in a proper way, so that I will be able to test that change? (I would prefer to stick with pip
rather than conda
, if possible. Or I can manually edit some files if needed.)
Something like this? https://stackoverflow.com/a/20101940
This or clone the repo and use pip install -e .
. You might want to ignore the deps if you already installed them.
Thank you, that seems to work fine (both the installation and rendering a complex model).
This leaves two remaining "issues" related to KiCad:
assy.save('model.wrl', exportType='VRML', scale=1/2.54)
But those are pretty unrelated and I'll probably open a new issue for those.
Ok, open new issues @mojca, but please use more quantitative language than "something is heavily unoptimized".
Solved by #1167
I'm not yet "proficient in interpreting VRML files", but it seems that the assemblies exported into VRML end up with wrong face orientation.
I first reported the issue to KiCad:
and prepared the files with a minimum example here:
@jmwright