Today's sweep pulled six community threads on this, across r/comfyui, r/FluxAI and r/StableDiffusion. Reddit thread IDs sort roughly by age, and these run from well back in the sequence to this month, so the span is long. A question that recurs that steadily is not a sign that people are lazy searchers. It is a sign that the answers on offer do not close it.
What everyone is actually asking
Strip the six threads down and they want the same thing, phrased three ways. Take a drawing or a rough model that already has the building right. Add the realism. Do not change the building.
The word that keeps appearing is "maintain." Maintain details, maintain composition, maintain the design. Nobody in these threads is asking for a picture of a house. They already have the house. They drew it, or they modelled it badly and quickly, which is what a working model looks like on a Thursday. They want it to look photographed, with the window heads where they put them.
That is a much narrower request than "make good images," and it is the request that separates architectural use from every other use of these tools.
What keeps getting offered
Two kinds of reply dominate.
The first is the tutorial pack. Today's sweep surfaced one of the popular ones: forty simple workflows and seventy-five minutes of material. That is a genuinely useful resource and it is not what the asker needs, because forty workflows at under two minutes each is a tour of what the software can do, not a solution to the one thing they asked. Nobody bounces off ComfyUI for lack of workflows to try.
The second is philosophy. One highly upvoted thread on making Stable Diffusion behave like Midjourney offers: find a method that works for you, consume all the tools you can find, prompting is just a guide. That is fine advice for someone making art. For someone with a planning submission on Friday it is a shrug in the shape of a sentence.
Nobody bounces off ComfyUI because they ran out of workflows to try.
Both replies answer the question "how do I make an image with this," which was never in doubt. Both skip the question that was actually asked.
The half that never gets answered
Here is the mechanical truth underneath all six threads, and it is why a workflow file cannot be the answer on its own.
Adding realism to an existing image means running a diffusion pass over it. How much that pass is allowed to change is the denoise value, and the input geometry is held by whatever conditioning you have attached, typically a depth or line-based ControlNet. Those two settings are in tension, permanently, and the tension is the whole job.
| Setting | Low | High |
|---|---|---|
| Denoise | Your building survives intact, and the output looks like your input with a filter on it. Little realism gained. | Convincing materials, real light, and a facade that has quietly grown a window you did not draw. |
| ControlNet strength | The model is free to reinterpret, so geometry drifts between runs. | Geometry holds, but the output inherits every flaw in a rough working model, including the wall that never got resolved. |
There is a band where those two land in the right place. That band is narrow, it moves with the model you are using, and it moves again with the character of your input, because a clean lineart export and a grey-clay 3D viewport screenshot do not want the same numbers.
Which is why the honest answer to "can someone share a workflow" is that the graph is the easy part and the numbers are the work. You can hand someone a node layout in thirty seconds. You cannot hand them the denoise value that suits a model they have not shown you.
And then the part that ends meetings
Suppose you find the band. You produce one excellent image. This is where the community threads stop, and where architectural work starts.
You need seven more views of the same scheme that read as the same building. Same brick, same glazing tint, same time of day, same mood. Diffusion does not naturally give you that, because each run is an independent sample and the model has no memory of the material it invented last time. Pinning it takes fixed seeds, locked prompts, per-view conditioning discipline, and usually a reference image doing the heavy lifting. We have written this up separately as the set consistency problem, and the seed mechanics in what a seed actually locks.
Then the client approves the image and asks for one change. Move the entrance, warm up the brick, lose the tree. You need the same building back with one thing different. If your setup cannot do that, it is not a rendering pipeline, it is a slot machine that occasionally pays out in something you can show.
None of the six threads asks about either of these, which is the most telling detail. People ask how to get the first good image. They discover the other two problems privately, later, usually while a deadline is running.
How to ask so the question can be answered
If you are going to post the question, post it in a form that admits a real reply.
Show the input. The single biggest reason these threads die is that nobody can advise on settings without seeing what is going in. A lineart export, a clay render and a textured viewport grab are three different starting points with three different answers.
State what must not move. "The window positions and floor levels are fixed, everything else is negotiable" gives people something to aim at.
Say how many images you need. One hero shot and a set of eight are different engineering problems, and anyone answering for the first will mislead you about the second.
Name your hardware and your model. A workflow tuned for a big local model on a 24GB card is not advice for a laptop, and renting the GPU changes the calculation again.
Our take
ComfyUI does this job well and it is the most controllable option available, which is exactly why it keeps attracting architects and then losing them. The control is real, and it is all manual. The plugin tools have spent two years building opinionated defaults over the same underlying idea, and defaults are what you are buying, as we set out when comparing an enhancer against a self-built pipeline.
Our position has not changed: if you are going to run it, build the small graph yourself rather than collecting other people's, and start from a sketch-to-photoreal setup you understand end to end. But the sharper point from today's threads is about the question itself.
Stop asking for a workflow. Ask for a denoise value, for your input, for a set of eight. The people who can answer that are the ones worth listening to, and the reason you rarely get a reply is that most of the people posting have only ever made one image at a time.
Written from the 21 July 2026 intel sweep. Thread titles and quoted phrasing are as captured from public Reddit search results on 21 July 2026 and may be edited or removed by their authors. Relative thread ages are inferred from Reddit ID ordering rather than displayed timestamps, so treat the span as approximate. Denoise and ControlNet behaviour described here is general to current diffusion pipelines and varies by model, sampler and conditioning type; test on your own inputs rather than adopting numbers from any post, including this one.