Open notdanilo opened 3 months ago
@lstein I suspect this will still be a problem on v4.0.0. Not sure how to approach this myself...
There's a partial fix in #6076, which will be in v4.0.0 or v4.0.1. You should be able to generate without seamless enabled with this fix, but if you enable seamless, I'd expect the same error.
Sorry, GitHub closed this but I didn't mean to.
What happens if you set the CUDA_VISIBLE_DEVICES
environment variable to cuda:1
instead of using —device
?
CUDA_VISIBLE_DEVICES=“cuda:1” invokeai-web
I am unable to test it for the following weeks.
Changing
python .venv\Scripts\invokeai-web.exe %*
to
set CUDA_VISIBLE_DEVICES=1 & python .venv\Scripts\invokeai-web.exe %*
worked on Windows.
Is there an existing issue for this problem?
Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
cuda:0 RTX 4090 cuda:1 RTX 3080
GPU VRAM
cuda:0 24GB cuda:1 10GB
Version number
3.7.0
Browser
Chrome
Python dependencies
No response
What happened
Running it with --device "cuda:1" isn't working.
What you expected to happen
To be able to run it on cuda:1
How to reproduce the problem
No response
Additional context
It looks like both cuda:0 and cuda:1 are being used, even if I try to select cuda:0 Maybe some code parts of the code is harcoded to cuda:0?
Discord username
not.danilo