Skip to content
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

Pixart Sigma images are garbled #57

Open
TemuPaulMcCartney opened this issue May 30, 2024 · 3 comments
Open

Pixart Sigma images are garbled #57

TemuPaulMcCartney opened this issue May 30, 2024 · 3 comments

Comments

@TemuPaulMcCartney
Copy link

For some reason, Pixart Sigma images are coming out as some sort of incomprehensible mess. I followed the directions as best I could and used the sample workflow, but this is the result:
ComfyUI_PixArt_00002_

Mind you, the prompt is unchanged: "pixelart drawing of a tank with a (blue:0.8) camo pattern". I assumed this was a VAE issue, but changing the VAE has little to no effect. Everything has been uninstalled and reinstalled, but I've had no success. Any help would be sincerely appreciated.

@city96
Copy link
Owner

city96 commented May 31, 2024

Yeah, this definitely seems odd, I can't really think of anything that would cause it. Could you maybe tell me the following:

  • What model file(s) you used
  • Python and pytorch versions
  • GPU make/model

Plus maybe a copy of the workflow to be sure (you can export it as json and drag-and-drop it here)

@TemuPaulMcCartney
Copy link
Author

Hi! Thank you so much for responding!!! Sorry for the lack of info.

Models:

Python and Pytorch:

  • Python version: 3.10.11
  • pytorch version: 2.3.0+cu121

Hardware:

  • RTX 4090. Drivers are the most recent update.

Here's the workflow file! Thank you so much for your time.
pixartbad(2).json

@city96
Copy link
Owner

city96 commented Jun 2, 2024

Well, no issues with the workflow or the pixart model file, so it must be something else. I assume there's no errors/warnings in the console? (you can ignore the "Not using xformers!" one, that one doesn't apply anymore).

I haven't used those exact text encoder files, but I don't see why they wouldn't work. You could test using the FP16 T5 model files from here I guess. Could also try setting the device to "cpu" or leaving it on "gpu" but setting the dtype to "FP16" and see if that changes anything.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants