TheFerumn
commented
2 days ago Since everything works well in zluda, I think that the inpaint problem is not related to my PC.
Its not so simple. When you use ZLUDA then SD downloads different packages so your environment is set up differently. It can be totally related to your PC. You said you deleted every package with pip freeze commands ? If you did it correctly then i doubt there is anything we can do about it. Can you show your Sys Info ? Its in Settings/sysinfo
*MAIN: I need to be able to use inpaint with lora and do it in pictures from 20482048.** It should work, TheFerumn on RX570 4GB has directml inpaint running even with lora.
Yes but never on such a big resolutions due to 4GB.
Harbitos
This story started from here: 44 — It says in more detail what I have already tried to do.
I tell you: everything works well on ZLUDA, I can use lora in inpaint, but zluda cannot make images larger than 1024*1280, so I switched to directml. And it turned out that zluda and directml generate images at the same time for me.
But on directml inpaint, it doesn't work with any lora, even if I change the model and prompt with resolution. But everything works perfectly without lora! I was even able to make images with a resolution of 2048 2048 in 15-25 minutes in inpaint without lora. And I can also generate 2048 2048 images in 44 minutes in txt2img.
I made pictures in txt2img with arguments: (inpaint works here, but does not change the picture, the result of the picture is unchanged)
I did inpaint with arguments: (crashes, showing
press any key to continue...)I tried to write other (--always-low-vram --all-in-fp16) arguments, but it didn't help.
And there was also
[W dml_heap_allocator.cc:120] DML allocator out of memory!when there were arguments:I was able to set up the arguments (I don't remember which ones, and I can't reproduce it right now) once in such a way that after that I noticed that the generation in inpaint is going on! There are changes in the picture! But at the end of 100% generation, it also crashed and did not save the picture. All this time, the console was being spammed:
A clean install of the SD did not help. Windows reinstalled this month. Reinstalling git, python, amd driver (or installing pro) did not help. If anything, the swap file is on automatically and it's about 20GB. Putting the swap file 1.5 times more RAM did not help, but when I made a mistake and put 2 times more, then my generation was 29% and then the PC froze, but the cursor moved, I was able to complete the work.
Since everything works well in zluda, I think that the inpaint problem is not related to my PC.
*MAIN: I need to be able to use inpaint with lora and do it in pictures from 20482048.** It should work, TheFerumn on RX570 4GB has directml inpaint running even with lora.
Changed settings: The
optimizations/Batch cond/uncondcheckmark has been removed. There are TAESD inVAE/VAE type for decode. They stand at 64 (a screenshot will be attached) inUpscaling/Tile size.Live previews/Live preview display periodis set to 2.Approximately these are the parameters I set every time: Changing gpu weights 0/1024 — no difference.
Tile size:
Console after inpainting with any lora:
@lshqqytiger, please help me.