For the complete documentation index, see llms.txt. This page is also available as Markdown.

Controlling AI output

How Intangible's three modes give you real control over AI output – scene fidelity in Build, framing in Compose, model choice in Visualize.

Prompt-only generation gives you powerful output and no control surface: a character that drifts between shots, a composition you can't pin down, a client's product the model keeps re-interpreting. The render that comes back is someone else's idea of the brief.

Intangible's three modes are the control surface. Each mode is one lever.

  • Build locks the scene. Objects, props, time of day, imported CAD, brand-true reference images. Everything that belongs in the shot, you place. The model honors what you brought.

  • Compose frames the moment. Camera position, lens, aspect, aim target. Spatial decisions the model can't override.

  • Visualize picks the model. Photoreal, stylized, video with first-and-last-frame interpolation. The auto-prompt is editable; the scene grounds it.

A render you can put your name on isn't a single prompt. It's three locked decisions.

Which lever for which problem

The most common control failures with prompt-only tools, and where Intangible solves each:

What you're trying to control
The right lever
Where to start

Same character or product across every shot

Build (Image Reference)

Image reference

Specific framing, lens, aspect ratio

Compose

Camera controls, Lenses

Photoreal vs stylized look

Visualize (model picker)

Models

Lighting and time of day

Build (Sky) plus Visualize (Lighting Presets)

Lighting presets

Brand-specific style across the project

Visualize (Custom Styles)

Custom styles

Specific 3D geometry the asset library doesn't have

Build (Smart Import or Generate 3D)

Generate 3D Asset

A character or product the model has never seen

Build (LoRAs)

LoRAs

Reference image being ignored / livery not showing

Build (use a generic object name)

Image reference

Why this works when prompting alone doesn't

Pure prompt tools render from text. Text is lossy. "A red sports car on a wet street at dusk" generates a plausible red sports car, not the 2024 Bronco the client briefed. The model fills in what it doesn't know, and the gaps drift between renders.

The one exception to "the fix isn't in the prompt": a too-specific object name is a prompt problem. The object's name flows into the final prompt, and a name like "Gulfstream G550" makes the model imagine its own version and override the reference image you attached. Keep names generic ("private jet") so the reference wins. The full precedence – geometry, then image reference, then the prompt – is in Image reference.

Intangible passes the AI model a structured 3D scene plus a prompt. The geometry, the placement, the bound reference images, and the camera framing are all there as structured input. The prompt is one piece, not the whole brief. See How the visualizer thinks for the technical version.

The practical version: every Intangible page below is one of the levers. When a render comes back wrong, the fix is almost never in the prompt.

Where to go next

Last updated

Was this helpful?