espressif/kicad-libraries

VRML models do not work

Opened this issue · 1 comments

Checklist

  • Checked the issue tracker for similar issues to ensure this is not a duplicate
  • Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
  • Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

To be able to export complete PCBs to VRML, the 3D models must be in VRML format. By default footprints in this library link to the STEP 3D models. If you switch a model from STEP to VRML (WRL), KiCAD does not show the model (at least the KiCad release 8.0.5 I'm running).

Actual behavior (suspected bug)

When switching from the STEP 3D models to the VRML 3D models, the VRML model should be shown, but nothing is shown.

Error logs or terminal output

No response

Steps to reproduce the behavior

Previously to these steps, you should have the Espressif Library plugin installed.

  1. Open KiCad Footprint Editor
  2. Open any module from PCM_Espressif library. E.g.: ESP32-C3-WROOM-02.
  3. Switch to 3D view (press ALT+3). The 3D module shows properly.
  4. Close the 3D viewer and in the Footprint Editor open the Footprint Properties dialog (Click File / Footprint Properties...).
  5. Go to the 3D Models tab.
  6. Change the model path to point to the VRML version (e.g.: ${KICAD8_3RD_PARTY}/3dmodels/com_github_espressif_kicad-libraries/espressif.3dshapes/ESP32-C3-WROOM-02.wrl).
  7. The 3D model is not shown.

This problem happens with all VRML files I tested in the Espressif Library. VRML files included with KiCad libraries load without a problem.

The bug also happens in the PCB Editor and prevents the full PCBs to be exported to VRML correctly.

Project release version

Latest release 3.0.1, and KiCad 8.0.5

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Linux

Operating system version

ArchLinux

Shell

Bash

Additional context

No response

I also ran into this issue today. Is there any update regarding this?