FS#77752 - Blender is looking for libextern_draco.so in the wrong place.
Attached to Project:
Community Packages
Opened by Andrew Tyler (assimilat) - Monday, 06 March 2023, 23:28 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 12 March 2023, 07:37 GMT
Opened by Andrew Tyler (assimilat) - Monday, 06 March 2023, 23:28 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 12 March 2023, 07:37 GMT
|
Details
Description:
The 'blender' package in the 'community' repo is looking for libextern_draco.so. When I attempted to export a gltf blender returned 'ERROR: Draco mesh compression is not available because library could not be found at /usr/lib/python3.10/site-packages' to the console. I added 'print(dll_path())' right after its defined in '/usr/share/blender/3.4/scripts/addons/io_scene_gltf2/io/com/gltf2_io_draco_compression_extension.py' and that verifies that it is looking in '/usr/lib/python3.10/site-packages'. I reverted the changes from '/usr/share/blender/3.4/scripts/addons/io_scene_gltf2/io/com/gltf2_io_draco_compression_extension.py.orig' to '/usr/share/blender/3.4/scripts/addons/io_scene_gltf2/io/com/gltf2_io_draco_compression_extension.py', left my print(dll_path) line in place, and that returned: ERROR: Draco mesh compression is not available because library could not be found at /usr/bin/3.4/python/lib/python3.10/site-packages/libextern_draco.so Reverting 'gltf2_io_draco_compression_extension.py' to the contents of 'gltf2_io_draco_compression_extension.py.orig', and exporting 'BLENDER_EXTERN_DRACO_LIBRARY_PATH=/usr/lib/python3.10/site-packages/libextern_draco.so' before executing blender fixes the issue. Additional info: * blender 3.4 Steps to reproduce: Run blender without "BLENDER_EXTERN_DRACO_LIBRARY_PATH" defined, go to 'File > Export > gLTF 2.0 (glb/gltf)', then look in the console for: 'ERROR: Draco mesh compression is not available because library could not be found at /usr/lib/python3.10/site-packages' |
This task depends upon
Comment by
Sven-Hendrik Haase (Svenstaro) -
Tuesday, 07 March 2023, 03:12 GMT
Should be fixed in 3.4.1-18. Please test.
Comment by
Sven-Hendrik Haase (Svenstaro) -
Sunday, 12 March 2023, 07:37 GMT
Assuming fixed and I tested it. Reopen if it isn't.