Updated on: 30 October 2026
The most common rendering problems in architecture are wrong scale, camera and perspective errors, noise and fireflies, light leaks, stretched or missing textures, crashes and slow renders, endless revisions and, with AI tools, results that drift from the design. Most have a simple technical cause, and most are fixed before the render starts: in the model, the camera or the scene settings.
This guide takes them one at a time: what you see, what causes it and how to fix it in any render program, plus where ArchiVinci helps and where it does not. A checklist at the end sums them up.
Wrong Scale and Misplaced Elements
A render can be beautiful and still wrong. When a door, a stair or a whole facade comes out at the wrong size, the image no longer matches the drawings, and clients and consultants notice. The usual causes:
Units that do not match on import: a model drawn in millimeters opened as meters or inches, so everything is off by a factor of 1000 or 25.4
CAD or BIM data that loses or moves geometry on the way into the render program
Linked models or layers that are out of sync, so an old version of one part sits in the scene
Manual edits that stretch an object instead of setting it to a dimension
How to Fix It
Set the units explicitly in both programs before you export, and check one known dimension after the import: a standard door or a floor-to-floor height shows a scale error at once.
Keep one shared origin and orientation for every linked model.
Place people and furniture at their real size early: entourage is the quickest scale check, and clients make it too.
Render again only once the geometry matches the current drawings.
If the plan itself is in doubt, rebuild it in Floor Plan Maker, ArchiVinci's browser floor plan app. When you draw over a picture of a plan, you calibrate the scale from one known length; wall lengths and furniture dimensions then appear as you draw, like in a CAD program, rooms show their areas, and the 3D view lets you check the layout before any render.
An AI renderer does not repair scale. ArchiVinci never opens your model or reads its dimensions: it follows the image you upload, so a scale error in the view stays in the render. Fix the model first, then take the screenshot.
Check the plan before you render Draw the plan in Floor Plan Maker or upload the one you have: wall lengths and furniture dimensions appear as you draw, like in a CAD program, rooms show their areas, and the 3D view and walkthrough show the layout before any render. Export DXF for CAD or GLB and OBJ for 3D programs. Drawing, 3D and exports are free in a desktop browser; reading an uploaded plan with AI costs 1 credit on a free account. |
Camera and Perspective Errors
A render with the wrong camera looks off even when every dimension is right. Verticals lean, rooms look deeper or smaller than they are, and a two-story house looks like a tower. The picture above shows the effect at its strongest: when the camera looks straight up, every vertical line converges.
Common Causes
A tilted camera: as soon as it looks up or down, vertical lines converge (three-point perspective)
The wrong eye height: a camera at 3 m or at knee height changes how big a space feels
An extreme focal length: very wide lenses stretch the corners and exaggerate depth, long lenses flatten it
A field of view chosen to fit a whole room into one shot
How to Fix It
Put the camera at eye height, about 1.5 to 1.7 m, for street and interior views, unless the image is meant as an aerial.
Keep the camera level, or use the two-point perspective or vertical correction setting of your modeling or render program, so verticals stay vertical.
Use moderate focal lengths for interiors and show a large room in two views rather than one very wide one.
Compare the view with a photo of a similar real space; our guide on how to make renders look real covers camera, light and materials in more depth.
AI does not correct a camera either. ArchiVinci keeps the viewpoint of the image you upload, so set the camera in your model first, then turn the screenshot into an AI rendering in seconds.
Noise, Grain and Fireflies
Grain all over the image, or single white dots on walls and floors, comes from the way ray-traced and path-traced renderers work: they estimate light with random samples, and too few samples leave noise. Fireflies are isolated bright pixels caused by small, strong light sources, glossy reflections or light that reaches a surface only after several bounces. Interiors lit only through windows are the hardest case. Our guide to ray tracing explains the sampling behind it.
Raise the samples or lower the noise threshold, and render a small test region before the full image.
Turn on the denoiser that most current engines include, then check fine textures and small text: a denoiser can blur them.
Add light where the room is dark instead of only adding samples: a larger or brighter source, or a light portal in the windows where your engine has one.
Against fireflies, limit the brightness of indirect light (often called clamping) or make tiny light sources larger.
Light Leaks, Z-Fighting and Shadow Artifacts
A bright seam along the edge of a closed room, where a wall meets the floor or the ceiling, is a light leak: light passes through geometry that is too thin, has gaps or is made of single-sided planes. Engines that cache or bake indirect light are the most prone to it; our guide to global illumination covers this and the other artifacts of bounced light.
Give walls, floors and roof slabs a real thickness and let them overlap at the corners instead of meeting edge to edge.
Close the gaps between linked models and delete stray single faces.
Raise the quality of the indirect light cache, or use full path tracing for the final image.
What Is Z-Fighting?
Z-fighting is the flickering, striped pattern that appears where two faces lie in exactly the same plane, such as a floor finish modeled on top of the slab or a duplicated wall. The renderer cannot decide which surface is in front, so the two alternate from pixel to pixel and from frame to frame. It is most visible in real-time engines, viewports and animations. The fix is to delete the duplicate face or move one of the two surfaces a few millimeters away from the other.
Shadows that float away from an object usually mean that it hovers slightly above the floor. Jagged or blurred shadow edges in real-time engines come from a low shadow resolution, which a quality setting fixes.
Stretched or Repeating Textures
Stretched wood grain on a curved wall, bricks twice their real size, or the same stain repeating every meter across a facade: texture problems make materials look fake at once. They usually come from the mapping, not from the texture file.
Common Causes
Missing or automatic UVs, so the image is projected at the wrong angle onto curved or sloping faces
A texture size that does not match reality, for example a 60 × 60 cm tile shown at 2 m
One small texture tiled across a large surface, which makes the repeat obvious
Low-resolution maps seen close to the camera
How to Fix It
Use box or cube mapping with a real-world size for walls and floors, and unwrap the UVs of curved or organic objects; our guide to UV mapping shows how.
Measure one unit of the material (a brick, a tile, a board) and set the texture to that size.
Break the repeat with a larger texture, a random offset or rotation where your program offers it, or a second layer of dirt or variation.
Match map resolution to camera distance: the surfaces closest to the camera get the sharpest maps.
AI can also make the texture itself. In March 2024 Adobe announced Text to Texture for Substance 3D Sampler, a beta feature powered by Adobe Firefly that generates a texture from a text description (Adobe's announcement).
To compare finishes on an existing render or photo without mapping anything, use ArchiVinci's Edit module (ArchiGPT): mark the surface and, with Apply texture, choose one of 103 library materials in 15 categories or upload your own sample. Each run gives a new image, not a texture map for your model, so it is a way to choose a material before you set it up in the scene.
Fix a detail in a render by describing it Upload a render or a photo and tell ArchiGPT what to change, a material, a piece of furniture or the light, and it returns the edited image. A new account starts with 3 free credits. |
Missing Textures and Broken Links After Export
Pink, black or checkered surfaces, or a scene that looks fine on one computer and bare on another, are the classic sign of missing textures: the model moved between programs or machines, and the image files did not move with it. It happens most when a project passes between Rhino, Revit, SketchUp, Blender and Unreal Engine.
Common Causes
Texture paths that point to a folder on another computer
A file sent without its textures, because they were linked rather than packed
An export format that does not carry materials in full: OBJ, for example, keeps them in a separate .mtl file that has to travel with it
Materials that the receiving program reads differently, so they arrive without maps or at the wrong scale
How to Fix It
Keep every texture inside the project folder and use relative paths.
Before you send a file, use your program's command to collect or pack its external files.
After an import, open the program's list of missing files, relink what it reports and render a small test.
Where a renderer runs as a plugin inside the modeling program, the model does not have to be exported at all: as of October 2026, Enscape lists plugins for Revit, SketchUp, Rhino, Archicad and Vectorworks.
ArchiVinci avoids the file transfer altogether: it works from an image, a JPG, PNG or WebP screenshot or export of up to 5 MB from any program, so no model, texture or material has to travel. SketchUp users can also render from inside SketchUp with ArchiVinci's extension and an ArchiVinci account; it sends the active view or up to four saved scenes at a time, and our list of SketchUp plugins describes it. For plans, Floor Plan Maker exports DXF (no native DWG), SVG, PDF, PNG, GLB and OBJ.
Crashes, Out of Memory and Slow Renders
A GPU render engine has to fit the whole scene into the graphics card's memory (VRAM). When it does not, the render stops with an out-of-memory error, crashes or, in some engines, falls back to a much slower mode. Dense vegetation, high-resolution textures on every object and copied rather than instanced furniture are the usual causes.
Use proxies or instances for trees, cars and repeated furniture.
Reduce the texture size of objects far from the camera, and purge unused materials and models.
Render a test at a quarter of the final size before you start the full image.
Update the graphics driver and check the card against your engine's requirements; our guide to GPUs for rendering compares current cards.
When renders are simply slow, estimate the time before you commit: our render time calculator gives you a figure to plan with, and cloud rendering services add machines when a deadline is close. For a still image of a design option, ArchiVinci renders an uploaded view online in seconds, so your computer's GPU and VRAM do not matter.
Why Is My Render Black or Blank?
A black or empty image usually has a plain cause: the camera sits inside a wall or behind a clipping plane, the lights or the sun are switched off or below the horizon, the exposure is far too low, or the render crashed before it saved. Check the camera position first, then the lights, then the exposure, then the log.
Revisions, Scope Creep and Deadlines
Not every rendering problem is technical. Scope creep, when client changes keep adding rounds beyond the agreed plan, means rendering the same views again and again, and a tight deadline leaves no time to check light or textures. Both can cost more than any software problem.
Write the number of revision rounds into the contract and price extra rounds; as our guide to rendering costs shows, quotes differ in how many rounds they include.
Agree the camera views and the massing on quick clay renders before materials and light are set.
Freeze the model on a date, and log every change requested after it.
Plan the final renders backwards from the deadline, with a day kept free for corrections.
In the early rounds, AI images help the client choose before the full render: ArchiVinci turns a screenshot of each option into a photorealistic image in seconds, and with a plan you can run it again as often as you need. Using the results for client work or marketing needs an active plan; plans are on the pricing page.
When an AI Result Drifts From Your Design
AI renderers bring a problem of their own: with many tools, the result can drift from the design. A window moves, a railing disappears, the roof changes pitch or the proportions shift between two runs. The reason is that an AI renderer does not read your model: it generates a new image every time, with your upload as the reference.
ArchiVinci's default engine, ArchiVinci 4.0, keeps the perspective, geometry and colors of the image you upload, so materials and light change while your design stays. Every run draws a new variation, so run it again for another option or refine a detail with Edit render.
Left: the uploaded image. Right: the result of the prompt "Modern house with white plaster walls, timber cladding on the upper floor, large glass openings, a lawn and a few trees." with the Daylight button, in ArchiVinci's Exterior module on the default engine.
How to Keep Your Design
Start from a clean view: hide grids, section planes and notes, and pick a view where walls, windows and roof read clearly.
Use the prompt for materials, light and mood rather than describing the building again, and keep it short (the app warns above 200 characters).
To change one part only, use Edit render on the result: mark the area and describe the change, and only that area is changed.
For another option, run it again: each run draws a new variation.
Present the result beside your upload in the before/after viewer, so the client sees the same view with new materials and light.
Our prompt guide for architecture shows how to word the request, and our list of the best AI rendering tools covers the other tools for this step.
A simpler rendering workflow No render engine to set up: upload a view of your project, write what you want to see, and get a photorealistic render that follows your image. A new account starts with 3 free credits. |
Rendering Problem Checklist
Use the table as a quick check before a render goes to a client.
Problem | Likely cause | First fix |
|---|---|---|
Wrong scale | Units that do not match on import | Check one known dimension; set units before export |
Leaning verticals | Tilted camera | Level the camera or use two-point perspective |
Grain and white dots | Too few samples, small strong lights | More samples, a denoiser, clamped indirect light |
Bright seams at room edges | Thin or open geometry | Thicker walls, overlapping corners |
Flickering stripes | Two faces in the same plane (z-fighting) | Delete or offset the duplicate face |
Stretched or repeating texture | Wrong mapping or texture size | Real-world size mapping, unwrapped UVs |
Pink or missing textures | Broken file paths | Pack or collect the files, relink |
Crash or out-of-memory error | Scene larger than the VRAM | Proxies, smaller textures, a small test render |
Black or blank image | Camera inside geometry, no light | Check camera, lights and exposure |
Endless re-renders | Unlimited revisions | Revision rounds in the contract, clay previews |
AI result changes the design | A new image on every run | Short prompt, Edit render on the area, another run |
Most of these problems are cheaper to prevent than to fix: check scale, camera and geometry before the final render, and keep the first test render small.
Try it in ArchiVinci
Describe a building in a sentence, or upload a sketch or a 3D model view: ArchiVinci generates concept images that follow it. A new account starts with 3 free credits.
For early design concepts: AI concept generator
Render a sketch, photo or model view: AI render
Frequently Asked Questions
What is the difference between a rendering issue and a design error?
A rendering issue happens while the image is made: wrong lighting, missing textures, noise or a bad camera. A design error is in the project itself: a wrong dimension, a clash or a room that does not work. A rendering issue is fixed in the scene and the design stays the same; a design error has to be fixed in the drawings first, and the render only shows it.
Can AI fix these problems without a human?
No. AI denoisers clean up noise, and AI renderers give a finished image without a scene setup, but neither checks whether the design is right. Architects still set the camera, check the geometry and decide what the image should show.
Does ArchiVinci work with Revit, Rhino and SketchUp?
Yes, through an image: ArchiVinci works with any program that can save a screenshot or an export, including Revit, Rhino, AutoCAD, Archicad and Blender. You upload a JPG, PNG or WebP of up to 5 MB. For SketchUp there is also an extension that renders from inside the program with an ArchiVinci account. ArchiVinci does not open model files such as .rvt, .3dm or .skp.
What should architects check before adding an AI tool to their workflow?
Before you add an AI tool, check:
Which inputs it takes (an image, a sketch or a model file) and which programs it works with
Whether your plan allows the results to be used commercially
How much control you keep over geometry and details, and how you correct a single area
Testing a tool on a view of a real project answers most of these questions faster than a feature list; a new ArchiVinci account starts with 3 free credits.