Inconsistent with the A1111 SD generation result？

[tsjslgy]

Used my own LORA, sent PNG information directly, same Prompt and seed, all the same but the results were different, and the quality was very low.
Tried several times with the same result, wondering if it was really the same thing.

[lllyasviel]

there was some similar reports like #85
but they are mostly caused by users forgetting to turn on some features that are deeply hidden in their original A1111 settings, like code former, etc.
usually the difference can be resolved after some investigation of all old/new settings

[tsjslgy]

sdwebui

forge

seed:12345 step:20

a1111 webui




forge

[tsjslgy]

This is with seed 12345, the difference would be more noticeable when generating higher quality images.

[CCpt5]

You should go into settings for both A1111 and Forge and open up Sys Info (tab) in settings. Pick "Open as txt in new page". Do that on both A1111 and Forge at the same time and just go between tabs making sure all of the values you have set for A1111 are the same in forge. As mentioned there are a few optimizations that will make SD non-deterministic w/ generations (XFormers for example can).....probably something there causing a difference.

The other thing that probably isn't it, but there's a bug at the moment (#51) where the preview/live-preview does not display at full resolution even if it's set as full in settings. If you're watching and judging quality of generations by the preview while rendering (before the batch completely finishes) that could be why you're seeing bad quality. I reported this issue the other day here: #51 - The outputted files and final preview post-batch should be correct/full quality though.