An error occurred while using the latest Linux o-voxel wheel.

[lestersssss]

Traceback (most recent call last):
File "/root/ComfyUI/nodes.py", line 2155, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 999, in exec_module
File "", line 488, in _call_with_frames_removed
File "/root/ComfyUI/custom_nodes/ComfyUI-Trellis2/init.py", line 1, in
from .nodes import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
File "/root/ComfyUI/custom_nodes/ComfyUI-Trellis2/nodes.py", line 21, in
import o_voxel
File "/root/miniconda3/lib/python3.12/site-packages/o_voxel/init.py", line 1, in
from . import (
File "/root/miniconda3/lib/python3.12/site-packages/o_voxel/convert/init.py", line 1, in
from .flexible_dual_grid import *
File "/root/miniconda3/lib/python3.12/site-packages/o_voxel/convert/flexible_dual_grid.py", line 4, in
from .. import _C
ImportError: /root/miniconda3/lib/python3.12/site-packages/o_voxel/_C.cpython-312-x86_64-linux-gnu.so: undefined symbol: _ZNK3c107SymBool14guard_or_falseEPKcl

Cannot import /root/ComfyUI/custom_nodes/ComfyUI-Trellis2 module for custom nodes: /root/miniconda3/lib/python3.12/site-packages/o_voxel/_C.cpython-312-x86_64-linux-gnu.so: undefined symbol: _ZNK3c107SymBool14guard_or_falseEPKcl

[JuyeongYi]

I don't know why but the creator of the ComfyUI TRELLIS node has modified o_voxel and is providing it only as a closed-source .whl file, which is making life difficult for the entire community. This is unnecessary; we should stick to the official Microsoft implementation of o_voxel to avoid these compatibility nightmares.

well. whl is just a zip file, so we can modify those crumbs, but modifying those package is not a good idea i think.

I don't like to separate env for trellis and comfy.

[visualbruno]

I made public the repository about cumesh here: https://github.com/visualbruno/CuMesh
And about o_voxel, it is the Fork about Trellis.2 here: https://github.com/visualbruno/TRELLIS.2

[JuyeongYi]

No, that is not the original. If you want them to use your modified version, have them follow the exact same method Microsoft used to build o_voxel. Also, provide a .sh file for that process. Providing a wheel file is difficult to use because it must perfectly match the user's environment, including the Python, PyTorch, and CUDA versions.

The README.md lacks a Table of Contents or navigation. Am I expected to go through every repository you have?

[visualbruno]

Fine. I added a section in the README.md about custom builds