Manual / The cloud / Generating a themeiCity 2 · Windows

Generating a theme

A theme is the largest job iCity runs: roughly 220 to 275 credits and about twenty minutes for the materials, props and elements that dress your city. It stops halfway to show you guide images and ask whether to carry on, and that pause is the cheapest place to change your mind.

Before you start

A theme dresses a city that already exists. It does not draw one. Both of the following have to be true before the Design module will let you send anything.

  • You are signed in. Signed out, the Theme screen reads Sign in to start designing and offers a Sign In button instead of the composer.
  • The scene holds a city. With an empty scene the composer shows Generate a city first — the theme is applied to your city (Draft module). in amber and the send button is disabled.

Switch the header toggle to DESIGN. The rail's first tab reads Theme, and it opens on a choice screen headed How should this city be dressed? with three buttons: Start with default theme, Generate theme and Append from a project. Only the middle one goes to the cloud. The other two are described in Themes.

generating-a-theme-choice-screen.png

The Design rail's Theme tab in the iCity Editor, signed in, with a city in the scene and no theme yet: the heading 'How should this city be dressed?' above the three stacked buttons 'Start with default theme', 'Generate theme' and 'Append from a project'. Header toggle visible set to DESIGN.

/docs-shots/blender/
The Theme tab's choice screen, before anything has been sent.

Press Generate theme. The choice screen is replaced by the composer: a prompt box, a row of icons under it, and the conversation thread below.

Note

Your city is not your .blend. It lives in the engine process and is saved by the header S button into your project folder — How iCity fits with Blender explains what is stored where.

Writing the prompt and attaching references

Type into the box. Enter sends the prompt; Shift+Enter starts a new line. An empty prompt is refused with Please enter a prompt first. The placeholder text reads write something to generate.

generating-a-theme-composer.png

The Theme tab composer in the iCity Editor immediately after pressing Generate theme, signed in with a city in the scene and nothing typed yet: the empty prompt box showing its 'write something to generate' placeholder, the row beneath it with the Generation Mode icon and the attach-references icon at the left and the up-arrow send button at the right, the camera icon near the send button, and the empty conversation thread below.

/docs-shots/blender/
The composer: prompt box, the icon row under it, and the empty thread below.

Two icons sit at the left of the row under the box. The second one attaches reference images — its tooltip reads Attach reference images (max 10). It opens a file browser filtered to .png, .jpg, .jpeg and .webp. Attached images appear as chips above the box, and the cloud shapes the guides from them, so a reference does more to steer the result than another sentence of text.

Near the send button there is also a camera icon: Screenshot a region of the viewport and attach it to this prompt. You drag a box over the 3D viewport, the shot opens big with Accept and Retake, and Accept puts it in the same tray — counting against the same ten.

generating-a-theme-attachment-tray.png

The Theme tab composer with three references attached — two image files and one viewport screenshot accepted from the camera icon — so the chips are showing in the tray above the prompt box, each with its thumbnail and remove control, and a prompt typed into the box beneath them. Frame the icon row so the attach icon and the camera icon are both in shot.

/docs-shots/blender/
Reference chips in the tray above the prompt box, one of them a viewport screenshot.
Note

Attachments are consumed. Once the job is created the tray is cleared, and it is cleared again after a guide re-roll. If you want to reuse the same references on a later prompt, attach them again.

Choosing where the assets come from

The first icon in that row opens Generation Mode. Its tooltip reads Generation options — what to generate, asset sourcing, editing modes. The same settings appear on the Generate with AI popup's Assets row; there is one setting behind both.

Under Assets, pick how the job sources its materials and props:

Asset modeWhat the job does
Mixed (default)Reuse a matching library asset when one exists, generate otherwise.
Select onlyOnly select from the library — never generate new assets.
Generate onlyAlways generate fresh assets — never adopt from the library.
generating-a-theme-generation-mode.png

The Generation Mode popup opened from the first icon in the composer's row: the Generate materials and Generate props switches above, both on; the Assets row with Mixed, Select only and Generate only and Mixed picked; and the Edit material and Edit prop switches below, both off.

/docs-shots/blender/
The Generation Mode popup, with the Assets row on Mixed.

Above that row, Generate materials and Generate props are both on. Turning one off leaves that lane out of the job; the log records the change as Generation lanes: props off for the session. Below the row, Edit material and Edit prop switch the composer out of theme generation entirely and into regenerating assets you already have — leave both off for a theme.

Sending it

  1. Press Enter, or the up-arrow send button at the right of the icon row.
  2. The city is exported first. If the export fails — no geometry, or a collection switched off in the Outliner — nothing is submitted and the reason is reported.
  3. The project is then saved for you. If no project is open, one named Untitled (N) is created and adopted first.
  4. The job is created and the city files are uploaded. The thread prints Job 1a2b3c4d created — analyzing and the step ladder starts moving: Submitting, Analyzing, Guides.
generating-a-theme-job-running.png

The Theme composer a minute into a real theme run: the thread showing the prompt that was sent and the line 'Job 1a2b3c4d created — analyzing', the step ladder underneath with Submitting done and Analyzing or Guides current, and the send button at the right of the icon row rendered as a red stop square rather than an up arrow.

/docs-shots/blender/
A live theme job: the created line in the thread, the step ladder moving, and the send button as a red stop square.

While the job is alive the send button becomes a red stop square. Pressing it cancels the run on the server. The local record is closed only if the server agreed, so read the reply: if it says the pipeline did not stop, the run is still going.

Your draft city is not locked while a theme job runs. The dress arrives later as new objects in their own collection, so Draft editing and the gizmos stay available for the whole twenty minutes.

If the library already has something close

Before generating, the cloud may search its theme library for matches to your prompt. When it finds some, the job pauses and a popup titled CHOOSE A THEME opens over the viewport. Each card shows that theme's guide images, a counter reading Theme 1 / 4 with its name, and a line of detail — who made it, its quality score, how many times it has been used, how many materials and props it carries, and its category.

generating-a-theme-choose-a-theme.png

The CHOOSE A THEME popup over the 3D viewport on a paused job that found at least four matches: one card showing its guide images, the counter reading 'Theme 1 / 4' with the theme name, the detail line naming the author, quality score, use count, material and prop counts and category, and the buttons Use this theme, Load more, and Close (decide later).

/docs-shots/blender/
The CHOOSE A THEME popup, offering a library match before anything is generated.
  • Use this theme adopts the theme shown. Nothing is generated, so nothing is spent on generation.
  • Load more appears on the last card while the cloud has further batches to show.
  • Generate new replaces that button once there are no more to load. It opens a small box for optional extra details, then ignores the library and generates a fresh theme.

The close button on this popup reads Close (decide later), and that is exactly what it does — the job waits on the cloud for your answer.

The guide review

The job makes reference images first and stops. A popup titled THEME GUIDES opens by itself over the 3D viewport with the sheets this attempt produced — a city scene, a building close-up, a road view and whatever else the pipeline sent.

generating-a-theme-guides-popup.png

The THEME GUIDES popup over the 3D viewport on a job paused at the guide gate after one re-roll, so the seed counter is present: the guide sheets (city scene, building close-up, road view) laid out, the ‹ and › arrows with the counter reading 'Seed 2 / 2', and the Approve, Regenerate and Close (decide later) buttons.

/docs-shots/blender/
THEME GUIDES — the checkpoint the whole flow is built around.

This is the checkpoint the whole flow is built around. Guides are the cheap part of the run; materials, props and elements are the expensive part, and they do not start until you press Approve. Look at the images and decide here, not after the credits are gone.

ControlWhat it does
‹ and › beside the imagesPage between attempts. The counter reads Seed 1 / 2 and only appears once there is more than one.
ApproveUse the shown seed and continue generation.
RegenerateGenerate a new set. This one stays, reachable with the arrows.
Close (decide later)The job waits on the cloud. Nothing is cancelled and nothing continues.

Regenerate opens the Generate with AI popup on the Theme tab, banner-headed → Regenerating Theme 1a2b3c4d. What you type there is a refinement note, not a new prompt — leave it empty for a plain re-roll. Reference images attached in that popup steer the new set. Sending it ends the current job and continues the run in a child job, which is what the thread then follows.

If it goes wrong

Once the Theme Guides popup is closed, no button in the interface reopens it. The job is still waiting, but the way to end it is the composer's stop button — the review itself has no cancel control.

What it costs and how long it takes

Budget roughly 220 to 275 credits and about twenty minutes for a full theme. The Generate with AI popup's Theme tab shows ~219 credits · ~18 min. That is a fixed number built into the addon — an average of ten completed runs taken in August 2026, not a quote from the server — and it runs low: theme runs measured since have come in at 272 to 274 credits. Budget for the upper end.

A one-credit analysis fee is charged for the moderation pass when the job is created, whatever the run turns out to cost. Every guide re-roll is its own job with its own moderation pass and its own credits, so a theme you re-roll twice costs more than the figures above. What credits are and where yours come from is covered in Credits & plans.

Warning

Leave Blender open until the job comes back. Job tracking lives entirely in the running session — if you close Blender mid-run, the results cannot be recovered from the interface, even though the credits were spent.

What runs in the cloud explains why, and what Dress City from Outputs can and cannot rescue.

When it finishes

Materials and props that finish early are installed into your library part-way through the run, so the library grows before the job ends. At completion, four things happen without you pressing anything.

  • The generated assets are downloaded into your local library.
  • assets.json — the theme's list of materials, props and elements — is written into the project folder.
  • The Design cards pick up the theme's materials and props, and material slots are assigned by category.
  • The dressed city is imported into the iCity2 Front End collection.

The thread closes with the credits the cloud actually charged:

text
Job 1a2b3c4d complete

From here, changing the draft re-dresses the city with this theme — see Re-dressing after a change — and What is in your .blend after a dress describes what the collection holds.