Open altoiddealer opened 3 months ago
Here is some new information:
HOWEVER - If I do the following, InstantID model suddenly works again:
pip install onnx
As soon as I re-enable ReActor (which subsequently installs the other onnx packages) InstantID no longer works, and neither does ReActor (CUDA).
Now, I'm wishing to just figure out how to prevent ReActor from trying to install the wrong stuff over and over, breaking all my WebUI installations - I'd rather just use CPU for ReActor then nothing working at all
- pip install onnx
u right... try install Reactor will break InstantID too
but reinstall onnx
still dont work
r have solution? im used Webui-forge
So the temp solution I found to this is thanks to a user response here.
Delete the onnxruntime_gpu 1.8.x version in your /venv/Lib/site_packages folder, and then (after activating your venv) run pip install onnxruntime-gpu==1.17.0 --index-url=https://pkgs.dev.azure.com/onnxruntime/onnxruntime/_packaging/onnxruntime-cuda-12/pypi/simple
command.
The issue is though, even if I remove all onnx references in both the ReForge requirements files, and the requirements for roop (with no other extensions in the folder), upon restarting the webui, it updates onnxruntimegpu 1.8 again, removing the fixed version. I'm assuming onnx is a dependency for something else, and is triggering the update for onnxgpu back to the non CUDA 12 version of 18. Only way to get it to run without updating is to just pass the --skip-install
arg in webui-user.bat. But obviously that's not a great long term solution as it'll lock you out of future updates.
I dug further, and found discussions here and here talking about CUDA 12 versions of 1.18, but for some reason, those still didn't work for me. I tried manually installing the 1.18 CUDA12 build from pip install onnxruntime-gpu==1.18.1 --extra-index-url https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-cuda-12/pypi/simple/ --force-reinstall
, and sure enough ReForge would start without updating it, but it'd still throw the same CUDA not found error, which makes me think that there's some other issue, or maybe I'm still missing something, someone else can feel free to experiment.
I'm sure someone with more knowledge on the update mechanisms can figure it out. But this at least fixes it for me for now:
TL;DR
First, confirm
What happened?
Hello, I have fresh installations for the following webuis:
Note that ReForge is now widely regarded as the successor to Forge, with an active developer who has brought (almost) all of the A1111 upstream changes into Forge's memory management / performance. They optionally have a dev_upstream branch with additional upstream changes from ComfyUI.
With that all said! On a fresh installation of all of the above, with only ReActor enabled:
A1111 - NO ERROR
Forge / ReForge - ERROR (See below)
Note that I did not have any issues for a long time with Forge, but I also did not use ReActor for some time.
I believe one of your recent updates is the issue.
I've searched other posts, found a number of solutions such as:
Doesn't matter - STILL ALWAYS:
Steps to reproduce the problem
Sysinfo
Windows 11 nVidia RTX 4070ti
A1111 SYSINFO (NO ERROR) sysinfo-2024-07-25-17-01.json
FORGE SYSINFO (ERROR) sysinfo-2024-07-25-16-59.json
REFORGE SYSINFO (ERROR) sysinfo-2024-07-25-17-40.json
Relevant console log