The source render already looks good. It came out of Lumion, Twinmotion, or D5 at 4K. The team wants a final AI pass for more convincing light, richer materials, atmosphere, and the irregular details that make a clean computer image feel occupied.
That request appeared almost word for word in this morning's community sweep. It is a better starting point than asking a model to invent the building. It also hides a trap. Once the image enters an image-to-image graph, every unresolved defect becomes harder to classify. Did the model change the window, or was the window wrong before? Is the stone too warm because of the grade, or because the wrong finish left the model?
Do not begin with a model recommendation. Begin with an acceptance gate. A base render either carries the project facts cleanly enough to refine, or it returns to the rendering application.
AI refinement is an edit, not an inspection
ComfyUI is a node-based interface, not a guarantee of architectural control. Flux names a family of models, not a preservation setting. A 4K file describes pixel dimensions, not correctness. Those distinctions matter because the usual shopping list, model, interface, resolution, GPU, says nothing about whether the input is ready.
The community thread that prompted this article asks sensible questions about Flux versions, LoRAs, staged upscaling, and local hardware. A detailed reply also warns that edit models may do too little, make unwanted changes, or degrade the source. That is one user's experience, not a controlled benchmark. The operational lesson is still sound: preservation must be measured against a known input.
If the team has not approved what must survive, it cannot tell whether the AI pass preserved it.
The six-part base-render gate
| Gate | Pass condition | If it fails |
|---|---|---|
| Camera | Named view, approved crop, credible eye level | Return to model |
| Geometry | Openings, edges, levels, and joints match the issue | Return to model |
| Materials | Specified families are assigned in the right locations | Correct assignments |
| Light logic | Sources and shadow directions are internally plausible | Correct lighting setup |
| Content | Required furniture, planting, signage, and context are present | Add controlled assets |
| Evidence | Source file, model revision, render settings, and owner are recorded | Complete the record |
1. Lock the camera
A final-polish workflow should not discover the composition. Record the camera name, lens or field of view, eye height, crop, output ratio, and source application. Check verticals, foreground obstruction, horizon, and the amount of context the client needs. If the view feels weak, solve that in the scene where the camera remains editable and repeatable.
Save a low-opacity overlay or edge image from the approved base. It becomes the quickest test for later movement. The purpose is not to forbid every changed pixel. It is to make camera drift obvious.
2. Audit silhouette and junctions
Start with the building's silhouette, then move inward. Count major openings. Trace roof edges, slab lines, parapets, columns, stairs, balcony guards, and facade bays. Zoom into junctions where generated images often become persuasive but wrong: glazing corners, canopy supports, wall returns, recessed doors, handrails, and repeated mullions.
A missing joint should not be repaired with a prompt. Correct the model or source render so the project record and presentation image agree. Otherwise the image may look fixed while every future camera retains the defect.
3. Approve material identity before texture character
Separate material identity from material expression. Identity answers whether a surface is brick, precast concrete, clear glass, zinc, oak, or painted gypsum. Expression covers weathering, roughness variation, subtle stains, edge wear, and photographic texture.
The base must get identity right. AI can help explore expression within a stated limit. If the cladding family is undecided, label the image as a study and keep each option separate. Do not let a polishing pass quietly choose a product that the specification team has not.
4. Make the lighting physically legible
The source does not need to be beautiful, but its light needs an understandable cause. List the sun or sky condition, visible luminaires, emissive surfaces, and intended exposure. Trace cast-shadow direction. Check whether interior brightness relates to actual openings and fixtures.
An AI pass may soften a shadow, change color temperature, or add local contrast. It should not invent a second sun or make an unlit ceiling glow. When lighting logic is weak at the source, enhancement can turn an obvious draft into a confident fiction.
5. Divide scene content into fixed and flexible
Mark content that must match: a client logo, commissioned artwork, selected chair, accessibility sign, mature retained tree, neighboring building, or approved planting species. Supply exact assets where identity matters. Then identify content that may vary, such as generic pedestrians, cloud cover, loose planting density, or minor surface imperfection.
This division becomes the edit brief. The model is allowed to work inside the flexible list. The fixed list gets masks, overlays, local protection, or a manual composite after generation.
6. Package the source
Give the base image an identity before creating variants. Record project code, view name, model revision, source application, render date, dimensions, and reviewer. Keep the original output read-only. Store AI results beside it with graph or workflow version, model name, seed when available, and the operation performed.
A polished image without its base is almost impossible to audit. A base and variant pair lets a reviewer use difference blending, edge overlays, or a simple rapid toggle to spot unrequested changes.
Define the polish as a short work order
After the gate passes, write a one-paragraph work order. Name three things to improve, three things that cannot change, and the review scale. For example: improve overcast light separation, concrete roughness variation, and planting integration; preserve all geometry, camera, facade module, signage, and furniture selections; review at full frame, presentation size, and 100 percent.
Run a small proof before committing to a high-resolution path. Test a representative crop that includes a hard edge, glazing, a material transition, planting, and a person. A workflow that cannot hold those elements at proof size does not deserve an overnight 4K run.
When a pass fails, classify the failure. Geometry change means reduce the edit strength, add structure guidance, protect a region, or remove that task from the generative pass. Texture repetition calls for a different material treatment. Plastic people may need a separate local operation. Soft detail may belong in an upscaling stage. Do not answer every failure by adding more words to one prompt.
Our take: protect the expensive decisions
The appeal of final polish is restraint. The design, camera, and specification work are already there. AI is invited to improve a narrow visual layer, not reopen the project. That makes the base render more important, not less.
A studio should be willing to reject its own source image before blaming the model. Fix project facts where they originate. Approve what must survive. Test the smallest difficult crop. Then refine.
The cheapest bad render is the one that never enters the polish queue.
Editorial basis: the 27 September 2026 ArchiGen AI intel sweep, including a current r/StableDiffusion request about using Flux and ComfyUI to polish already strong 4K renders from Lumion, Twinmotion, or D5. The quoted workflow goals and reported difficulties are community statements, not ArchiGen testing. This article makes no performance claim for a specific model or GPU; the acceptance gate and work-order method are editorial recommendations.