-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
[Bug]: UserWarning: NVIDIA GeForce RTX 5070 Ti with CUDA capability sm_120 is not compatible with the current PyTorch installation. The current PyTorch install supports CUDA capabilities sm_50 sm_60 sm_61 sm_70 sm_75 sm_80 sm_86 sm_90. #16884
Comments
As per #16824, there is a separated release for RTX 50s. Were you using that one? |
No, when I go to a GitHub repository, I grab the release from the main page and read the instructions on the main page. I don't go into every single issue page of the repository just to find a working version. Expecting users to do that is absolutely unrealistic. It only took me a few minutes to open this issue explaning both the problem and a solution. Is it so tremendously difficult to add this information to the main page, rather than expect everyone to check every single issue for a solution? Really, common sense is the least common of senses it seems. If the main release doesn't work for the new GPUs and there are alternative versions, don't provide a link or a small text note, just expect people to check every issue one by one. |
Well, So no stable release for 50s 🤷♂ |
It's pinned btw |
I believe the project may be for all intents and purposes abandoned by its creator. There hasn't been an update in like 8 months with various other features also missing (i.e. support for newer model architectures) so the readme is probably the least of its issues. From what I can see, the only activity is from other contributors trying to respond to issues here and not much else going on. |
I see. Also explains SD 2.1 not working for months and still not being fixed (even on my old 1080 ti) |
Forge seems to be the effective continuation of this style of webui and it supports quite a few of the newer model architectures like flux, however depending on your workflow and/or needs it still lacks some features and support for certain addons. For example the training tab available in A1111 is missing entirely on Forge, which I personally use a lot for training embeddings. But hey, at least it is being actively developed/improved compared to this one, so it has potential. |
Checklist
What happened?
As suggested, I start the fresh install process by using the pre-release ZIP file, then running update.bat, then running run.bat, which triggers the following:
But then, it will fail to launch. There is a way to fix this, but the user has to follow these specific steps manually:
Steps to reproduce the problem
Go through the normal NVIDIA GPU installation process and try to launch 1111.
What should have happened?
The run.bat should have detected the incompatibility issue and downloaded https://download.pytorch.org/whl/nightly/cu128 rather than https://download.pytorch.org/whl/cu121. The user shouldn't have to wait for a very long download of over 2 GB, and then have to manually reinstall with another very long download of over 3 GB. This workaround is far from an acceptable solution, and the assumption by developers that all users have fast internet connections is NOT some universal truth. A lot of people have really slow internet connections and they have to make do with that. And a lot of people don't know how to fix this issue (the manual reinstall). You shouldn't expect the average 1111 user to know how to fix it entirely by themselves.
What browsers do you use to access the UI ?
No response
Sysinfo
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: