# CAD Scene Help Center This file contains the complete published CAD Scene Help Center in canonical navigation order. ## Getting started and workspace map Canonical URL: https://cadscene.com/help/start-here/getting-started Summary: Set up your first CAD Scene project, learn the workspace, and send a first render. Last updated: 2026-08-06 CAD Scene turns words or a 3D screenshot into an architectural render. Each project keeps its settings, studies, and renders together. New accounts start with a five-step welcome tour. It introduces Create, Enhance, and Edit. Use Continue, the arrow controls, or the step dots to move through it. You can also skip the tour after confirming. The final step offers two useful starts: * **Create project** opens a new project named **Untitled Project**. * **Open the sample project** opens a prepared project you can inspect. A new empty project then asks how you want to set it up: 1. **Generate from a realistic image** uploads a Project reference image and generates the five Composition fields. 2. **Generate from a description** turns a short description into those fields. 3. **Pick a style** opens on **Built-in presets** and also lists your saved Presets. Choose **Skip for now** if you want an empty workspace. You can fill the project settings later. ### Use a directory prompt The public [architecture prompt directory](/architecture-prompt-library) can start a Project for you. Select **Use in CAD Scene** on one prompt. CAD Scene always creates a new **Untitled Project** for that prompt. It never opens or changes an existing Project. New accounts finish or skip the welcome tour first, then continue into the new Project. Text-only prompts open Create. Source-assisted prompts open Enhance and still need your own source image. CAD Scene fills and focuses the prompt. It does not select **Send**, charge credits, or start a render. If the saved handoff expires, return to the directory and select **Use in CAD Scene** again. ### From setup to first render The first working loop is Setup, Project, Study, then Render. Setup creates the shared Project context. A Study holds one view or option. Each send adds a render to that Study. The setup screen is the handoff into this loop. Its choices prepare the shared Project before you open a Study and send. If setup generation needs more credits, CAD Scene keeps the selected image or written description and opens the available plans and top-ups. After a verified purchase, **Continue** returns to that setup choice without generating automatically. Select **Generate** when you are ready. ### Workspace map The workspace keeps one project context around the active study. * **Studies rail:** The left rail lists studies. Its collapsed view shows study thumbnails and a **New study** button. * **Project settings:** The icon rail opens Overview, Style, Scene, Lighting, Materials, Entourage, Gallery, and Settings. The Overview tab summarizes the full Composition and Project reference image. * **Feed:** The center shows messages and renders from the active study. * **Composer:** The floating input card switches between Create, Enhance, and Edit. It also holds model settings, output count, references, and Send. * **Edit and Enhance panel:** On larger screens, the right panel holds the source-image chooser and image tools. On smaller screens, those tools appear with the Composer. * **Gallery:** The Gallery tab shows finished renders from every study in the project. * **Help menu:** The signed-in top bar opens the Help Center, Prompt Examples, or Contact Support. Public pages open in a new tab. Project settings apply across all studies. Switching studies changes the Feed, not the project's Composition. Learn the hierarchy in [Projects](/help/projects-and-studies/projects) and [Studies, Feed, and Gallery](/help/projects-and-studies/studies-feed-and-gallery). ### First render Create is the shortest first-render path because it needs no source image. 1. Open the sample project or finish one of the new-project setup paths. 2. Select **Create** in the Composer. 3. Write a clear description of the view you need. 4. Review the model, its available settings, and the output count if needed. 5. Select **Send**. Sending requires enough credits for the full request. Each output is charged separately, so increasing the count multiplies the per-image cost. See [Quality and cost](/help/rendering-and-results/models-quality-credits-and-daily-limits#quality-and-cost) for the verified model settings and cost breakdown. Create requires a non-empty prompt. If the project has no study yet, the first send creates one automatically. The new render appears in that study's Feed. It also appears in the project-wide Gallery after completion. A clear brief still sends in one step. If CAD Scene needs one outcome-changing decision, the Composer asks a short question before the render starts. Answer it to continue automatically, or select **Skip and Send Now** to render the original prompt. If you already have a 3D screenshot, use [Enhance](/help/modes/enhance#choose-a-source-image) instead. Use [Edit](/help/modes/edit#mark-a-region) to change marked parts of an image. ### Replay the welcome tour Open **Settings**, then **Onboarding**. Select **Reset onboarding**, confirm, and the welcome tour restarts at step one. Resetting onboarding does not change your projects. It also leaves the sample project untouched. For prompt controls, references, slash commands, and keyboard shortcuts, open [Composer, slash commands, and keyboard shortcuts](/help/reference-and-troubleshooting/composer-slash-commands-and-keyboard-shortcuts). ## Projects Canonical URL: https://cadscene.com/help/projects-and-studies/projects Summary: Create, name, configure, trash, restore, and permanently delete CAD Scene projects. Last updated: 2026-08-09 A Project is the container for one design effort. It holds project settings, studies, and every render made inside them. ### Project setup options A new empty project offers three starting points. Each one prepares the shared Composition before the first render. * **Generate from a realistic image** uses a Project reference image to generate the five Composition fields. Choose this when you have a finished render or a photograph of a real place. * **Generate from a description** turns a short written brief into the five fields. Choose this when the design direction is clearer in words. * **Pick a style** opens on **Built-in presets** and applies one complete five-field direction. **My presets** remains available for returning users. Select **Skip for now** to enter the workspace with empty fields. You can configure every Project setting later. ### Project hierarchy The Composition and optional Project reference image sit at Project level. Every Study uses that shared context. Each Study keeps its own Feed and renders. The Project view keeps shared context above the separate Study branches. A change to Project settings affects future sends across those branches. ### Create a project Open the Projects dashboard and select **New Project**. CAD Scene creates an **Untitled Project** and opens it immediately. The dashboard shows up to 20 projects per page. Before a project has a finished render, its Project reference image appears as the project thumbnail. After the first finished render, the render becomes the main thumbnail and the Project reference image moves to a small inset at the bottom right. ### Projects created from directory prompts Selecting **Use in CAD Scene** in the [architecture prompt directory](/architecture-prompt-library) always creates a new **Untitled Project**. The handoff never reuses the most recent Project and never changes another Project's settings. The new Project opens directly in the Composer. Its setup screen stays out of the way because choosing the prompt is the starting decision. The prompt is filled but not sent. If a browser retries the handoff, CAD Scene returns to the same newly created Project instead of creating duplicates. The setup screen and Projects dashboard link directly to [Project setup options](#project-setup-options). To rename a project, open its actions menu and choose **Rename**. You can also select the project name in its workspace header. Press Enter or leave the field to save. Press Escape to cancel the change. ### Project settings Project settings are the shared render context for the whole project. They include the Composition and the optional Project reference image. The Composition contains five fields: * Style * Scene * Lighting * Materials * Entourage Every study reads the same saved fields. A field edit stays local until you select **Save** or press Command-S on macOS or Control-S elsewhere. The **Settings** tab also holds **Default render settings**. These include the model and its supported options. Create may expose Aspect. Models may expose Resolution. GPT image models may expose Quality. You can override these settings for a Composer session without changing the project defaults. The app-wide **Default model** in `/settings` seeds new projects only. Each project then stores its own model and native defaults. Those project defaults seed new Composer sessions across its studies. For field generation, Presets, and versions, read [Composition and the five fields](/help/composition-and-presets/composition-and-the-five-fields). ### Project reference image The Project reference image helps write the five Composition fields. Select **Generate Composition** to read the image and replace those field values. The image is not sent as a render input. Create and Enhance read the saved fields. Edit uses a separate source image, named regions, and one required prompt. You can replace or clear the Project reference image. Clearing it does not change existing renders or saved field values. See [Image roles and source-image preparation](/help/images-and-references/image-roles-and-source-image-preparation#project-reference-image) before choosing an image for this role. ### Trash and restore The Projects dashboard separates **Active** projects from **Trash**. To move a project: 1. Open the project's actions menu. 2. Select **Move to Trash**. 3. Open the **Trash** tab to find it. A project in Trash is read-only. Its workspace shows a restore notice, and project changes are blocked until restoration. Select **Restore** from the Trash row or the workspace notice. The project returns to **Active** with its contents intact. Permanent deletion is available only in Trash: 1. Open the trashed project's actions menu. 2. Select **Delete forever**. 3. Read the warning and confirm **Delete forever**. This removes the project and all its renders. It cannot be undone. ## Studies, Feed, and Gallery Canonical URL: https://cadscene.com/help/projects-and-studies/studies-feed-and-gallery Summary: Understand studies, the active study Feed, and the project-wide Gallery. Last updated: 2026-07-15 A Study is an independent thread inside a Project. Its Feed stays separate, while every study shares the same project settings. ### Studies and shared settings Use separate studies for different views, options, or review rounds. A project can hold multiple studies without duplicating its Composition. There are two ways to start one: * Select **New study** in the left rail. * Send from a project that has no study yet. CAD Scene creates one first. A new study starts as **New study**. After its first render request, CAD Scene tries to create a short title from that first prompt. If that step fails, the study remains **New study** and rendering continues normally. The expanded rail shows each study's name, latest render thumbnail, and recent activity. The collapsed rail shows the same studies as circular thumbnails. Select either form to make that study active. The active study appears in the URL and controls the center Feed. When no study is selected explicitly, the most recently active study opens. Changes to Style, Scene, Lighting, Materials, Entourage, or Default render settings belong to the Project. Every study uses the saved Project values on its next send. Learn more in [Projects](/help/projects-and-studies/projects#project-settings). ### Feed and Gallery The Feed and Gallery answer different questions. **The Feed shows the active study.** Each render request becomes a Feed card. Its output images stay grouped with that request. Select another study to see that study's history. **The Gallery shows the whole Project.** It gathers completed renders from every study. Opening a Gallery image does not change the active study. The Gallery view combines results without merging their Study histories. Return to a Study Feed when you need its prompt and request context. Use Gallery controls to narrow or order the project: * Select one or more studies, or leave **All studies** selected. * Filter by Create, Enhance, or Edit. * Filter by model or quality. * Sort the currently loaded results by **Most recent** or **Oldest**. * Open **Trash** to restore deleted renders. Gallery fetches up to 20 renders per page, newest-first. **Oldest** reverses only the results loaded so far. It is not project-wide oldest-first until every page has been loaded with **Load more**. The default Gallery excludes renders moved to Trash. Restoring a render returns it to the normal Gallery. An empty, unfiltered Gallery means the Project has no finished renders yet. Clear active filters before treating an empty result as an empty Gallery. Use the Feed when prompt context matters. Use the Gallery when comparing work across studies. For retries, variations, deletion, and history, read [Render actions and history](/help/rendering-and-results/render-actions-and-history#feed-and-gallery). ### Render clarification history When a render brief needed questions, a completed clarification appears as a thin row immediately before its Render card. The preview lists each question and answer in order. Select **read more** to see the initial prompt and the full ordered answers. The clarification does not repeat the final prompt. The Render card shows that submitted prompt. Clear briefs, skipped questions, failed checks, and abandoned clarifications add no row. The row belongs to the same Feed message as the Render. It does not add another page item or Gallery result. When every Render in that message moves to Trash, the clarification row leaves the Feed with its card. ## 3D models and viewer Canonical URL: https://cadscene.com/help/projects-and-studies/3d-models-and-viewer Summary: Upload an architecture model, compose a clay view, and use a saved capture as the source for Enhance. Last updated: 2026-08-11 This reference owns supported formats, Viewer tools, setup corrections, and conversion recovery. Follow [the 3D model render tutorial](/help/tutorials/use-3d-models-in-ai-renders) for the complete capture-to-Enhance procedure. Conversion costs no credits. One package must contain exactly one root model and be 200 MB or smaller. ### Supported files The software column gives conservative examples, not an exhaustive compatibility list. Export support varies by software and version. Check your installed export options. | Accepted format/family | Software commonly able to export it | Requirements/notes | | --------------------------- | -------------------------------------------- | ----------------------------------------------------------------------------------------- | | GLB or glTF with companions | Blender | GLB is simplest. Include every glTF companion file. Remote links are rejected. | | IFC or IFCZIP | Revit, Archicad, Vectorworks | Use IFC2X3 or IFC4 with visible building elements. | | STEP/STP | Rhino, Fusion 360, SOLIDWORKS, FreeCAD | Include valid, visible solids or surfaces. | | IGES/IGS | Rhino, Fusion 360, SOLIDWORKS, FreeCAD | Include valid, visible solids or surfaces. | | OpenCascade BREP | FreeCAD or other OpenCascade-based tools | Include valid, visible solids or surfaces. | | FCStd | FreeCAD | Include visible shapes. Plugins are not loaded. | | BLEND | Blender | Save a static visible scene. Scripts are disabled and presentation data is removed. | | FBX | Blender, SketchUp Pro, 3ds Max, Cinema 4D | Export a static visible exchange scene. | | DAE | Blender, SketchUp Pro, Cinema 4D | Export a static visible exchange scene. | | ABC | Blender, Maya, Houdini, Cinema 4D | Export a static visible exchange scene. | | USD, USDA, or USDC | Blender, Maya, Houdini, 3ds Max | Export a static visible exchange scene. | | USDZ | Reality Composer Pro or other USDZ exporters | One example source. Export a static visible exchange scene. | | OBJ | Blender, Rhino, SketchUp Pro | Include triangle geometry and required companions. Units or orientation can be ambiguous. | | STL | Blender, Rhino, FreeCAD | Include triangle geometry. Units, up axis, and Front are not defined. | | PLY | Blender | Include triangle geometry. Units or orientation can be ambiguous. | | 3MF | Rhino, FreeCAD | Include visible triangle geometry. | | 3DS | 3ds Max | Include visible triangle geometry. | | 3D DXF | AutoCAD, Rhino, FreeCAD | Include 3DFACE or mesh entities only. Units or orientation can be ambiguous. | | 3DM | Rhino | Save shaded cached render meshes. Do not use SaveSmall. | Unsupported authoring formats include RVT/RFA, SKP, MAX/C4D, DWG, PLN/VWX, NWD/NWC, and modern DGN. This list is not exhaustive. Export a supported exchange format first. A package can be one file, a file with companions, a folder, or a ZIP. ### Upload and open a model The **3D models** panel accepts one file, a companion set, a folder, or a ZIP. Conversion continues when you leave the Project. Ready tiles open Viewer; processing tiles show the current conversion stage. **Tutorial:** [Find the 3D models panel and upload](/help/tutorials/use-3d-models-in-ai-renders#find-the-3d-models-panel-and-upload). A replacement keeps the current model available until the new version is ready. A failed replacement leaves the current model unchanged. ### Inspect and compose Viewer includes Layers, Camera, Appearance, Section, Detail, and **Model setup**. Camera controls projection and lens. **Views** provides standard directions and named saved views. **Presentation** is the default clay appearance. Layers hides or isolates geometry. Section reveals interiors. **Reset view** recenters the complete model without changing those choices. **Tutorial:** [Compose the camera in Viewer](/help/tutorials/use-3d-models-in-ai-renders#compose-the-camera-in-viewer). ### Capture and Enhance Capture mode locks the camera and hides Viewer chrome and helpers. Its crop defines the exact PNG frame and output size. **Download PNG** saves locally. **Save capture** keeps the Viewer capture with the Project. After **Save capture**, the result opens with **Enhance this capture** as the primary action. It closes the viewer, switches the Composer to Enhance, attaches the saved image as the source, and focuses the prompt. It does not send. **Stay in capture mode** returns to the same crop and controls. **Tutorial:** [Capture and save the shot](/help/tutorials/use-3d-models-in-ai-renders#capture-and-save-the-shot). Saved captures remain under **Captures** and **This project**. Deleting the source model removes it from the Project immediately. Saved captures remain. ### Correct model setup Use **Viewer → Model setup** only when scale or orientation is wrong. Camera Orbit and saved Views do not change the model itself. 1. Check the imported units and up axis. 2. For STL, choose the units used during export. 3. Choose **Y up** or **Z up**. 4. Use the quarter-turn controls, or orbit to a side and choose **Set current view as Front**. 5. Review **Setup preview · Not applied**. 6. Choose **Reset preview** or **Apply correction**. Applying a correction clears saved Views tied to the old geometry. Existing captures remain unchanged. Replace the source when you need X-up, mirroring, pitch, roll, or an arbitrary angle. ### Recover a conversion An initial conversion with no ready version cannot open. A failed replacement keeps the current ready model openable. Use the tile **Actions** menu, then choose **Retry conversion** or **Replace file**. * IFC needs visible building elements. * Solid CAD may need repaired solids or visible surfaces. * DCC files need a static visible scene. * DXF needs 3D face/mesh entities. * 3DM needs cached render meshes from a shaded Rhino view. ## Choose Create, Enhance, or Edit Canonical URL: https://cadscene.com/help/modes/choose-create-enhance-or-edit Summary: Pick a CAD Scene mode from your starting material and the change you need. Last updated: 2026-08-08 Choose Create for words, Enhance for a 3D screenshot, and Edit for marked changes to an existing image. ### Compare the modes Start with the material you already have. Then name what must remain fixed. Words point to Create. A fixed 3D view points to Enhance. A local image change points to Edit. The Composer mode picker keeps all three choices together. Changing mode changes the required inputs, not the Project or active Study. Before a paid render starts, CAD Scene checks the brief after its input and credit checks. A clear brief sends without interruption. A hard ambiguity asks one question at a time. Choose an answer or write your own. The final answer sends one resolved prompt automatically. Clarification never changes the selected mode or saved Composition. A mode conflict opens **Review before sending**. Select **Back to composer** to change modes, or select **Continue with Create**, **Continue with Enhance**, or **Continue with Edit** to send under the mode already selected. For an actual clarification question, **Skip and Send Now** renders the original prompt without keeping the clarification. #### Create starts from a description Use Create when no source image should define the scene. * **Required:** A non-empty prompt. * **Optional:** Up to five composer reference images. * **Uses:** The project's five-field Composition. * **Preservation aim:** Nothing from a source image because there is no source. Create is useful for early concepts and new views. Read [Create](/help/modes/create#create-requirements). #### Enhance starts from a 3D screenshot Use Enhance when the camera and geometry already exist. * **Required:** One explicit source image. * **Optional:** A prompt and up to five composer reference images. * **Uses:** The project's five-field Composition. * **Preservation aim:** Instructs the model to preserve camera, angle, perspective, framing, proportions, and major geometry. * **Change instruction:** Instructs the model to change materials, textures, lighting, atmosphere, vegetation, sky, and surface finish. Enhance is usually the right choice for a Rhino, SketchUp, Revit, or Blender screenshot. Read [Enhance](/help/modes/enhance#choose-a-source-image). #### Edit starts from an image and marked regions Use Edit when you want the model to preserve most of the source. * **Required:** One source image, at least one marked region, a unique name for every region, and one prompt that references every name. * **Optional:** Supported composer reference images. * **Uses:** Automatic editable region names and the required global Edit prompt. * **Preservation aim:** Instructs the model to preserve unmarked pixels, camera, framing, and the existing photographic style. * **Change instruction:** Instructs the model to change the marked regions. Small drift can still occur. Nano Banana models accept Edit references. GPT Image 2 Edit uses only the source and mask. Read [Edit](/help/modes/edit#mark-a-region). ### Source images and reference images A source image is the image Enhance or Edit modifies. Choose it in the Enhance or Edit image panel. A composer reference image supplies visual guidance. It can suggest materials, palette, mood, or content. It does not replace a required source image. The Project reference image has a third role. It generates Composition fields and is never used automatically as a mode source. See [Image roles and source-image preparation](/help/images-and-references/image-roles-and-source-image-preparation#compare-image-roles) for the complete comparison. ### Quick choice * Have only an idea or brief? Choose **Create**. * Have a screenshot whose view should stay fixed? Choose **Enhance**. * Have a finished image with one local change? Choose **Edit**. * Need a new camera view from an existing screenshot? Choose **Create** and describe the new view. Enhance is designed to retain the source camera. ## Create Canonical URL: https://cadscene.com/help/modes/create Summary: Generate a new architectural render from a prompt, project Composition, and optional references. Last updated: 2026-07-31 Create generates a new architectural image from text. It combines your prompt with the project's five-field Composition. ### Create requirements Create requires one non-empty prompt. It does not require a source image. Before sending, review the Composition and write the current view. Add references only when they clarify materials or mood. Then choose the model, available settings, and output count. 1. Select **Create** in the Composer. 2. Review the Project's Style, Scene, Lighting, Materials, and Entourage. 3. Describe the camera, scene, and result needed for this send. 4. Attach references only when they clarify materials, mood, or content. 5. Choose the model, supported settings, and output count. 6. Select **Send**. The saved Composition is included with the render request. Empty fields remain empty, so the prompt carries more of the brief. Create also checks for usable Style, Scene, Lighting, Materials, Entourage, and an explicit view. It uses the saved Composition, the current prompt, and clear visual references together. If an outcome-changing direction is missing, the Composer asks one short question with suggested bundles and a custom reply. Your current prompt wins over a conflicting reusable field for this render. Mode rules still remain mandatory. After the final answer, CAD Scene submits one resolved prompt automatically. Select **Skip and Send Now** to send the original prompt instead. Skipping discards the answers and stores no clarification. Use project settings for decisions that should persist across studies. Use the prompt for the current image. See [Composition and the five fields](/help/composition-and-presets/composition-and-the-five-fields#the-five-fields) for the field boundaries. #### Prompt example > Create a street-level view of a compact courtyard library. Use warm red > brick, weathered brass, and pale stone. Set soft overcast afternoon light. > Add two people, parked bicycles, and restrained planting. Keep the image calm > and editorial. This prompt names the Scene, Materials, Lighting, Entourage, and Style. A useful prompt gives each visible decision one clear phrase. Avoid repeating a long Composition in every send. Save durable decisions in the matching fields, then use a shorter prompt for each view. ### Prefilled directory prompts The [architecture prompt directory](/architecture-prompt-library) contains complete, adaptable Create and Enhance prompts. **Use in CAD Scene** creates a new Project and fills the matching Composer mode. Review the prompt against your Project before sending. Change any project, material, light, camera, or activity detail that does not fit. A prefilled prompt never sends automatically and never spends credits until you select **Send**. ### Composer reference images Composer reference images are optional visual context for the current send. Create supports them with every current model. You can attach up to five references. Use the attachment control to: * upload an image; * choose a render or upload already in CAD Scene; * attach the latest successful render. References guide materials, palette, mood, or content. They are not treated as the scene to reproduce. Create still starts from the written brief. A reference supplies the render view only when the prompt explicitly asks to use that reference's view. Attaching it alone does not replace the written view requirement. Remove an image before sending if it conflicts with the prompt. The Composer prevents more references after the limit is reached. For each send, model and available settings affect capability and cost. Resolution appears when the model offers it. Create also exposes Aspect. GPT image models expose Quality. The output count creates parallel results from the same brief. Read [Models, quality, credits, and daily limits](/help/rendering-and-results/models-quality-credits-and-daily-limits#choose-a-model) and [Parallel Variants versus Variations](/help/rendering-and-results/parallel-variants-versus-variations#composer-variants). ### Review a Create result Compare the result against three inputs: prompt, Composition, and references. Check the camera and scene first. Then inspect materials, lighting, and entourage. **Static example:** Create starts from a written view brief. It combines that brief with the saved Composition and any references attached to the message, then holds the finished result for review. If one decision is wrong, revise the narrowest source. Change the prompt for this view. Change a Composition field when every future render needs the fix. ## Enhance Canonical URL: https://cadscene.com/help/modes/enhance Summary: Restyle a 3D screenshot while aiming to preserve its camera, framing, geometry, and proportions. Last updated: 2026-08-08 Enhance turns a 3D screenshot into a finished render. It aims to preserve the source view while applying the project's Composition. ### Choose a source image Enhance requires one explicit source image. The prompt is optional. Choose the exact source view first. Then add only guidance that changes its finish. Before sending, review the model, available settings, and output count. 1. Select **Enhance** in the Composer. 2. Drop an image into **Scene to enhance**, choose one from CAD Scene, or use the last render. 3. Add an optional prompt for changes specific to this send. 4. Attach references only when they clarify materials, light, mood, or content. 5. Choose the model, supported settings, and output count. 6. Confirm the source view. 7. Select **Send**. The source image is the scene being restyled. It is not the same as a composer reference image. References guide materials, palette, mood, or content. Before upload and rendering, CAD Scene checks the brief for a hard conflict. It may ask one short question. Your current prompt can override a conflicting Composition field for this render, but it cannot override Enhance camera, geometry, framing, or dimension rules. A request that appears to belong in Edit opens **Review before sending**. Select **Back to composer** to change modes. Select **Continue with Enhance** to send the original prompt under Enhance preservation rules. CAD Scene never switches modes automatically. For an actual clarification question, **Skip and Send Now** sends the original prompt and stores no clarification. It does not bypass the required source image or Enhance preservation rules. Enhance accepts up to five composer references with every current model. The required source does not count as one of those references. The Project reference image is also separate. CAD Scene does not insert it into Enhance automatically. Read [Image roles and source-image preparation](/help/images-and-references/image-roles-and-source-image-preparation#source-image) for the three roles. ### Prepare your source image Use the exact camera, angle, and framing you want in the result. Enhance instructs the model to preserve: * camera position, angle, lens, and perspective; * overall composition, framing, aspect ratio, scale, and proportions; * buildings, walls, doors, windows, and major site features. Enhance is designed to change finish, not design geometry. It instructs the model to change materials, textures, lighting, atmosphere, color, vegetation, sky, and surface qualities. #### Source screenshot checklist Before attaching the image: * frame the intended final view in your 3D tool; * keep important geometry visible and unobstructed; * remove temporary selection marks or guides you do not want interpreted; * crop an extreme panorama if the model reports an unsupported aspect ratio; * convert HEIC to JPEG or PNG if your browser cannot decode it. See the verified comparisons in [Prepare Enhance images](/help/images-and-references/image-roles-and-source-image-preparation#prepare-enhance-images). #### Dimensions and model rounding Uploads are preprocessed before storage. Images above 2048 pixels on the long edge are reduced proportionally. Enhance instructs every model to preserve the source composition and aspect ratio. This instruction does not guarantee the original pixel dimensions. Models with multiple Resolution choices expose supported presets such as 1K, 2K, or 4K. Enhance instructs the model to preserve source proportions, so it does not expose Aspect. GPT image models may also expose provider Quality. Exact controls depend on the selected model. Resolution sets a target tier, not a promise of the source's exact pixel dimensions. The composition-preservation instruction still applies. For current quality choices and model behavior, read [Models, quality, credits, and daily limits](/help/rendering-and-results/models-quality-credits-and-daily-limits#choose-a-model). ### Check the result Compare stable geometry before judging materials. Window positions, roof lines, camera height, and crop should still correspond to the source. **Static example:** Enhance begins with a bare 3D scene. It instructs the model to preserve the camera, framing, and geometry while changing materials, light, and atmosphere. If the structure drifts, simplify the optional prompt and use a cleaner source. Keep references focused on finish rather than alternate geometry. ## Edit Canonical URL: https://cadscene.com/help/modes/edit Summary: Mark named regions, reference every name in one prompt, and preserve the rest of the source. Last updated: 2026-08-10 Edit changes named parts of one existing image. It requires a source, at least one marked region, and one prompt that references every unique region name. ### Choose a source image Select **Edit**, then choose the image under **Image to edit**. You can: * drop or select an image from your device; * choose a render or upload already in CAD Scene; * use the latest successful render. The selected image is the source that Edit modifies. A composer reference image is only extra visual guidance. Read [Image roles and source-image preparation](/help/images-and-references/image-roles-and-source-image-preparation#prepare-edit-images) before choosing a difficult source. Changing the source clears the current canvas and marked regions. Choose the source before painting. ### Mark a region Use the image tools to identify every area that may change. 1. Choose the source before drawing. A source change clears the canvas. 2. Mark each change with Rectangle or Brush. Keep every area tight. 3. Review the automatic names. Edit any name that needs more context. 4. Write one prompt that mentions every unique name as a distinct reference. 5. Review the source, regions, model settings, and output count. Then select **Send**. * **Rectangle** marks a rectangular area and is selected by default. * **Brush** paints a freeform area. * **Eraser** removes painted mask pixels. * **Undo** and **Redo** step through mask changes. * **Clear all** removes every marked region after confirmation. The brush-size control changes the Brush and Eraser width. Nearby strokes can meet one or several existing regions. CAD Scene pauses the completed mark and asks how to resolve it: * **Extend Region A** adds the mark to the one region it meets. * **Merge 2 regions** combines every region the mark meets. The oldest region keeps its name. * **Create new region** keeps the mark as a separate named region, even when its bounds overlap another region. * **Discard stroke** removes the pending mark. The pending mark is only a preview. It is not part of the saved canvas, region count, mask export, or Send input until you choose Extend, Merge, or Create new. The canvas and its controls stay locked while the choice is open. Select **Group nearby strokes automatically** with Extend or Merge to remember that grouping choice for the current source image. Later nearby marks extend one region or merge several without asking. A checked footer control shows when automatic grouping is active. Clear it to restore the choice. The region cap follows the selected model's Edit capability. Every current model supports up to eight regions. At the cap, Rectangle and Brush stop adding regions. Eraser, Undo, Redo, Clear all, and region deletion remain available. If a model switch leaves too many regions, remove the stated number or choose a compatible model. CAD Scene preserves the existing work instead of deleting or merging it. Overlapping regions keep separate names and bounds, but they share editable pixels. Write compatible, concrete instructions for the shared area. Tighten the marks when two requested changes cannot coexist. **Static example:** Mark a tight rectangle around each intended change. CAD Scene assigns `Region A` and `Region B`. One prompt references both names. On larger screens, keep the Edit panel open when sending. Closing it removes the active canvas from the page, so CAD Scene asks you to reopen and review the regions. ### Name each region CAD Scene names new regions `Region A`, `Region B`, and onward. After `Region Z`, the sequence continues as `Region AA`, `Region AB`, and so on. Names are editable control references. They are never intended as readable text inside the image. Keep every name non-empty and unique. Names remain attached to the marked area during normal delete, Undo, Redo, and canvas remounts. Deleting a region does not rename the survivors. A later region continues the sequence instead of reusing a deleted name. You can keep the automatic names. Use a more descriptive name only when it makes the prompt easier to read, such as `North wall` or `Lobby doors`. ### Write the Edit prompt The Edit prompt is required. Mention every unique region name as a distinct, unquoted reference. Then state the change for that area. ```text In Region A, replace the ceiling with oak boards. In Region B, replace the people with dogs. ``` The names tell CAD Scene which marked areas the sentences address. They do not ask for the words `Region A` or `Region B` to appear in the result. Put exact new readable scene text inside straight double quotes: ```text In Region A, change the sign to "Library". In Region B, keep the existing lettering. ``` Only the quoted word `Library` is requested as new readable text. Existing scene text stays unless the prompt asks to change or remove it. A name mentioned only inside quotes does not count as a region reference. After an invalid **Send**, CAD Scene keeps the draft and opens **Before you send** with every fix. Select **Review region names** to close the dialog and focus the first empty or duplicate name in visual order. Select **Update the prompt** to close it and focus the prompt when a name reference is missing. After those requirements pass, CAD Scene checks the Edit brief for a hard semantic conflict. It may ask one short question before preparing the mask. This check does not add the Project Composition to Edit. The resolved prompt still has to reference every region name, and the final unmarked-area preservation lock remains mandatory. A mode conflict opens **Review before sending**. Select **Back to composer** to change modes. Select **Continue with Edit** to send the original prompt under Edit rules. CAD Scene never switches modes automatically. For an actual clarification question, **Skip and Send Now** sends the original prompt and stores no clarification. It cannot bypass the source, region, name, or prompt requirements. Inline name errors appear only after an invalid Send. Changing a region or name clears them until the next invalid Send. See [Troubleshooting and recovery](/help/reference-and-troubleshooting/troubleshooting-and-recovery#edit-requirements) for exact recovery steps. ### How Edit sends the request Edit sends the source image, one union mask covering all marked areas, and one compiled spatial prompt in a single image request. It does not send one request per region. Intersecting named bounds stay as separate spatial instructions. Their shared pixels appear once in the union mask, and every applicable instruction still applies there. Names and bounds are metadata. They are not separate uploaded masks. If one instruction cannot be prepared safely, CAD Scene uses the marked area's spatial placement and the prompt wording. The render continues with the same source and mask. This recovery does not change the prompt requirements. ### What Edit aims to preserve Edit sends the source with a mask. The render request instructs the model to modify only mask pixels. It also instructs the model to preserve camera, perspective, framing, overall composition, and the existing photographic style. Generative image models can still introduce small differences or follow a shared boundary loosely. Edit regions are not pixel-perfect layers. Keep regions tight and instructions concrete. Review shared pixels and unmarked edges before accepting a result. Edit instructs every model to preserve the source composition and aspect ratio. This instruction does not guarantee the original pixel dimensions. Models with multiple Resolution choices expose supported presets such as 1K, 2K, or 4K. Edit instructs the model to preserve source proportions, so it does not expose Aspect. GPT image models may also expose provider Quality. Exact controls depend on the selected model. The composition-preservation instruction still applies. Nano Banana models accept up to five Composer references in Edit. GPT Image 2 Edit uses only the source and mask, so its reference control is disabled. ### How to review an Edit Read an Edit comparison in three states. Start with the original source. Next, map each region name to its marked outline. Last, compare the result inside those boundaries. Check the unmarked edges separately for drift. A sound result follows every named instruction and aims to leave the surrounding image stable. **Static example:** Review the source first, then the named outlines, then the result. The instruction asks the model to change marked areas and preserve the surrounding camera, framing, and scene. ## Composition and the five fields Canonical URL: https://cadscene.com/help/composition-and-presets/composition-and-the-five-fields Summary: Set the five project-wide fields that shape every render. Last updated: 2026-08-10 Composition is the complete set of five project settings. It is not one field. It contains Style, Scene, Lighting, Materials, and Entourage. The five fields apply across every study in a project. Change them when the project direction changes, not for one isolated message. ### The five fields Each field is free text. Describe intent in plain language and keep it specific; you do not need full sentences. #### Style field Name the overall look: era, movement, regional language, palette, and finish. A Style field is not a saved [Preset](/help/composition-and-presets/presets-style-atlas-and-choosing-a-style). #### Scene field Describe program-neutral environmental and experiential context. This can cover climate, landscape or urban character, broader atmosphere, and the relationship between shelter and its surroundings. Keep it useful across interior and exterior studies. Do not name a room or program. Do not prescribe building geometry or object placement. Camera position, angle, lens, perspective, framing, and viewpoint belong to the current render request or source image, not the reusable Scene field. #### Lighting field Set the light: time of day, direction, shadows, weather, and atmosphere. It can also describe visible artificial light. #### Materials field Call out the surfaces and finishes to feature: texture, color, and reflectivity. Name the materials that should be legible in the result. #### Entourage field Add the life around the subject: people, planting, vehicles, signage, furniture, and activity. State when a space should remain empty. Each render keeps an immutable snapshot of these fields at submit time. Later changes shape future renders only. They do not rewrite past results. #### Edit and save a field Open the corresponding settings tab and edit the text. Changes stay local until you select **Save**. You can also press **Cmd+S** on macOS or **Ctrl+S** on Windows and Linux while the field is focused. Every successful save records a [field version](/help/composition-and-presets/field-versions-and-preset-versions#field-versions). The Save control disappears when the field is clean. ### Generate Composition Generate Composition writes all five fields in one operation. There are three current setup paths for a new, empty project: 1. **Describe your project** turns a short written brief into all five fields. 2. **Start from an image** stores one Project reference image, then reads it. 3. **Browse presets** applies a complete five-field Preset. Full Composition generation from words is available only during new-project setup. After setup, generate one field from words or edit fields directly. There is no post-setup control that generates all five fields from a written brief. If a new project starts from an image, CAD Scene uploads the image, stores it as the Project reference image, generates the five fields, then saves them. If the generated fields are ready but saving fails, **Retry** resumes the save. It does not repeat the completed generation or charge it again. **Static example:** A short project description or one Project reference image can produce example text for Style, Scene, Lighting, Materials, and Entourage. The result is still editable project-wide text. Manual field saves create field versions. A generated Composition is still editable text. Review each field before the first render. Remove anything the project should not inherit. ### Project reference image A Project reference image is one optional image in Project settings. Select **Generate Composition** to read it and overwrite all five fields. You can also generate a Composition from a finished Render. **Use as composition** lets you apply only selected fields. See the [Use as composition guide](/help/rendering-and-results/use-as-composition). After initial setup, you can add or replace this image from the Overview tab. The same **Generate Composition** action is available there. If any field already contains text, CAD Scene asks you to confirm the overwrite. The image itself is not sent to the render provider. Only the five generated text fields shape later renders. Replacing or clearing it does not change past renders. Do not confuse this image with a source image or a per-message composer reference. See [image roles](/help/images-and-references/image-roles-and-source-image-preparation#compare-image-roles). ### Field generation Select **Generate with AI** beside one field. Then choose one input: * **From words** expands rough notes into one field description. * **From images** reads up to five reference images and writes one field. Image-based field generation describes what is visible. It should not invent people, planting, objects, or activity that the images do not show. For Scene, it also does not invent an exterior site when the environmental context is not visible. The new text replaces that field and records its source in field history. The other four fields remain unchanged. Composition generation and field generation use credits. They also have separate rolling daily limits. The request is refunded if generation fails after a debit. See [credits and limits](/help/rendering-and-results/models-quality-credits-and-daily-limits#credits-and-limits) for the current amounts. If credits block generation, the current reference image, field tab, words, and selected files stay available. After a verified purchase, **Continue** returns to the same control without generating. Review the restored inputs, then select the action again. ## Presets, Style Atlas, and choosing a style Canonical URL: https://cadscene.com/help/composition-and-presets/presets-style-atlas-and-choosing-a-style Summary: Compare complete five-field Presets and apply one to a project. Last updated: 2026-07-14 A Preset is a named bundle of all five Composition fields. It carries Style, Scene, Lighting, Materials, and Entourage together. The Style field is only one part of that bundle. Changing the Style field does not apply or create a Preset. Four vertical interior render studies showing white modern, colorful classical, earth-toned, and minimalist Preset directions. Four Presets set four complete directions. Compare material palette, spatial mood, and light before applying one. ### Choose a Preset Open the Overview tab and select **Pick preset**. The Preset library has two groups: * **Built-in presets** are read-only Presets supplied by CAD Scene. * **My presets** are Presets you saved from your own projects. New-project setup opens this library on **Built-in presets**. The Project tab opens it on **My presets** so saved work stays close at hand. The library supports search. Built-in entries also support visual tags. Expand an entry to read its complete five-field brief before applying it. #### Use the Style Atlas The [Style Atlas](/styles) shows all 62 canonical built-in Presets. Every entry uses the same bare scene and camera. This makes the visual language easier to compare. Each built-in Scene paragraph supplies program-neutral environmental context. It stays useful across interior and exterior studies. The current render prompt or source image supplies the specific program, geometry, placement, and camera. Each Atlas page explains its defining cues, suitable project types, and complete Composition. For example: * [Nordic Calm](/styles/nordic-calm) uses restrained materials and diffuse light. * [Brutalist Concrete](/styles/brutalist-concrete) emphasizes mass and raw surfaces. * [Tropical Modern](/styles/tropical-modern) combines open planning and dense planting. * [Organic Modern](/styles/organic-modern) favors soft forms and tactile finishes. **Static comparison:** Every Atlas option renders the same scene and camera. Compare broad mood, material character, and light before adapting the complete five-field Preset to the actual project. Without the interactive explorer, start from three questions: 1. Should the image feel warm, cool, quiet, or dramatic? 2. Which materials must carry the architectural idea? 3. Does the setting need regional or historical specificity? Choose the closest complete direction. Then edit the five fields for the actual site, season, and brief. ### Apply a Preset Applying any Preset overwrites all five current fields. Past renders keep their original settings snapshots. A built-in Preset applies its five fields once. It is read-only and has no Preset version history. Applying it clears any active saved Preset. Existing projects keep their current Scene text until you apply a Preset again. A saved Preset applies its latest version. It also becomes the project's active Preset. The active Preset name identifies where **Save as version** will append the next five-field snapshot. Applying a Preset records the change in each field's history. Review the fields before the next render. A Preset is a starting point, not a lock. #### Save your own Preset Use **More preset actions**, then **Save as preset**. Give the current Composition a name and optional note. CAD Scene creates version 1 from all five current fields. When a saved Preset is active, use **Save as version** to append the current five-field state. Manual field edits do not create a Preset version automatically. Use **Browse versions** to compare or reapply an earlier snapshot. See [field versions and Preset versions](/help/composition-and-presets/field-versions-and-preset-versions) for the difference. ## Field versions and preset versions Canonical URL: https://cadscene.com/help/composition-and-presets/field-versions-and-preset-versions Summary: Understand one-field history, five-field Preset history, and restore behavior. Last updated: 2026-08-10 Field versions and Preset versions record different scopes. They can exist at the same time. ### Field versions A field version records one field in one project. Style, Scene, Lighting, Materials, and Entourage each have a separate timeline. Open a field and select **Versions**. History can identify these sources: * Generated from words * Generated from reference images * Generated from the Project reference image * Applied from a saved Preset * Applied from a built-in Preset * Manual save * Restored from an earlier field version Some entries also retain the source prompt or image previews. This makes the history useful for tracing why the text changed. Every successful manual field Save records a version. Generated values and Preset applications also record their result. #### Current state and empty history The field editor always shows the project's current value. The version timeline shows recorded checkpoints only. **No versions yet** does not mean the current field is lost. It means no checkpoint has been recorded for that field. Select **Save current as version** when the current text differs from the latest checkpoint. #### Go back to a field version Select **Go back** on an earlier entry. CAD Scene copies that text into the current field and appends a new restore entry. The old entries remain unchanged. Future renders use the restored text. Past renders retain the settings snapshot they were created with. ### Preset versions A Preset version is one immutable snapshot of all five fields under a saved Preset. Use **Save as preset** to create a named Preset and version 1. When that Preset is active, use **Save as version** to append the current Composition. Open **Browse versions** to compare any Preset version with the project's current five fields. Applying a Preset version copies all five saved values into the project and keeps that saved Preset active. Applying an earlier Preset version does not erase newer versions. It also does not create another Preset version by itself. Save a new version if you want the restored state recorded as the latest checkpoint. Built-in Presets are read-only. They have no Preset version timeline. ### Use as composition **Use as composition** can append the complete generated Composition to an active saved Preset. This remains a five-field Preset version even when only some generated fields replace the project settings. See the [Use as composition guide](/help/rendering-and-results/use-as-composition) for the full procedure, current cost, wait stages, and retry behavior. ## Image roles and source-image preparation Canonical URL: https://cadscene.com/help/images-and-references/image-roles-and-source-image-preparation Summary: Choose the correct image role and prepare reliable inputs. Last updated: 2026-08-10 CAD Scene uses images in three distinct roles. Choose the role by what the image should affect. ### Compare image roles **Project reference image** * Chosen once in Project settings. * Read only when you select **Generate Composition**. * Writes Style, Scene, Lighting, Materials, and Entourage. * Is not sent with later renders. **Source image** * Chosen in the Enhance or Edit panel. * Is the image being restyled or changed. * Is sent as a direct render input. * One source image is required for Enhance and Edit. **Composer reference image** * Attached to one Composer message as visual context. * Can guide style, material, content, or mood. * Does not replace the Enhance or Edit source image. * Up to five can be attached to one message. **Interactive contract comparison:** The same sample image can represent three different contracts. The selected role changes where it is chosen, who reads it, what it affects, and whether it is sent with a render. **Flow overview:** The Project reference image produces persistent field text. A source image is the image Enhance or Edit transforms. A Composer reference travels with one compatible send as visual guidance. ### Project reference image Use a Project reference image when one image should seed the five text fields. It works well when the intended materials, light, setting, and atmosphere are clearly visible. After generation, review the written fields. Those fields become the persistent project settings. The image does not remain in the render input. Use a Composer reference instead when the image should guide one send. Use a source image when the image itself must be restyled or edited. ### Source image Enhance and Edit each require one source image. In Enhance, the source is usually a screenshot from a 3D or CAD application. CAD Scene asks the model to preserve its geometry, camera, perspective, composition, framing, proportions, and canvas dimensions. In Edit, the source is usually a finished render. CAD Scene sends it with a mask. The model is asked to change only the marked regions and preserve the rest. All marked areas share one union mask. Region bounds can overlap, but each painted pixel appears in the mask once. Region names and bounds remain separate metadata. They are not separate uploaded masks. One Edit send uses that mask, the source, and one prompt that references every region name. It makes one image request, not one request per region. Source selection lives in the right panel. Composer references remain in the Composer card. Keeping these controls separate prevents a reference from being mistaken for the image being changed. ### Composer reference images Composer references are available in Create and Enhance with every selectable model. In Edit, the Nano Banana models accept Composer references. GPT Image 2 does not. Its Edit request uses only the source and mask. The attach control is disabled for that combination. References are stored per mode. Switching modes keeps each mode's draft and reference list. A successful send clears the active mode's prompt and references unless **Keep prompt** is on. You can upload references or attach an existing CAD Scene render. Duplicate images are skipped. The per-message limit is five. In Create, a Composer reference supplies view intent only when the current prompt explicitly asks to use that reference's view. Attaching a reference by itself can guide visible style or content, but Create still asks for a written view. ### Prepare Composition images #### Works well * One clear visual direction. * Materials shown at a useful scale. * Lighting and atmosphere visible across the frame. * Context and entourage visible when they should enter the written fields. * A crop that contains only relevant design evidence. #### Prepare first * Crop out browser chrome, tool palettes, cursors, guides, and annotations. * Remove title blocks, watermarks, and overlaid labels. * Choose a frame where important materials are not hidden. * Avoid combining unrelated visual directions in one image. * Crop empty borders that weaken the useful image area. Composition generation is grounded in visible content. If no people, planting, vehicles, or objects are shown, the generated fields should not invent them. The camera is excluded from the generated brief. ### Prepare Enhance images #### Works well * A clean viewport capture from the final camera. * Complete, readable geometry. * Clear edges around walls, openings, roofs, and major site elements. * Enough pixel detail to read surfaces and boundaries. * The exact framing and aspect ratio you want to keep. #### Prepare first * Hide grids, axes, selection outlines, guides, and transform controls. * Close menus, dialogs, tooltips, and floating palettes over the scene. * Remove dimensions, notes, and viewport labels. * Fix clipped geometry and unwanted objects before capture. * Crop the viewport to the intended final frame. The uploaded image is resized only when its long edge exceeds 2048 pixels. It is never enlarged during upload. Start with a source that remains readable at that size. GPT Image 2 accepts source aspect ratios up to 3:1. Crop a more extreme panorama or tall strip before using that model. Other selectable models use their own output handling. ### Prepare Edit images #### Works well * A finished render with clear detail in the target area. * A source whose camera and framing are already correct. * Separate, tightly marked regions for separate changes. * Overlapping regions only when their shared-area instructions can coexist. * Automatic region names kept or edited for clarity. * One prompt that mentions every unique region name. #### Prepare first * Remove overlays that cover pixels you need to edit. * Use a larger source when the target detail is only a few blurred pixels. * Keep each mark on the image. * Split unrelated changes into separate named regions. * Tighten overlapping marks or make their shared-area instructions compatible. * Keep region names unquoted. Use straight double quotes only for exact new readable scene text. * Re-upload the source if CAD Scene reports that it cannot read the file. Edit sends one union mask that matches the source canvas. Generative models can follow mask boundaries loosely, especially where named regions share pixels. The output size remains subject to the selected model's constraints. GPT Image 2 can scale the source and round each edge to its nearest valid dimensions. #### File formats Uploads are decoded in your browser, resized when needed, and normally encoded as WebP. PNG and JPEG are reliable inputs. HEIC and HEIF decoding depends on the browser and operating system. If CAD Scene reports that HEIC is unsupported, convert the file to JPEG or PNG first. Corrupt files and files whose contents do not match their declared format are rejected. Re-export or re-upload them instead of retrying the same bytes. ## Models, quality, credits, and daily limits Canonical URL: https://cadscene.com/help/rendering-and-results/models-quality-credits-and-daily-limits Summary: Choose compatible render settings and understand every current charge. Last updated: 2026-08-10 Every render has a model, model-specific output settings, and an image count. CAD Scene shows the total credit cost before you send. ### Choose a model A project has a default model. New Composer sends start with that model. Changing the model for one send does not change the project default. Changing the model resets its Quality, Resolution, and Aspect to that model's defaults. Nano Banana 2 is the app default for new or unset selections. Its native defaults are 2K Resolution and a 3:2 Create Aspect. Existing app-wide and project defaults keep their saved model. Four models are currently available. #### Nano Banana 2 * Supports Create, Enhance, and Edit. * Supports Composer references in all three modes. * Offers 512, 1K, 2K, and 4K resolution. * Offers the widest Create aspect-ratio range. #### Nano Banana Pro * Supports Create, Enhance, and Edit. * Supports Composer references in all three modes. * Offers 1K, 2K, and 4K resolution. * Offers the conventional Create aspect-ratio range. #### Nano Banana * Supports Create, Enhance, and Edit. * Supports Composer references in all three modes. * Uses a fixed 1K resolution. * Offers the conventional Create aspect-ratio range. #### GPT Image 2 * Supports Create, Enhance, and Edit. * Supports Composer references in Create and Enhance. * Does not accept Composer references in Edit. * Offers Low, Medium, and High provider quality. * Offers 1K, 2K, and 4K resolution. Model capability is a compatibility choice. CAD Scene does not promise that one model is always faster or visually better. Controls and limits follow both the selected model and the active mode. In Edit, the model capability sets the maximum number of named regions. Every current selectable model supports eight. CAD Scene reads that value from the model registry, so a future lower-cap model will update the canvas, Send requirements, Render again, and Create variations without a separate hardcoded limit. Changing to a lower-cap model would preserve existing regions and state the exact number to remove before Send. You could remove regions or choose a compatible model. Render again and Create variations would mark an incompatible model unavailable instead of trimming the stored mask metadata. ### Quality and cost The model list is always visible in the render settings popover. Fine settings sit under a collapsed **Settings** disclosure. Open it to review the current selection. CAD Scene hides a control when it has only one possible value. Nano Banana's fixed 1K Resolution is recorded without showing a one-choice control. Gemini models expose Resolution, not Quality. Their cost can change with Resolution. GPT Image 2 exposes both provider Quality and Resolution. Either setting can change its cost. Selectable Resolution defaults to 2K. GPT Image 2 Quality defaults to Medium. GPT Image 2 2K and 4K outputs are experimental. Their provider support may change. #### Create aspect Create shows each supported aspect ratio directly. There are no orientation groups. The default is 3:2 when that ratio is available. Ratio availability changes with the model. A ratio tooltip shows the expected requested dimensions for the current Resolution. The final Output size can differ from that request. #### Enhance and Edit size Enhance and Edit do not show Aspect. They preserve the source proportions while applying the selected Resolution. OpenAI may round the requested dimensions to a valid provider size. Generation details records the Requested size and measured Output size separately. Changing models resets the output settings to that model's defaults. Review the Settings disclosure after every model change. The Composer is the source for the exact current cost. It calculates the per-image rate from the selected model, Quality, and Resolution. Image count multiplies that rate. The preview updates before submit, including inside Render again and Create variations. The popover header shows a compact total such as `5cr`. This means 5 credits for the current image count. The resting Composer bar does not show a cost. The free 4K upscale is a separate Lanczos resize. It does not create another provider generation or change the original render settings. ### Project defaults The **Default model** in app-wide Settings applies only when you create a new project. The new project stores that model with its current native defaults. Each project's **Default render settings** then control new Composer sessions in that project. They store the model, Quality when supported, Resolution, and Create Aspect. Composer changes last for the current session. They do not rewrite project defaults. An unavailable saved model switches to the product default and shows a notice. ### Credits and limits Render credits are charged when the send is submitted. One send with multiple images creates one charge equal to the per-image rate multiplied by the count. Generate Composition and Generate one field have fixed costs. Each action shows its current cost before confirmation. Lanczos 4K upscale is free. Create variations, Render again, retries, and Modify, Relight, or Effects operations submit new Renders. They use the normal per-image rate for the model and settings resolved by that action. Credits and rolling daily limits are separate checks. Having enough credits does not bypass a limit. Current rolling 24-hour limits are: * 1,000 render submissions. * 1,000 Composition generation requests. * 1,000 field generation requests. The render limit counts submissions, not output tiles. A single send with several parallel images uses one render-submission quota entry. It still charges for every image. When a limit is reached, CAD Scene reports the estimated reset time. Wait for the rolling window or contact support for a higher cap. ### Refunds Failed and successfully cancelled render jobs refund their charged credits. Each output image has its own job and refund record. A failed tile does not cancel or refund its successful siblings. Composition and field generation debit before the provider call. A provider or response failure refunds that operation. Retry, Retry with model, Render again, Create variations, Modify, Relight, and Effects are new submissions. They create a new charge. A refund for the failed original does not make the replacement free. An insufficient-credit rejection does not create renders or jobs. The transaction is rolled back. When credits are the only remaining blocker, CAD Scene keeps the blocked control and opens the available plans and top-ups. A completed return is verified before confirmation appears. Stripe must report it as `paid` or `no_payment_required`. **Continue** returns to the original control. It does not submit the action automatically. ## Parallel Variants versus Variations Canonical URL: https://cadscene.com/help/rendering-and-results/parallel-variants-versus-variations Summary: Compare multiple images from one send with a later Variations action. Last updated: 2026-08-10 Variants and Variations both create multiple possible results. They happen at different times. ### Composer Variants Set the Composer count from 1 to 8 before sending. One message then creates that many parallel Variants. Each Variant has its own: * Render * Render job * Progress stream * Output tile * Per-image credit charge The images share the message's prompt, mode, model, render settings, source, references, and Composition snapshot. Provider sampling can still produce different results. The Feed keeps all Variants in one card. One failed or cancelled tile does not stop its siblings. Use the stop control on one active tile to cancel that job. **Cancel all** appears when more than one job in the card remains active. Cancellation is accepted while a job is queued or generating. A job already uploading finishes instead. The total cost is the per-image rate multiplied by the Variant count. ### Feed Variations Open a finished Render's actions and select **Create variations**. Then choose from 1 to 8 new images. You can also change the model and its supported output settings. Variations starts with the original: * Prompt * Mode * Source and mask, when present * Composer reference images The original model and render settings stay selected when both are still valid. If the settings are no longer valid, Variations uses that model's current defaults. If the original model has retired, Variations selects the current default model and its defaults. Before generating, you can choose the model, its available settings, and a count from 1 to 8. Each Variation is a new render charged at the selected model and settings. Missing original attachments disable the action. For an ordinary finished Render, the new submission snapshots the project's current Composition. It does not restore that Render's five-field snapshot. For a **Modify**, **Relight**, or **Effects** result, **Create variations** routes through operation replay. It resolves the original source Render and reuses that source Render's immutable Composition snapshot instead of current project fields. See [Modify, Relight, and Effects](/help/rendering-and-results/modify-relight-and-effects). ### Variants and Variations compared Use **Composer Variants** when you know before sending that you want several parallel takes. They use the model and settings currently selected in Composer. Use **Create variations** after reviewing a finished Render. The resulting Variations repeat its original inputs. The popover preserves a valid original model and settings, applies current defaults when needed, and lets you change the model, settings, and count. This interactive calculator is a **Create example**. Its displayed aspect ratio applies only to Create. Enhance and Edit take framing from the source. The calculator uses the same capability, default-setting, and pricing helpers as render submission. It shows the current settings summary, per-image cost, total cost, and one independent job for every selected image. It does not submit a render. **Static comparison:** Composer Variants split one Send into the chosen number of independent jobs. Variations start later from one finished result and create a new set of jobs with the selection shown in the Create variations popover. Both charge once per new image. Both choices create a new Feed card with independent jobs. Neither duplicates an existing output file. #### Render again and Retry are different **Render again** creates one new image. It preserves the original prompt, mode, and available attachments. You choose the model and its model-specific output settings. The project's current Composition is snapshotted for an ordinary new Render. For a **Modify**, **Relight**, or **Effects** result, **Render again** routes through operation replay. It resolves the original source Render and reuses that source Render's immutable Composition snapshot instead of current project fields. **Retry** appears on a failed tile. It preserves the original prompt, attachments, model, and settings when that selection is still valid. Invalid settings use that model's current defaults. A retired model falls back to the current default model and its defaults. **Retry with model** is the failed-tile configured retry. It lets you choose the model and its supported output settings before the new submission. All three are charged new render submissions. The failed original is refunded separately. ## Use as composition Canonical URL: https://cadscene.com/help/rendering-and-results/use-as-composition Summary: Generate a new five-field Composition from a finished Render and apply selected fields. Last updated: 2026-08-10 **Use as composition** reads one finished Render and generates a new Composition. You choose which generated fields replace the project settings. ### Where to find the action For a Feed or Gallery tile, open **Image actions**. Then select **Use as composition**. In the Render lightbox, select the icon-only **More actions** ellipsis at any width. Then select **Use as composition**. ### Apply a Render as the Composition 1. Open the actions for a finished Render. 2. Select **Use as composition**. 3. Keep checked only the fields you want to replace. 4. Optionally save the generated Composition as a new Preset version. 5. Review the current cost, then select **Use as composition**. The dialog starts with Style, Scene, Lighting, Materials, and Entourage checked. Clear a field to keep its current project value. AI always reads the finished Render image and generates all five fields. Only the checked fields overwrite the project's current Composition. ### Cost and Preset versions The dialog shows the current credit cost. **Use as composition** uses the same dynamic rate as **Generate Composition** from a Project reference image. If the project has an active saved Preset, the dialog offers a second option. It saves the complete generated Composition as a new Preset version. This Preset version always contains all five generated fields. It remains complete even when you apply only some fields to the project. ### What happens while you wait Keep the dialog open during both stages. The first stage is **Reading the render**. AI reads the image and generates the five fields. This can take a little while. The second stage is **Updating the project Composition**. CAD Scene saves the checked fields and the optional complete Preset version. The dialog shows both stages in order. A normal wait during image reading does not mean the action has stalled. ### Checkout and retry recovery If credits block generation, the checkout flow keeps the Render, checked fields, and Preset-version choice. After payment is verified, **Continue** reopens the same dialog. It does not start generation automatically. Review the restored choices, then select **Use as composition** again. If generation succeeds but the project update fails, leave the dialog open and retry. CAD Scene reuses the generated Composition. The retry does not create a second generation charge. Closing the dialog clears that generated retry state. Reopen it to start a new generation. ### Past Renders stay unchanged The action changes project settings for future work. It does not change the source Render or any earlier Render. Each past Render keeps its stored Composition snapshot and generation details. ## Modify, Relight, and Effects Canonical URL: https://cadscene.com/help/rendering-and-results/modify-relight-and-effects Summary: Apply one focused operation to a finished Render with its original context. Last updated: 2026-08-10 An **image operation** applies one focused preset to a finished Render. Selecting a preset submits one new Enhance Render immediately in the same study. The operation uses the source Render's image, model, supported native settings, and immutable Composition snapshot. It does not silently switch to the project's current settings. If the source model or settings are no longer available, CAD Scene uses the normal action fallback to an available selection. The charge is the normal per-image rate for that resolved model and settings. There is no flat operation price. A failed operation refunds its charge through the normal Render job path. Sample previews show the operation on a neutral scene, not your render. They teach the intended treatment and do not predict an exact result. ### Modify Use Modify for a bounded framing, viewpoint, scene-content, sky, perspective, material, or realism change. Camera changes such as a higher viewpoint are inferred by the image model. They can rebuild parts of the scene and cannot guarantee exact geometry. * **Zoom in:** Move closer to the subject while keeping the same view direction. * **Zoom out:** Reveal more context around the scene without redesigning it. * **View from above:** Rebuild the scene from a higher, downward-looking view. * **Add people:** Add a few naturally scaled people without hiding the architecture. * **Add decorations:** Add restrained decor that fits the existing design. * **Expand image:** Extend the scene beyond every edge while keeping its aspect ratio. * **Cleanup:** Remove visual defects and clutter without redesigning the scene. * **Add greenery:** Add restrained, climate-appropriate planting in plausible locations. * **Refine materials:** Improve texture, roughness, reflections, and material realism. * **Add vehicles:** Add one or two context-appropriate vehicles in plausible positions. * **Remove people:** Remove people and reconstruct the surfaces behind them. * **Improve sky:** Use a natural sky that matches the scene’s existing light. * **Correct perspective:** Straighten architectural verticals while retaining the original view. * **View at eye level:** Rebuild the scene from a natural standing-height viewpoint. * **Make photoreal:** Convert the image to a photographic render without redesigning it. * **Remove vehicles:** Remove vehicles and reconstruct roads, paving, and landscape. Modify preserves the source's visual direction by default. **Make photoreal** is the explicit exception: it converts the image to a photographic render while asking the model not to redesign it. ### Relight Use Relight when the design and composition should remain while illumination and related atmosphere change. * **Clear morning:** Use cool early daylight with crisp shadows and clear atmosphere. * **Soft overcast:** Use even diffuse daylight that reveals materials without harsh contrast. * **Bright midday:** Use high neutral sun with short shadows and clean contrast. * **Golden hour:** Use warm low-angle sun with longer, softer shadows. * **Blue hour:** Balance cool ambient twilight with existing warm lights. * **Rainy day:** Use diffuse cool daylight, light rain haze, and damp reflections. * **Misty dawn:** Use pale dawn light with shallow mist and clear foreground detail. * **Storm clearing:** Add a restrained cloud break with one plausible shaft of sun. * **Night illumination:** Use existing windows and fixtures for a balanced night exposure. * **North light:** Use soft cool daylight with gentle interior tonal falloff. * **Window sun:** Cast directional sunlight through existing openings with aligned shadows. * **Warm practicals:** Use evening light from existing warm lamps and fixtures. * **Sunset afterglow:** Add soft residual sunset color after direct sun has passed. * **Moonlit night:** Use cool natural moonlight with readable shadows and restrained contrast. * **Dramatic side light:** Model the architecture with strong side light and retained detail. * **Backlit glow:** Add controlled backlight and rim light around the existing silhouette. * **Skylight wash:** Use broad top light from existing skylights or overhead openings. * **Gallery spotlights:** Add focused pools from existing spotlights with clean falloff. * **Winter sun:** Use low cool sunlight with long, crisp seasonal shadows. * **Desert sun:** Use dry bright sun with strong form and restrained warm bounce. ### Effects Use Effects for a restrained physical, optical, weather, movement, or photographic treatment. * **Atmospheric mist:** Add thin mist for depth while keeping the architecture crisp. * **Lens flare:** Add a subtle flare aligned with the existing light direction. * **After rain:** Add wet surfaces and restrained reflections after rain clears. * **Soft sunbeams:** Add faint volumetric rays aligned with existing light and openings. * **Dappled shadows:** Add soft leaf shadows without obscuring architectural details. * **Snow flurry:** Add sparse fine snow with minimal accumulation and clear façades. * **Light trails:** Add thin long-exposure vehicle trails along existing roads. * **Optical bloom:** Add restrained glow around highlights while edges stay sharp. * **Shallow depth of field:** Add gentle focus falloff while architecture remains dominant. * **Fine rain:** Add light visible rainfall without flooding or a heavy storm. * **Dust motes:** Add subtle illuminated particles in plausible interior light. * **Long-exposure clouds:** Add soft directional cloud movement above stable architecture. * **Starburst lights:** Add controlled diffraction stars around existing point lights. * **Foreground bokeh:** Add restrained out-of-focus foreground highlights around the scene. * **Fine film grain:** Add subtle photographic grain without reducing material clarity. * **Soft vignette:** Add gentle edge darkening while keeping the building fully legible. * **Water caustics:** Add subtle reflected patterns where existing water supports them. * **Cloud reflections:** Add natural sky reflections on existing glazing only. * **Falling leaves:** Add sparse seasonal leaves with plausible scale, depth, and motion. * **Wind movement:** Add gentle motion to existing foliage, fabric, or light elements. ### Existing scene conditions Context-specific presets use what the scene already supports. They do not invent water, lights, roads, foliage, glazing, openings, or fabric only to make an effect visible. If a required condition is absent, the treatment may be subtle or have no useful effect. ### History, replay, and recovery Operation results keep the **Enhance** badge. Their Feed prompt starts with `Category · Preset`, followed by a short public summary. Public Help and Feed text never expose the longer provider instruction. **Render again** and **Create variations** preserve valid operation identity and replay the preset while letting you choose supported model settings and, for variations, a count. They still create newly charged Render jobs. If credits block an operation, verified checkout **Continue** restores the same source, category, and preset without submitting it. Select the preset again when ready. A missing source image, retired preset, invalid saved metadata, or unavailable project stops safely instead of turning into an ordinary Enhance. Correct the source or choose a current finished Render, then try again. ## Render actions, retries, history, cancellation, and refunds Canonical URL: https://cadscene.com/help/rendering-and-results/render-actions-and-history Summary: Reuse finished Renders, replay work, manage history, and understand charges. Last updated: 2026-08-11 Every generated image is a Render. Feed and Gallery organize the same project results for different tasks, and their finished-image actions use the same labels, descriptions, order, and availability. ### Feed and Gallery The **Feed** follows one study. Each message appears as one card with its Variant tiles. Active, failed, cancelled, and finished tiles stay grouped with the message that created them. Open any finished Feed Render to review every finished image already loaded in the Feed. Arrow buttons, Arrow keys, swipes, and thumbnails follow visible Feed order. The strip shows global position, such as **7 / 24**. Cmd/Ctrl+Arrow jumps to the first image in the next or previous loaded card. Navigation stops at the first and last image and does not load older messages. The **Gallery** collects finished Renders from every study in the project. You can filter by study, mode, model, and quality, sort the loaded results, and open any image in its lightbox. The Gallery Quality filter is a compatibility filter across old and new rows; it does not mean Gemini exposes a native Quality setting. Select the model and settings summary on a Feed card to open **Generation details**. This is a Feed-card affordance, not an action-menu item. It can show: * Source and Composer reference images * Model, output settings, image count, and total credits * Slash-command changes applied by the message * The five-field Composition snapshot used for the Render That snapshot explains an older Render even after project settings change. The Feed card also shows input images as small thumbnails. Open one from the card rail or Generation details. Its viewer offers **Download**, **Edit**, **Enhance**, and **Attach**. Edit and Enhance prepare the Composer without sending. Attach adds the image as Composer reference context and keeps the viewer open. **Requested size** is the provider target. **Output size** is the measured finished file. Native Quality, Resolution, Aspect, and Requested size appear only when stored versioned settings validate for that model and mode. Older rows may omit them while retaining safe facts such as Model, Output size, Images, and Cost. #### Render clarification history A completed render clarification appears in a separate thin row immediately before its Render card. Its **read more** view contains the initial prompt and ordered questions and answers. The final submitted prompt stays on the Render card. Clear, skipped, failed, and abandoned checks create no clarification history. Render again, Create variations, Retry, and image operations do not copy an older clarification into the new request. Deleting every Render tile in the message also removes its clarification row from the Feed. ### Finished Render actions The toolbar and tile menu use this order: 1. **Download** is a split control. Select its main action to save the original. Open the chevron for **Download 4K**, which creates or reuses a free Lanczos upscale and downloads it. 2. **Edit**, **Enhance**, and **Attach** prepare the Composer. Edit and Enhance set this Render as the source. Attach adds it as reference context. 3. **Render again** and **Create variations** open model and supported settings choices before a new submission. Create variations also lets you choose a count. 4. **Modify**, **Relight**, and **Effects** open preset menus. Selecting a preset immediately submits one Enhance Render. 5. The ellipsis contains **Use as composition** and **Delete**. Tile menus keep root rows to an icon and label. Hover or focus an action to read its short explanation and open the relevant Help guide. Modify, Relight, and Effects keep that guidance inside their opened preset menus. Edit uses its orchid mode tint, while Enhance uses ember. Edit and Enhance do not charge when selected. A charge starts only if you send the prepared Composer draft. Attach does not submit a Render. Image operations use the source Render's model, supported native settings, image, and immutable Composition snapshot. They do not use current project settings. They charge the normal per-image rate for that resolved selection, and failures refund. Results retain the **Enhance** badge and show `Category · Preset` with a short public summary in the Feed. The [Modify, Relight, and Effects reference](/help/rendering-and-results/modify-relight-and-effects) lists every preset, explains illustrative previews and scene requirements, and covers operation replay. If credits block an operation, verified checkout **Continue** restores its source, category, and preset without submitting. Select the preset again when ready. The same no-auto-submit rule applies to restored Render again and Create variations controls. ### Use as composition Select **Use as composition** to generate a new five-field Composition from the finished Render. You choose which fields replace project settings. The dedicated [Use as composition guide](/help/rendering-and-results/use-as-composition) explains field selection, cost, Preset versions, wait stages, and recovery. ### Delete, Trash, and Restore **Delete** always opens a confirmation. Confirming moves the Render to **Gallery Trash**; it does not hard-delete the file. Cancellation or a failed request keeps the Render and focus. A lightbox closes only after deletion succeeds. Open the Gallery Trash filter and select **Restore** to return the Render to the Gallery. ### Retry and replay A transient provider error is retried once by the worker before a tile becomes a final failure. Content-policy, invalid-image, and invalid-size errors are not repeated automatically. After a final failure: * **Retry** keeps the failed job's prompt, mode, attachments, model, and settings when that selection remains valid. Invalid settings use that model's current defaults. A retired model falls back to the current default and its defaults. * **Retry with model** keeps the prompt, mode, and attachments while you choose a model and supported native settings. Render again and Create variations keep the original prompt, mode, and available attachments. For an ordinary Render, their new submission snapshots the project's current Composition. For an image-operation Render, they also preserve valid operation identity and replay the server-owned preset instruction. Create offers Aspect. Enhance and Edit preserve source proportions and do not offer Aspect. If an original source, mask, or reference file is unavailable, replay is disabled. Pick or upload a current image instead. ### Cancellation and refunds Credits are charged when a Render message is submitted. Each output tile has its own job and charged amount. You can stop one job while it is queued or generating. **Cancel all** requests cancellation for every active sibling in the card. Cancellation can be too late: once a job is uploading, CAD Scene lets it reach a final state to avoid an incomplete stored result. An accepted cancellation refunds that job. A failed job also refunds its charged credits. Refunds are idempotent, so overlapping worker and cancellation cleanup cannot refund twice. Successful siblings remain charged; failed or successfully cancelled siblings are refunded independently. ## How to use 3D models in your AI renders Canonical URL: https://cadscene.com/help/tutorials/use-3d-models-in-ai-renders Summary: Turn a composed 3D model view into a Viewer capture, then use it as the source for Enhance. Last updated: 2026-08-11 ### How the capture becomes an AI render The viewer does not send your 3D file directly to AI. It turns the chosen camera and visible geometry into a 2D PNG Viewer capture. Enhance uses that Viewer capture as its explicit source image. It aims to keep the camera, framing, and visible geometry while applying your guidance. ### Use a 3D model in an AI render 1. Open the Project, then choose the **3D models** panel. 2. Add a supported package, then open its tile when conversion is ready. 3. Compose the camera, projection, lens, visibility, and **Presentation** appearance in Viewer. 4. Choose **Capture**, then frame and position the crop for the required output. 5. Name the Viewer capture, then choose **Save capture** to create the PNG. 6. Choose **Enhance this capture**, add guidance, review Render settings, then choose **Send**. Expected results: * The saved Viewer capture remains available under **Captures** and **This project**. * Enhance opens with the PNG attached as its explicit source image. * The finished render follows the captured camera, framing, and visible geometry. ### Find the 3D models panel and upload Open your Project settings rail, then choose **3D models**. Add one supported package with **Add model**, **Folder**, drag and drop, or a ZIP. Conversion continues if you leave the Project. Open the ready tile after its preview appears. A processing tile shows its current conversion stage. If conversion fails, use the tile **Actions** menu. Choose **Retry conversion** when the retained source remains available. Choose **Replace file** for a corrected export. ### Compose the camera in Viewer Open the model tile, then choose **Viewer**. Use Camera to set projection, lens, and framing. Use Layers to hide or isolate geometry. Keep **Presentation** when you want the default clay appearance. Saved Views let you return to a useful camera before capture. * Use **Reset view** when the complete model sits outside the frame. * Correct model setup when units, up axis, or Front orientation are wrong. * Return to Layers when unwanted geometry remains visible. ### Capture and save the shot Choose **Capture**, then expand **Capture controls**. Select a ratio such as 4:3, then move or resize the crop over the intended frame. Choose the output size and background. Add a stable capture name, then choose **Save capture**. CAD Scene saves the framed result as a PNG. * Reposition the crop when important geometry falls outside the safe frame. * Wait for the model to finish loading if capture actions remain unavailable. * Use **Stay in capture mode** to adjust the same crop after saving. ### Open the capture in Enhance After saving, choose **Enhance this capture**. The handoff closes Viewer, attaches the PNG as the Enhance source, and focuses the prompt. The handoff does not send a render. Add your guidance, review Render settings, then choose **Send** when the source and brief are correct. * Reopen the Viewer capture from **Captures** if the wrong image was selected. * Choose **Stay in capture mode** when framing needs another pass. * Replace the source in Enhance before sending if a different capture fits better. ### Formats, setup, and recovery The [3D models and viewer reference](/help/projects-and-studies/3d-models-and-viewer) owns details that change by model format: * [Check supported files and package requirements](/help/projects-and-studies/3d-models-and-viewer#supported-files). * [Correct units, up axis, and Front orientation](/help/projects-and-studies/3d-models-and-viewer#correct-model-setup). * [Recover a failed model conversion](/help/projects-and-studies/3d-models-and-viewer#recover-a-conversion). That reference owns the format table, setup corrections, and conversion recovery. This tutorial owns the capture-to-Enhance procedure. ## Composer, slash commands, and keyboard shortcuts Canonical URL: https://cadscene.com/help/reference-and-troubleshooting/composer-slash-commands-and-keyboard-shortcuts Summary: Use Composer controls, project-setting commands, and workspace shortcuts. Last updated: 2026-08-08 Composer sends Create, Enhance, and Edit messages. The active mode controls which inputs are required. The control row contains the mode, model and output settings, image count, Keep prompt, and Send controls. Composer references attach inside the Composer card. The source image for Enhance or Edit lives in the right panel. Each mode keeps its own prompt and Composer references. Switching modes does not clear the other drafts. Create requires a prompt. Enhance can send without one. Edit requires one prompt after you mark a region. The Edit prompt must mention every unique region name outside quotes. Region names are references, not requested scene text. After a successful send with **Keep prompt** off: * The active mode's prompt and Composer references clear. * An Enhance source clears. * An Edit source stays selected, but its mask and regions clear. * Drafts in the other modes stay unchanged. Turn **Keep prompt** on to retain the active prompt, references, Enhance source, or Edit source, mask, and regions after a successful send. This preference is stored in the current browser. If a render brief has a hard ambiguity, Composer temporarily shows one clarification question instead of its normal controls. Choose a suggested answer immediately, or write a custom reply and select **Continue**. Select **Back** to revise the previous answer. Press **Escape** to discard the clarification and restore the original draft. **Skip and Send Now** renders the original prompt and keeps no clarification. Its tooltip says: “Skip these questions and render your original prompt. No clarification will be saved.” Provider or network failure follows the same original-prompt path silently. A mode conflict is a confirmation instead of a question. Composer shows **Review before sending**. Select **Back to composer** to change modes, or select **Continue with Create**, **Continue with Enhance**, or **Continue with Edit** to send the original prompt under the selected mode's rules. ### Slash commands Slash commands can update project settings without opening a settings tab. Type `/` in the prompt to open the current command list. Use lowercase commands at the start of the message. * `/style` sets the Style field. * `/scene` sets the Scene field. * `/lighting` sets the Lighting field. * `/materials` sets the Materials field. * `/entourage` sets the Entourage field. * `/shortcuts` opens Composer help. * `/help` opens the Help Center in a new tab. Add the new value after a field command: ```text /lighting soft overcast daylight with long diffuse shadows /materials pale oak, lime plaster, dark bronze frames Keep the camera at eye level and the room quiet. ``` Leading field commands update the project before the render snapshot is taken. The remaining text becomes the render prompt. You can also send field commands without a render prompt. CAD Scene updates the fields and adds an Undo event to the Feed. No render is generated or charged. Commands are read only from the leading lines. The first normal or unknown line starts the prompt. If the same field appears more than once, the last value wins. `/shortcuts` and `/help` are UI-only commands. When either appears among the leading command lines, CAD Scene opens its destination and removes that command line from the active draft. It does not submit a render. Any remaining prompt text, field commands, and Composer references stay in place for the next send. ### Keyboard shortcuts Use **Cmd** on macOS. Use **Ctrl** on Windows and Linux. Press **Cmd/Ctrl+?** or use `/shortcuts` to open Composer help. The dialog is the authoritative reference for the Composer, workspace layout, mode, and slash commands it lists. **Cmd/Ctrl+S** is field-editor behavior and remains documented below. #### Composer * **Cmd/Ctrl+Enter** sends the active draft. * **Shift+Enter** inserts a newline. * In a custom clarification reply, **Cmd/Ctrl+Enter** selects **Continue**. * In clarification, **Escape** returns to the original Composer draft. #### Workspace layout * **Cmd/Ctrl+K** focuses the Composer prompt. * **Cmd/Ctrl+B** toggles the studies rail. * **Cmd/Ctrl+.** toggles the settings rail. * **Cmd/Ctrl+?** opens Composer help. #### Modes * **Cmd/Ctrl+1** switches to Create. * **Cmd/Ctrl+2** switches to Enhance. * **Cmd/Ctrl+3** switches to Edit. #### Project fields * **Cmd/Ctrl+S** saves the focused Composition field. Global layout and mode shortcuts are suppressed while you type in an input. Composer send and newline shortcuts still work in the prompt. ### Composer reference images Select the attachment control to add visual context. Choose a render or upload from the picker, upload a new image, or attach the last render. Composer references are separate from the Enhance or Edit source. They are also separate from the Project reference image. Each mode keeps its own reference list. The list skips duplicates and accepts up to five images. Reference support depends on model and mode. Every selectable model supports references in Create and Enhance. In Edit, GPT Image 2 uses only the source and mask. Switch to a Nano Banana model or remove the references. See [image roles](/help/images-and-references/image-roles-and-source-image-preparation#compare-image-roles) for the complete comparison. ## Troubleshooting and recovery Canonical URL: https://cadscene.com/help/reference-and-troubleshooting/troubleshooting-and-recovery Summary: Resolve input, credit, limit, image, provider, and cancellation problems. Last updated: 2026-08-10 CAD Scene can catch requirements before submission. A collapsed Edit panel defers source, region, and name checks until it is opened. User-fixable server failures after Send populate the same requirements dialog. The draft stays available so you can fix every listed item and send again. Input requirements and the credit check remain blocking and run before the brief check. If the brief-check provider, timeout, schema, or network request fails, CAD Scene silently sends the original prompt and stores no clarification. For a clarification question, **Skip and Send Now** follows the same original-prompt path. For a mode conflict, **Continue with Create**, **Continue with Enhance**, or **Continue with Edit** uses that path under the selected mode's rules. Neither action can bypass a missing source, invalid Edit regions or names, unsupported settings, ownership, credits, or quota. ### Edit requirements #### Pick an image to edit Open the Edit panel and choose a source image. A Composer reference does not count as the source. If a retry says the source is no longer available, the stored original was removed or cannot be signed. Choose or upload a current source. #### Mark a region Paint at least one region on the source. Keep every mark on the image. One Edit can contain up to eight regions with every current model. If a region sits outside the image, move or repaint it. The mask must overlap the source. #### The wrong regions merged Select **Undo** once. Redraw the mark, then choose **Create new region** when the overlap choice opens. This keeps the named regions separate even when their bounds overlap. If nearby strokes merge without asking, clear **Group nearby strokes automatically** in the footer. The next ambiguous mark opens the choice again. #### The selected model supports fewer regions CAD Scene preserves every region when a model switch lowers the available cap. The footer and Send requirement state the exact number to remove. Delete or undo regions, or choose a model whose Edit capability supports the current count. #### Overlapping instructions conflict Overlapping regions share editable pixels. Tighten one or both marks when the requested changes cannot coexist. Otherwise rewrite the instructions so every named change can apply in the shared area. #### Add an Edit prompt The Edit prompt cannot be empty. Write one instruction that mentions every region name and states what changes there. ```text In Region A, replace the paving with dark basalt. In Region B, add a slim black steel frame. ``` #### Name every region Every marked region needs a non-empty, unique name. CAD Scene fills `Region A`, `Region B`, and the later names automatically. You can edit them. If two names still match after case, spacing, and character-width normalization, rename one. For example, `Region A` and `ｒｅｇｉｏｎ　Ａ` are duplicates. Overlapping names need separate prompt occurrences. If the names are `Wall` and `North Wall`, the phrase `North Wall` cannot satisfy both. Write both names: `Replace North Wall with oak. Keep Wall unchanged.` #### Reference every region name Each unique name needs its own whole-phrase occurrence outside quoted text. If `Region A` appears only inside `"Region A"`, remove the quotes around the reference. Then describe the area's change. If one name is missing, use the inline error or **Update the prompt**. Add the exact missing name as a separate reference. Do not rename every region to work around one missing reference. Use straight double quotes only for exact new readable scene text: ```text In Region A, change the sign to "Library". ``` Existing scene text stays unless the prompt asks to change or remove it. Region names are controls, not requested scene text. Keep the Edit panel open while sending. The canvas must remain mounted so CAD Scene can export the mask. #### Safe spatial recovery Edit can use a marked area's spatial placement when an instruction cannot be prepared safely. The same source and union mask continue through the render. You do not need to repaint the regions. Review the result and revise the prompt only when the intended change is missing. #### References not supported GPT Image 2 Edit accepts only the source image and mask. Remove Composer references or switch to a Nano Banana model. Every model supports up to five Composer references in Create and Enhance. ### Credits and limits #### Not enough credits CAD Scene shows input requirements before credit options. When credits are the only remaining blocker, it preserves the draft or action selection and opens the available plans and top-ups. Reduce image count, choose a lower-cost model or output setting, or purchase credits. An insufficient-credit rejection rolls back the transaction. It creates no renders or jobs. Canceling checkout charges nothing and returns to the same offers. A completed return succeeds when Stripe reports `paid` or `no_payment_required`. After that verification, **Continue** returns to the blocked control with its state restored. Select the action again when you are ready. CAD Scene does not submit it automatically. See [quality and cost](/help/rendering-and-results/models-quality-credits-and-daily-limits#quality-and-cost) for the current per-image rates. #### Daily limit reached The error includes an estimated reset time for the rolling 24-hour window. Wait for that time or contact support for a higher cap. Render, Composition, and field generation have separate limits. See [credits and limits](/help/rendering-and-results/models-quality-credits-and-daily-limits#credits-and-limits). #### Too many requests A short rate limiter can reject a burst even when the daily limit remains. Wait briefly, then submit once. A provider rate limit is different. The worker retries a retryable provider failure once before showing a final failed tile. #### Project is in Trash Restore the project before sending another render. Trashed projects remain readable but reject new render writes. ### Image and dimension problems #### The image cannot be read Remove the image, then re-export or re-upload it. The file may be corrupt or its contents may not match its declared format. Use PNG or JPEG when browser format support is uncertain. If HEIC or HEIF cannot be decoded, convert it before upload. #### Source dimensions are invalid Use a normal architectural frame with readable pixel detail. Avoid a tiny thumbnail. GPT Image 2 supports aspect ratios up to 3:1. Crop a more extreme source before retrying with that model. For Edit, the source and generated mask must describe the same canvas. This input requirement does not guarantee identical output dimensions. Every output remains subject to its model's size constraints. GPT Image 2 can scale and round the source to its nearest valid dimensions. #### Too many references Remove Composer references until five or fewer remain. Source and mask images do not count toward that reference limit. ### Retry a render A failed tile offers two direct recovery actions. The failed original is refunded before any replacement is submitted. **Retry** creates one new render with the original prompt, mode, and attachments. It keeps the stored model and output settings when they remain valid. If the stored settings are invalid but the original model remains valid, Retry keeps that model and uses its current defaults. A retired or invalid model uses the global default model and its defaults. **Retry with model** keeps the prompt, mode, and attachments. Choose a compatible model and supported output settings before submitting. Changing the model resets the settings to the chosen model's defaults before you adjust them. If the prompt or attachments need correction, prepare a new Composer draft. Then send it through the normal preflight flow. Both retry actions and any new Composer send use the project's current Composition. They do not restore the original five-field snapshot. Each replacement is a new charged submission. #### Content policy rejection Rephrase the prompt without strong identifying or violent terms. Do not repeat the same rejected prompt. Content-policy failures are terminal and are not retried automatically. #### Unexpected provider error CAD Scene retries an unexpected provider failure once. If the second attempt fails, the tile becomes final and its credits are refunded. Use **Retry** for the same settings. Use **Retry with model** when another model is compatible. If the inputs need correction, prepare a new Composer draft. #### Cancellation did not stop the render Cancellation is accepted only while a job is queued or generating. Once upload starts, the render is allowed to finish. An accepted cancellation refunds that job. A late, refused cancellation does not refund a result that completes successfully. ### Contact support From a signed-in workspace, open **Help**, then select **Contact Support**. CAD Scene opens support chat with your current account details on desktop and smaller screens. If chat is unavailable, the same action opens this contact section instead. Contact [support@cadscene.com](mailto:support@cadscene.com) when: * A refund does not appear after a final failure or accepted cancellation. * A reproducible provider error remains after one careful retry. * A project or stored render cannot be opened. * You need a higher daily cap. Include the project name, study name, approximate time, and the visible error code. Do not send account passwords or private API keys.