Single materials & props

The fast lane

A theme job dresses the whole city and takes about twenty minutes. A single-asset job makes one material or one prop and comes back in a minute or two. Use it when the city is already dressed and one thing is wrong: the asphalt is too clean, the benches are the wrong period, a facade wants a brick you do not have.

The lane is the same in both directions. Generate makes a new asset from a description. Regenerate makes another version of an asset the cloud already made for you. Both land in your local library, and both are tracked in the same composer thread a theme job uses.

• —You have to be signed in. Without a session the submit is refused and the log reads Sign in first to generate assets.
• —No city is required. Only a theme is blocked in an empty scene. A single material or prop is generated into your library and does not need a city to exist.
• —Only cloud assets can be regenerated. An asset you put in your own custom folder has no cloud identity, so Regenerate, Generate Model and Generate PBR all skip it. See Your own assets.

Opening the generator

Every route ends at the same popup, headed Generate with AI, with four tabs across the top: Prop, Material, Screenshot and Theme. What you pressed decides which tab it opens on and whether the footer button reads Generate or Regenerate.

Generating a new material or prop

1. Open the popup on the Material or Prop tab.
2. Describe it in the box. A plain generate needs a description — an empty box keeps the popup open and does nothing.
3. Optionally attach references. The attach icon under the box takes image files (PNG, JPG, JPEG or WEBP, up to ten), and the pick icon beside it lets you point at an asset already in your library as a style reference. These are this popup's own attachments and never touch the composer's tray.
4. Press Generate. The popup closes and the log reads Generate material submitted…, then Job 3f2a1b9c created — analyzing.

If the cloud finds close matches in the library it pauses and opens a Library Suggestions dialog headed The library already has close matches: — each match offers Use this, and the bottom of the dialog offers None of these — generate new. Closing the dialog without choosing leaves the job waiting on the cloud, and the dialog says so: No decision sent — the job is still waiting on the cloud.

When the job completes the asset is written into your library folder and the log names it. Nothing in the viewport changes on its own — assign the new material or prop from the card that needs it.

Saved 1 generated assets for 3f2a1b9c to the local library

Regenerating what is in the scene

There are two ways to re-roll something that already exists. Both send the same kind of job; they differ in how you point at the target.

One asset, from the browser. Open the asset browser, click the card, and press Regenerate. The Generate with AI popup opens with that asset as its source. Type an adjustment, or leave the box empty for a fresh variation of the original, and press Regenerate.

Several at once, from the composer. In DESIGN › Theme, press the first icon under the prompt box — the +, whose tooltip reads “Generation options — what to generate, asset sourcing, editing modes”. The menu that opens has an Editing mode group at the bottom: choose Edit material or Edit prop. A pick icon appears in the composer's icon strip. Picking the mode you are already in switches it back off.

1. Press the pick icon. The asset browser opens headed SCENE MATERIALS — PICK TO EDIT (or SCENE PROPS — PICK TO EDIT).
2. Click cards to add and remove them. The footer counts them: 3 selected — the prompt edits these.
3. Press Done. The picks come back as small tiles under the composer's prompt box; each tile has a × that drops it again.
4. Type an adjustment and send, or send an empty prompt for a fresh variation of each. The report reads Regenerating 3 material(s) — see the log for progress.

Each picked target is its own job. Three targets means three jobs, three sets of credits and three results, and each one is logged separately as it goes out.

Regenerating material 'Asphalt Wet 02'…
Regenerating material 'Sidewalk Concrete 04'…

Seeds, and what changes in the scene

A regenerated asset does not overwrite the original. It is stored as a new seed of the same asset, in its own folder beside the old one, so the version you were using is still there and still assigned.

In the asset browser, a card with more than one local seed carries a small badge at the bottom right of its preview reading more · 3. Click it to drill into that asset's versions — one card per seed, with a ← Back button and the heading Seeds of <name>. Selecting a seed picks that exact version, so an assign uses it.

Nothing in the viewport re-skins by itself when a single-asset job finishes. The result is filed in the library; a material only reaches the city when you assign it from the card that owns that category, and a prop only reaches the city when a placement or scattering system uses it. The one exception is an asset generated from a scattering card, which is added to the system that asked for it.

Generate Model and Generate PBR

Some assets arrive short of a piece. A prop can exist as an image with no 3D model; a material can carry a config that asked for texture maps that were never produced. Those two cases have their own buttons, and they are not regeneration — nothing about the asset is re-decided, and the result lands on the same seed it came from.

• —Generate Model — a prop card marked No 3D model. Its tooltip reads This prop has no 3D model yet — generate one from its image. A prop without a model cannot be assigned, so this button stands in for Assign.
• —Generate PBR — a material card marked No PBR maps: This material has no PBR maps yet — generate them from its base colour.

Both act on the whole selection, one job per asset, and neither sends a prompt. While a job is in flight the card dims behind a Generating… pane and stops responding to clicks, so the same asset cannot be queued twice — that state survives closing and reopening the browser.

What it costs and how long it takes

The popup prints an estimate in its footer, beside Est. cost:, and it changes with the tab you are on. These are fixed figures built into the addon, not a live quote from the server.

The material figure comes from completed jobs and is close. The prop figure is marked (est.) because it is the server's own formula rather than a measurement — no prop run had completed when it was written down. The theme figure runs low: a full theme is roughly 220–275 credits and about twenty minutes, and measured runs came back at 272–274.

Whatever the lane, one credit of analysis is charged the moment a submission is accepted, and the real cost is settled when the job finishes. Credits and plans explains what a credit is, where your balance is shown and what happens when it runs out.

While the job runs, the composer thread and the CLOUD ACTIVITY popup behind the cloud badge both carry it — Jobs, progress and errors covers reading them and what the failure cards mean.