-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImportError: DLL load failed while importing _C #151
Comments
In my tests I found several I guess core packages like PyTorch3D are not yet ready for PyTorch 2.3. |
@Scharwunzel |
hi, sorry for the late reply and thank you für your help. I have now tried both tips, unfortunately without success. I have set PyTorch to The cuda version is also available at Both is showing while versions check in the cmd under \ComfyUI\python_embeded. At start of Comfy there are following versions: Do I have to do anything special for this to be taken over? |
Same problem here |
@Scharwunzel Try force-reinstall:
(By |
@YanWenKun I get this Message with this command: |
It works for me. .🥰 |
@Scharwunzel This error message was about other dependencies, you can ignore it, or:
|
@midnightrebels The warning in the screenshot is telling "some of the code is going to be outdated", and you can safely ignore it. |
Hello @YanWenKun , is the 2.2.2 version still usable for this solution? I guess a new solution need to be updated for 2.4.0? Ho can I solve the problem (ImportError: DLL load failed while importing _C: The specified module could not be found.) in that case? |
Referring to YanWenKun/ComfyUI-Windows-Portable#7 , just use 2.2.2 with old commit. Or if you want to update to the latest 3D-Pack, you need PyTorch 2.4 or 2.3.
Then update/reinstall 3D-Pack. Or just use all-in-one package: |
Hi thanks for your answer @YanWenKun before running your command, I would like to show you my current set and tell if you think I should proceed:
And I have cuda toolkit 12.1 ...init.py", line 53, in I am on the right path? |
OK @YanWenKun Just tried your line:
Seems Torch libraries no longer show cu118, instead it is cu121 But doing all of this brung me a whole new problem: A module that was compiled using NumPy 1.x cannot be run in If you are a user of the module, the easiest solution will be to What to do now? |
To downgrade Numpy:
And I noticed that you're using CUDA 11.8 packages, which should be fine with current setup, but in case you want to downgrade from cu121 to cu118:
|
@YanWenKun where did yousee the 11.8 packages, it was only torch_scatter right? |
Never mind it does not work :(
What do you think? |
|
Thanks. How did you know that was the exact version we needed? |
Just use PyPI to find the package you need:
Just seperate Python environments. One for Comfy3D, one for everything else, etc. I use GitHub to build big all-in-one package. It covers most popular nodes. Btw, I'm curious which node is asking for updating PyTorch from 2.4.0 to 2.4.1 ? |
p.s. Edit |
Hi again @YanWenKun, Almost all extensions (not all and I am afraid to experiment) uninstall Torch 2.4.0 and replace it with 2.4.1 (and forget to "inform" comfyui it did, so it can not even start?), it also UPDATE Numpy to the latest version. Which is a problme (as you saw earlier) One in mind is probably Comfy Essentials. (which did not even install actually, after breaking my comfy) Here is my method of installation: After that miraculously: few workflow work:
Here is where I am actually. |
And lastly, you can fork this repo, add/remove nodes in |
Thanks @YanWenKun But I wanted to learn the hard version, the version where we install it from base comfyui Official repo. |
Ok but how did you know by visiting that website (https://pypi.org/project/numpy/1.26.4/) that this is the right version for us I mean? |
@GPU-server Wow, that's cool! Tbh, I didn't choose the hard way in this case. I analyzed the build scripts of ComfyUI official portable and rewrote them into scripts of my own flavor. But if you want to build a ComfyUI bundle from the ground up, the key steps are:
|
Numpy2 brings break changes and many projects can't simply upgrade version number from 1.x to 2.x. |
I actually woudl have liked if you described the part number 7 more, but its ok for now. I will try it another day and see if I can. (I was able to make some workflow work Happy withthat for now. It was difficult overall) |
Hi,
when I start ConfyUI I get the following error in the (German) CMD:
Traceback (most recent call last):
File "C:\ComfyUI\ComfyUI\nodes.py", line 1879, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "C:\ComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack_init.py", line 28, in
module = importlib.import_module(f".{nodes_filename}", package=name)
File "importlib_init_.py", line 126, in import_module
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "C:\ComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\nodes.py", line 33, in
from .algorithms.main_3DGS import GaussianSplatting, GaussianSplattingCameraController, GSParams
File "C:\ComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\algorithms\main_3DGS.py", line 12, in
from .main_3DGS_renderer import GaussianSplattingRenderer
File "C:\ComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\algorithms\main_3DGS_renderer.py", line 24, in
from diff_gaussian_rasterization import (
File "C:\ComfyUI\python_embeded\lib\site-packages\diff_gaussian_rasterization_init.py", line 15, in
from . import _C
ImportError: DLL load failed while importing _C: Das angegebene Modul wurde nicht gefunden.
I already found out from the threat #77 that the error for others was due to the fact that they didn't install Visual Studio with C++, but I had this before installing Confyui and can't find a missing build either.
Can someone maybe help me with what else could be the problem or where else I could look?
Thank you in advance for any help!
The text was updated successfully, but these errors were encountered: