Python Module can't find Draco library #113469
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#113469
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Win10 / MacOS Ventura / Ubuntu 22
Graphics card: 1080 Ti / M2 Max / 1080 Ti
Blender Version
Python Module 3.6
Short description of error
If you try to export or import a Draco compressed GLTF, it throws an error that it failed to find the Draco library at an OS-specific location relative to the mesh file. Placing the library at this location allows normal import and export. Behaviour is identical for Windows, Mac, and Linux.
Exact steps for others to reproduce the error
Thank you for the report. But as you have reported an issue related to the "glTF 2.0 format" addon, it should have been reported in the blender-addons repository instead of the blender repository.
This addon actually has its own Bug Tracker. See https://github.com/KhronosGroup/glTF-Blender-IO/issues/
Unfortunately, we will have to close your report as it was filed in the wrong repository.
Please use the link indicated to report the bug.
I think this is most likely about the BPY python module itself, the one you can pip install separately from blender, and not strictly about the addon.
That's right, I should have clarified that I meant the bpy python module, used separately from the Blender app. The bug doesn't reproduce when you use the GLTF addon through the GUI, or when you use the commands above in the Blender app's Python console--it has no trouble finding the path to the included Draco library then.
Any news on that?
What is the wanted behavior about any external shared libraries that are compiled by Blender core.
How to manage them when publishing bpy as a py module?
I have PR request in for modify the build system to include the Draco library in the python module and a fix for the exporter to find it in the default location. This is working nicely for me locally but i would rather have this change pushed upstream so I don't have to patch my installation.
https://github.com/KhronosGroup/glTF-Blender-IO/pull/2300
#125556
The Blender part of the work is now merged.
I will merge glTF-Blender-IO soon