-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Awful Flux Fill results. (blurry, grainy results) #5746
Comments
It seems that not all GPUs are compatible, and there may be issues under certain seeds, only a few specific seeds are normal. |
It should be related to this: |
Strange, I have RTX 4070 gpu, should work fine I think? Because 4070 has Ada Lovelace architecture, which should work as expected. |
me too, always wierd blurry |
I tried many times, depending on the resolution and expanding the area of the image. Same goes for partial repaints. Noise appears when large areas are redrawn. Simple compositions and lower raw images are easier to achieve good results at 768 or 512 resolution. Additionally, it relies on random seeds. In short, very uncontrollable. . |
I have successfully used Flux fill 1024x1024 20 steps on my 2080ti-22GB using this diffusers-bnb-nf4 code https://huggingface.co/sayakpaul/FLUX.1-Fill-dev-nf4 |
Buried in a Swarmui commit is the comment:
I can confirm that making this change is a substantial improvement for me on a few test generations. |
All these generations that are shown in my examples were made with Guidance of 30. |
Are you inpainting or outpainting? I ask because normally I expect a flux fill output to contain a mix of content leftover from the original image and generated content, and yours look uniformly mushy everywhere. |
That was inpainting with the whole image masked, to show the issue more clearly. As for generating with small patches, it's the same, new generated objects are mushy too |
Should be fixed now. The flux inpaint model does not work in fp16 unlike the other flux models. The fix is to make it inference in fp32 on cards that do not support bf16 which is slow but will make it work. |
Thx, I can confirm it is working for my 2080ti now, though slower. |
Expected Behavior
A proper image being generated without the said artifact (blurry, grainy). Like on the image above when generating on Replicate Space.
Actual Behavior
Generates images with awful, mushy quality.
Steps to Reproduce
Use a standard (recommended) workflow for flux fill. You can load either a standard 22 gb dev model, or use a GGUF one, the results are nearly the same.
Debug Logs
Other
Have encountered another person on CivitAI using an community made FP8 version of this model, who describes that the results are exactly the same as I am encountering.
The text was updated successfully, but these errors were encountered: