for Maya 0.1.0

Handbook 0.1.0

Scenario for Maya

Make 3D models, mesh edits, motion and images with Scenario's models without leaving Maya 2025, 2026 or 2027. Give the panel a prompt, an image, views of an object, a mesh or a character, see the exact price on the button, and the result lands in the open scene as one undo step.

Download for Maya 2025 to 2027 Quick start

Maya 2027 with the Scenario panel docked on the right: a brass lantern generated with Meshy 7.1 and a wooden chest, imported side by side

Back in Maya

  • A model on the ground, at real size
  • A result over the object or mesh it came from
  • New UVs, material or geometry on your mesh
  • A rigged, animated character
  • A card, a material or an image plane

Each landing is one Ctrl+Z.

Screenshots may show earlier layouts, and the prices in them are examples, not quotes. Select a screenshot to enlarge it.

What it does#

  • 3D from a prompt, an image or views of an object. A model lands on the ground in front of the camera at its real size, or over the object its views were captured from, with PBR materials and import checks.
  • Edits your meshes. Remesh, UV unwrap or retexture a mesh of the scene; the result comes back fitted over it, or applied onto it after a review.
  • Animates characters. A prompt makes a character move: the model's own, or yours, rigged and animated, landed with its joints, skin and clip.
  • Images in the scene. As a card, a material or an image plane, and one click away from a 3D model.
  • Shows the price first. The exact price is on the Generate button before you click, every request is sent once and recorded on disk, and every landing is one Ctrl+Z.
Modes in this buildFromLands in Maya as
3D, TextA promptA model on the ground in front of the camera, at real size
3D, ImageAn image file, a viewport capture or an Image resultA model on the ground in front of the camera
3D, Multi-viewViews captured around a selected objectA model over the object, at its size
3D, Edit selectionA selected mesh: remesh, UV unwrap or retextureA result over the mesh, or applied onto it
3D, MotionA prompt, and your character if you wantA rigged, animated character
ImageA promptA card, a material or an image plane

What is not built yet: Known limits.

Install#

You need Maya 2025, 2026 or 2027 and a Scenario account on a plan with API access.

  1. Download scenario-maya-<version>.zip from maya.scenario.com/download/latest or the releases page and unzip it.
  2. Drag install_scenario.py from the unzipped folder onto a Maya viewport. It copies the module into your Maya modules folder, loads the plug-in, turns on autoload and opens the Scenario panel.
  3. Maya 2027 asks whether to load a plug-in from a location it does not trust yet. Choose Allow.

Scenario > Scenario Panel opens the panel later.

To uninstall, run import install_scenario; install_scenario.uninstall() in the Script Editor (Python). Your settings, job list and results stay.

Downloads#

Quick start#

  1. Install the plug-in: download scenario-maya-<version>.zip from maya.scenario.com/download/latest, unzip it and drag install_scenario.py onto a Maya viewport (Install).
  2. In the Scenario panel, choose Sign in with Scenario and approve in your browser. If your account has several teams or projects, pick one.
  3. Open the 3D tab, keep the Text mode and its default model, Meshy 7.1, and write a prompt: weathered brass ship lantern, game prop.
  4. The button shows the price once Scenario has checked it, for example Generate . 120 CU; the check is free. Press it.
  5. When the card says Ready to apply, press Import. The lantern lands on the ground in front of the camera at its real size. Ctrl+Z removes it in one step.

Find your way around#

The Scenario panel on the 3D tab: workspace at the top, the Text mode with Meshy 7.1, a prompt, the price on Generate and the job list

The panel#

Open it with Scenario > Scenario Panel. It docks beside the Channel Box and comes back with your workspace layout. From top to bottom:

  • Workspace: the team and project the panel works in (My Team / My Project). Click it to switch. Prices, uploads, results and the job list belong to that project.
  • Tabs: Image and 3D. The 3D tab has five modes: Text, Image, Multi-view, Edit selection and Motion. A tab opens on the mode you used last in it.
  • The mode: its model, with Change to pick another; the inputs the mode needs (an image, views, a mesh, a character); the prompt, which hides when the model takes none; the model's settings, read from Scenario; and the Generate button with its price. Ctrl+Enter presses it.
  • Results: one card per job of this mode, with its status, its price and the actions valid now (Import, and Apply... for an edit; Card, Material or Image plane for an image; Retry download). Before the first result, example prompts to start from. The ... menu of a card has Show file, Open on Scenario, Re-run settings (fills the form with that job's settings, sends nothing) and Copy details.
  • Jobs: every job of the project, from every Maya session (see Jobs and recovery).

The ☰ button at the top right has Workspace..., Refresh jobs, Copy diagnostics, the handbook, Privacy, Report a problem and Sign out.

The Scenario menu#

Maya's main menu bar gets a Scenario menu: Scenario Panel, Jobs, Import GLB... (any GLB, no sign-in needed), Workspace..., Sign In... or Sign Out, and Help (Handbook, Privacy, Report a Problem, Copy Diagnostics, About).

Sign in#

The sign-in page of the Scenario panel
  • Sign in with Scenario: your browser opens on Scenario's sign-in page, you approve, and Maya picks up the session.
  • Sign in on another device: the panel shows a code to enter on any device, for a machine without a browser.
  • Use an API key: a key and its secret from your project's API keys on app.scenario.com.

Secrets go to the system's credential store (macOS Keychain, Windows Credential Manager or Secret Service), never to the scene or Maya's preferences. Nothing is sent to Scenario until you sign in.

3D from a prompt#

Recording Typing a prompt, pricing it, generating with Meshy 7.1 and importing the lantern into the scene

Recorded in Maya 2027.2 with a live Scenario model. The wait for Scenario is sped up; everything else plays in real time. Videos: this flow, the whole session.

Generate#

1. Priced before sending2. Followed on Scenario3. Imported and checked
The 3D tab with Meshy 7.1 and the price on the Generate buttonThe result card while Scenario generatesThe result card after the import, with the import checks
  1. Open the 3D tab, Text mode. The default model is Meshy 7.1 Text-to-3D, preset to a 30,000-face game mesh (the raw mesh is close to a million triangles for the same price). Change lists the other text-to-3D models: Meshy T2.5 Smart Topology, the low-cost choice, Tripo P2 and Rodin Gen-2.5.
  2. Describe one object. The button shows the exact price as soon as Scenario has checked it.
  3. Generate sends the request once. The card follows the job, downloads the GLB when it is ready and shows what came back: format, faces and size in metres, with Scenario's preview picture.

Import#

Import adds the model as a new group at the size Scenario returns, its bottom centre on the ground below the camera's centre of interest. Materials are OpenPBR, with their textures written to sourceimages/scenario/. The card reports the import checks: size, materials and textures, non-manifold edges, missing textures. One Ctrl+Z removes the whole import; redo brings it back.

Recording The lantern and the chest turning in Maya's viewport

Viewport 2.0 with one key light. MP4

Import any GLB#

Scenario > Import GLB... imports any local GLB the same way, without signing in: meshes with UVs and normals, PBR materials, joints, skins, blend shapes and the first animation clip.

3D from an image#

The imageThe model, imported in Maya
A concept image of a carved wooden treasure chestThe chest generated from it with Meshy 7.1, in Maya's viewport

The image was generated in the Image tab with GPT Image 2.5 Flare. The model is Meshy 7.1 Image to 3D at the 30,000-face preset (28,984 faces), imported by the plug-in and rendered in Maya's Viewport 2.0.

Add the image#

  1. Open the 3D tab and choose the Image mode.
  2. Add the image:
    • File...: a PNG, JPEG or WebP;
    • Viewport: a capture of the view you look through, with the grid and the selection highlight hidden, so a blockout or a quick paint-over can be the start;
    • Image results: anything made in the Image tab. An Image result also has Make a 3D model from this image in its ... menu, which opens this mode with the image in place.
  3. A file or a capture is sent to your Scenario project when you add it, once per session. An Image result is already on Scenario and is used as it is.
  4. The price shows on Generate; the card then follows the job and offers Import, as for a prompt. A job without a prompt is named after its image.

One clear image of one object, on a plain background, works best. Meshy 7.1 also takes up to four views of the same object; models that take one image use the first.

Which model#

Both quick picks, from the image above, one run each:

Meshy 7.1 Image to 3D, the defaultTripo P2
Meshy 7.1 result, front and backTripo P2 result, front and back
28,984 faces (30,000 preset), carving kept on every side, about 140 s, 120 CU, up to four views4,222 faces, clean mesh with flatter carving and a plain back, about 85 s, 220 CU, one image

Change also lists Rodin Gen-2.5, Tripo 3.1 and Hunyuan 3D Pro 3.1.

3D from views of an object#

The Multi-view mode builds a model from pictures of one object taken from named sides. Start from a blockout, a kitbash or an old asset in your scene: the plug-in photographs it from the front, left, back and right, and the model returns a textured mesh of the same object, facing the same way, landed over it.

Front, left, back, right
Captured around a blockoutThe four views captured around a blockout robot
Tripo P2 Multi View, the defaultThe Tripo P2 result seen from the same four sides
Tripo 3.1 Multi ViewThe Tripo 3.1 result seen from the same four sides

Capture the views#

  1. Open the 3D tab and choose Multi-view. Each view the model takes has a slot: Front, Left, Back and Right for the Tripo models; Hunyuan 3D Pro 3.1 adds Top, Bottom and the two front three-quarter views.
  2. Select one object and press Capture views. The plug-in renders it from each side with temporary orthographic cameras, all at one scale, clipped close around the object so the floor and its neighbours stay out of the pictures. Nothing is added to the scene or to the undo queue, and the render settings it touches are put back.
  3. Left is the object's own left: with the object facing front (+Z), the side Maya's Right view shows. Model your blockout facing +Z.
  4. A slot also takes a file or an Image result, from its menu. Each view is sent to your project once. The Tripo models need the front and at least one more view; the Generate button says what is missing, then shows the price.

Where the result lands#

Import places the result over the object its views came from, at the object's size and facing the same way, as a new group. Your object is not changed: hide it, or keep it to compare. Views added as files land like any 3D result, on the ground in front of the camera.

Recording The Tripo P2 robot turning in Maya's Viewport 2.0
The Tripo P2 robot with every edge drawn: 4,987 faces

A robot blocked out from cubes in Maya and one Tripo P2 run on its four views. Right, the same mesh with every edge drawn.

Which model#

Same four views, one run each:

ModelFacesGLBPrice
Tripo P2 Multi View, the default4,987, a clean low-poly mesh1.4 MB220 CU
Tripo 3.1 Multi View, the low-cost choice1,425,173, dense42 MB45 CU
Hunyuan 3D Pro 3.1 Multiviewstarts at 40,000, its lightest settingnot run yet120 CU

Both Tripo results kept the shape and colours on every side, took under four minutes and landed on the blockout within half a centimetre of its 82 cm height.

Quad meshes and FBX results#

The Tripo models have a quad setting: the mesh comes back in quads, delivered as an FBX file (Scenario sends no GLB then). The plug-in imports it through Maya's own FBX importer, as one Ctrl+Z, and lands it like a GLB: on the ground in front of the camera, or over the captured object in the Multi-view mode.

The robot from Tripo 3.1 Multi View with quad on: as imported, and with every edge drawn, a grid of quads

Tripo 3.1 Multi View with quad on and a face limit of 8,000, from the four robot views: 8,153 faces, 8,132 of them quads. 53 CU.

What the plug-in does around the FBX importer#

  • Keeps the scene's unit, up axis, playback range, current frame and frame rate, which the importer would change.
  • Imports even when the scene already has nodes of the same names.
  • Writes the file's textures under sourceimages/scenario/.
  • Cleans up the names the FBX format mangles.
  • Keeps the importer's materials, with colour textures in sRGB and the other maps Raw.
  • Lands a rigged character upright and in one piece, in a Y-up or a Z-up scene.
  • Starts a clip on the scene's start frame, as for a GLB, and reports the same import checks.

Edit a mesh of the scene#

The Edit selection mode sends one of your meshes to an edit model and brings the result back: over the mesh as a new object, or onto the mesh itself.

Send a mesh#

  1. Select one mesh (the object, or some of its faces) and open 3D, Edit selection.
  2. Choose the task: Remesh, UV unwrap or Retexture. Each task keeps its own model; the defaults are Tripo Retopology v3, Tripo Smart UV and Meshy 7 Retexture.
  3. Use selection writes the mesh, with its UVs and base colour textures, to a file in the project's images/scenario/captures folder. Object, scene and path names stay on your machine.
  4. The mesh is checked against the model before anything is sent (Tripo Smart UV takes up to 80,000 triangles, Meshy UV Unwrap 44,000, Hunyuan UV Unwrapping 30,000); a mesh it cannot take shows why and is not sent. An unchanged mesh is sent once.
  5. Retexture needs a prompt. The price shows on Generate.

Import over the mesh#

Import places the result over the mesh it came from, as a new group, even if you moved the mesh after sending it. Your mesh is not changed.

Most edit models return the mesh resized and centred. The plug-in keeps the file it sent, fits the result back onto it and onto the mesh's current place, then checks that both are the same shape. A result that is not still lands, and the import message says so.

What came back#

A bevelled crate of 1,052 triangles with the cube's default UVs, one run per model:

Your meshMeshy 7 RetextureTripo 3.0 Texturing
The crate sent, grey, before any editThe crate retextured by Meshy 7 as weathered planks with metal cornersThe crate retextured by Tripo 3.0 in dark brown wood
1,052 trianglesSame triangles and the same UVs; base colour, normal, metallic and roughness maps; 40 CUSame triangles and the same UVs; PBR textures; 15 CU
Your UVs, on a checkerTripo Smart UV
The crate with its default UVs on a checker: large squares, stretched on the bevelsThe crate with Tripo Smart UV's layout on the same checker: even squares across the faces
The cube's default layoutA new layout on the same triangles; 40 CU
What was sentMeshy RemeshTripo Retopology v3
The crate as sent, every edge drawn: an even grid of bevelled panels split in trianglesThe crate remeshed by Meshy: larger, irregular triangles over the same shapeThe crate remeshed by Tripo: larger triangles in a more regular pattern over the same shape
1,052 triangles (398 faces in Maya)522 triangles, new UVs, base colour and metal-roughness maps baked; 20 CU560 triangles, a baked normal map; 70 CU

Apply onto the mesh#

Apply... writes the result onto the mesh itself. Before anything changes, the plug-in checks that the result is the same surface as your mesh (for a remesh, the same shape), then a review lists what changes, what is kept and what needs your confirmation. One Ctrl+Z undoes the whole apply.

TaskWhat Apply changesWhat it keeps
UV unwrapThe current UV set gets the result's UVsThe old layout as <set>_scnPrev, geometry, other UV sets, materials
RetextureA new material from the result's maps (base colour, metal and roughness, normal) is assigned to the mesh; UVs too if the model changed themThe old material, unassigned; Maya's default material is never edited
RemeshThe mesh's shape is replaced by the result's mesh, under your transform and with your shape's name; it gets the result's material when the result has texturesThe transform (name, place, attributes, parent, sets, connections); the old shape, hidden, as <shape>_scnPrev with its history

All five results above were applied onto the crate this way.

What Apply asks or refuses#

  • It asks before deleting the mesh's construction history, which would overwrite new UVs, and before giving one material to a mesh that has several.
  • It refuses deformed (skinned), referenced and locked meshes in this version, and a remesh refuses instanced ones. Import still works on them.

Animate a character#

The Motion mode turns a prompt into a character that moves: a skinned mesh, its joints and a clip, imported as one Ctrl+Z. Some models bring their own character; others rig and animate yours.

Recording A wooden mannequin waving its right hand, from Meshy Text to Motion
Recording The Multi-view robot, rigged and animated by Uthana Text to Motion 3.0, raising its right arm

"waves hello with the right hand". Left, Meshy Text to Motion from the prompt alone: its own mannequin, 52 joints, 3 seconds. Right, Uthana Text to Motion 3.0 on the robot from the Multi-view chapter, sent from the scene: rigged with 52 joints and animated for 4 seconds.

From a prompt alone#

Open the 3D tab and choose Motion. The default model, Meshy Text to Motion, needs only the prompt: one simple action works best (a walk, a wave, a jump), 2 to 10 seconds, 40 CU whatever the length.

On your own character#

  1. Press Change and pick Uthana Text to Motion 3.0 or Cartwheel Text to Motion.
  2. Select the character (its group or its meshes) and press Use selection. The meshes are written as one GLB, with neutral names, and sent to your project once. Nothing is added to the scene or to the undo queue. Cartwheel needs a character, and the Generate button says so until one is sent; Uthana takes one or makes its own.
  3. Import lands the result over your character, at its size, measured on the clip's first frame. Your character is not changed.

Model the character standing, facing front (+Z), arms away from the body. Check which way a rig faces before animating further: in our test, Cartwheel's rig faced the robot's back.

Frame rate and timeline#

  • A model's frame-rate setting starts at the scene's rate when the model offers it (Uthana: 24, 30 or 60 fps). When a clip was made at another rate (30 fps in a 24 fps scene), its keys fall between frames and the result says so.
  • The clip starts on the scene's start frame; the playback range is not changed.

Which model#

One prompt, one run each:

ModelCharacterResultPrice
Meshy Text to Motion, the defaultIts own wooden mannequin (52 joints)FBX, in about 30 seconds40 CU, 2 to 10 s
Uthana Text to Motion 3.0, first pick for your characterYours (auto-rigged) or its own (160 joints)GLB, in about 3 minutes104 CU for 4 s; 124 CU with a character
Cartwheel Text to MotionYours, requiredMaya FBX, in 2 to 4 minutes72 CU for 3 s
One row per run: Meshy's mannequin and Uthana's own character wave from the prompt alone; Uthana rigs the robot facing front; Cartwheel's rig faces the robot's back

Generate an image#

ReadyAs a card facing the cameraAs a material on a selected mesh
The Image tab with a ready resultA generated image as a card in the viewportThe image as the material of a cube

Land it in the scene#

The Image tab prices and generates like the 3D tab (default model: GPT Image 2.5 Flare). A ready image lands three ways, each one Ctrl+Z:

  • Card: a textured plane facing the camera, at its centre of interest. Use it as a reference board next to your model.
  • Material: base colour of a new material on the selected meshes or faces.
  • Image plane: on the current camera, to model or animate against.

Files go to sourceimages/scenario/.

Turn it into a 3D model#

Make a 3D model from this image, in a result's ... menu, opens 3D, Image with the image in place: concept, then mesh, without leaving Maya.

Choose a model#

The model picker on the 3D tab

Change opens the picker for the current mode: the mode's quick picks first, the ones this guide compares, then the other models of that kind in Scenario's catalog, with search, a Team models filter for your team's own models, and Show legacy for older models. The settings below the prompt follow the model you pick, read from Scenario.

Prices and spending#

The price on the button#

Every request is priced before it is sent. When you edit the prompt or a setting, the panel asks Scenario for the price, a free check, and the button shows it: Generate . 120 CU. Price unavailable (Retry) means the check failed; nothing was spent.

What the plug-in guarantees#

  • A price is valid for the exact request it was checked for, for two minutes. Any edit asks for a new price.
  • The job is saved on your computer before the request is sent, and it is sent once. If Maya crashes or the connection drops while it is being sent, the job shows as Not confirmed (see below) rather than being sent again.
  • The plug-in sets no spending cap of its own. Your team's limits on Scenario apply.

Jobs and recovery#

The job list#

Jobs, at the bottom of the panel or in the Scenario menu, lists every job of the project from every Maya session, newest first: state, model, prompt or input, quoted and charged CU. Right-click a job for Copy details (local and Scenario job ids, prices, times, the error and its hint), for a support request.

A job goes through Preparing, Submitting, Queued, Starting, Generating (with a percentage when Scenario reports one), Finalizing, Finished and Downloading to Ready to apply, then Applied once it is in the scene. It can also end as Failed, Blocked (refused by Scenario's content rules), Download failed, Canceled or Not confirmed.

When Maya closes#

Jobs live on Scenario, not in Maya. Close Maya during a long generation and, at the next start, the panel offers the results that finished meanwhile: press Download. A download that stopped resumes from where it was, with a fresh link; Retry download on the card does the same by hand. If Scenario cannot be read several times in a row, delivery pauses and the card says why.

Not confirmed#

A job is Not confirmed when Maya stopped, or the connection dropped, while its paid request was being sent: Scenario may or may not have received it, and may have charged it. Maya warns at the next start. To protect you from paying twice, the plug-in blocks the identical request (same project, model and settings). Check your project's jobs on app.scenario.com before generating it again. Changing anything in the request sends a new one.

Files and folders#

Results go into the current Maya project (File > Set Project), so they travel with your scene:

  • 3D results: scenario/<date>/<name>/ in the project, the GLB or FBX with a scenario.json record of how it was made.
  • Images, and the textures of 3D results: sourceimages/scenario/<name>/.
  • Captures, views and the meshes sent for an edit: images/scenario/captures/.

Results are also in your Scenario project, so you find them again on app.scenario.com.

Every node the plug-in creates carries its provenance (model, prompt, price, job and asset ids) as attributes, so the scene opens on machines without the plug-in and anyone can tell where an asset came from. Anyone you send the scene to can read those prompts.

The plug-in's own files (settings, the job list, the model catalog cache and logs) are in scenario/ inside Maya's user folder (Documents/maya on Windows, ~/Library/Preferences/Autodesk/maya on macOS, ~/maya on Linux).

What leaves your machine#

Scenario for Maya connects Autodesk Maya to the Scenario platform. This page says what leaves your computer, when, where it goes, and what stays on your machine. Scenario's own handling of the data it receives follows Scenario's Terms of Service and Privacy Policy, and its Trust Portal.

What is sent to Scenario, and when#

Nothing is sent before you sign in. After that, the plug-in talks to Scenario (api.cloud.scenario.com, clerk.scenario.com for sign-in, and Scenario's file storage) only for these actions:

ActionWhat is sent
Opening the panel, the picker or the workspace menuRequests for the model catalog and your teams and projects
Editing a requestThe request (model, prompt, settings, the ids of files already sent) for a free price check, 0.7 s after you stop typing
GenerateThe same request, as a paid request
Adding an image (a file, a viewport capture, views captured around an object)The picture, uploaded to your Scenario project when you add it
Use selection, for a mesh edit or a character to animateThe selected meshes as one GLB: geometry, UVs, normals and base colour textures. Object, material, scene and path names are replaced by neutral names
Jobs and resultsRequests for the status of your jobs and their result files

Not sent: the rest of your scene, file paths, node names, your Maya project's contents, or anything from other open scenes.

Result files are downloaded through signed links from Scenario's storage, which carry their own authorization, never your Scenario credentials.

What is stored on your computer#

ItemWhere
Sign-in token or API secretYour operating system's credential store (macOS Keychain, Windows Credential Manager, Secret Service on Linux). If none is available, a file readable only by your user account
Settings, model catalog cache, job list, logsscenario/ in Maya's user folder
Results, captures and the meshes sent for an editYour Maya project, in scenario/, sourceimages/scenario/ and images/scenario/
Provenance (model, prompt, price, job and asset ids)Attributes on the nodes the plug-in creates, saved inside your .ma or .mb file

Secrets are never written into scenes, Maya preferences, Maya.env, project files, settings or logs.

Provenance travels with your scene file: anyone you send the scene to can read the prompts and ids stored on its nodes.

The plug-in sends nothing else: no usage data, no update check.

Your controls#

  • Sign out asks Scenario to revoke the session and removes the secret from your credential store.
  • API keys can be revoked at any time from your team page on app.scenario.com.
  • Uninstall (in Maya's Script Editor, Python: import install_scenario; install_scenario.uninstall()) removes the plug-in and keeps your data. To remove it too: sign out first (the stored secret), delete scenario/ in Maya's user folder (settings, job list, logs), and in each Maya project you used, scenario/, sourceimages/scenario/ and images/scenario/ (results, captures and the meshes sent). Scenes you saved keep the prompts and ids on their nodes, in the attributes whose names start with scenario_: delete those attributes (Attribute Editor, Extra Attributes) or the nodes.

Contact#

Security issues: see Security. Other questions: support@scenario.com.

Troubleshooting#

Sign-in#

  • The browser does not come back to Maya: use Sign in on another device and type the code, or an API key.
  • "Unlock the login keychain" (macOS): the Keychain is locked; unlock it and sign in again.
  • "Sign in again or check the API key": the session expired or the key was revoked.

Prices and requests#

  • Price unavailable: press it to retry. A request the model refuses (a missing input, a value out of range) shows Scenario's reason.
  • "Upgrade the plan or wait for the limit to reset": your team's plan or limit refused the request; nothing was spent.
  • "Paid requests from Maya cannot name a task yet": the project bills every request to a task; choose another project.
  • "Mesh not accepted by this model": too many triangles for the edit model; reduce the mesh or pick another model.

Network#

  • A certificate error behind a company proxy: the proxy inspects TLS; its root certificate must be in the system's trust store, which the plug-in uses.
  • Download failed: press Retry download; it resumes.

Reporting a problem#

Scenario > Help > Copy Diagnostics copies versions, paths and state, never a secret, to paste into a GitHub issue with the job's Copy details. Or write to support@scenario.com.

Known limits#

  • Agents: a local Scenario MCP server inside Maya, so Claude Code, Codex or Cursor can drive the same actions, is not built yet.
  • 3D: rigging without a motion, splitting into parts, putting a motion onto a rig already in the scene (retargeting, HumanIK), video to motion.
  • Images: editing, upscale, LoRAs.
  • Other kinds of result: materials, sky domes, video, audio.
  • A settings page, a history of past results, and a list of the Scenario assets in the open scene.
  • Linking a Not confirmed job to a Scenario job from the panel.
  • Tested on Maya 2027.2 on macOS. Maya 2025 and 2026, Windows and Linux are supported but not yet checked by hand; the Multi-view, Edit selection and Motion modes were checked in automated runs of Maya, not by hand.

Changelog#

0.1.0 (2026-11-16)#

Features#

  • 3d: 3D lane, text to 3D; GLB-only download; import on the ground (16ec376)
  • 3d: Apply UV unwrap and Retexture results onto the mesh itself (4386ee7)
  • 3d: check an imported edit result against the mesh by surface distance (1746ebb)
  • 3d: Edit selection, remesh, UV unwrap or retexture a mesh of the scene (5859a72)
  • 3d: image to 3D, the 3D tab's Image mode (4952aee)
  • 3d: import FBX results, so quad meshes land in the scene (ee2dabf)
  • 3d: Motion mode, a prompt to a character that moves (eaf2923)
  • 3d: Multi-view mode, views captured around an object into a 3D model (577ae27)
  • 3d: Replace geometry, apply a remesh result onto the mesh itself (a69e8fc)
  • core: call Scenario's REST API through its Python SDK (#16) (1da19cb)
  • core: GLB reader and format sniffing for 3D results (931045b)
  • core: result delivery, downloads with receipts, catalog cache, lanes, provenance (503397c)
  • core: Scenario MCP client, sign-in, credential stores, quotes and job ledger (8fdf7d5)
  • core: sign in as Maya's registered OAuth application (#7) (9b8ab16)
  • maya: GLB import as one undo step; Scenario &gt; Import GLB... (2f3b727)
  • maya: job runner from quote to landed result, with restart recovery (6521b2d)
  • maya: land images as a card, a material on the selection or an image plane (92bbf4f)
  • maya: plug-in entry, runtime, main-thread dispatcher, panel, menu and installer (6569c7f)
  • ui: Image lane in the panel: model picker, settings, priced Generate, result cards (22937ac)

Bug Fixes#

  • 3d: land GLB results at the right size in metre and millimetre scenes (b120574)
  • ci: start the first release at 0.1.0, not release-please's default 1.0.0 (790b199)
  • core: a paid call refused with 429 is reported as not sent (fd697d9)
  • core: count a job's add-on charges in what it cost (1da19cb)
  • core: forget the session on sign-out even when offline (9b8ab16)
  • lanes: fetch a 3D result's preview after the download; card placeholder (4ecc332)
  • lint: scan new files too; drop an em dash from a recorded schema (b6fe46f)
  • maya: show textures after landing; stack example prompts (3094d76)
  • ui: bring the panel tab to the front, keep the sign-in links whole, scale pixel fonts (3e7a174)
  • ui: each lane starts with its own example prompt until used (e8974fc)
  • ui: grow the sign-in dialogs when their text wraps (#10) (c95bf12)
  • ui: open one project picker at a time (#12) (676068c)
  • ui: workspace question opens without a nested event loop (539ab44)

Documentation#

  • 3d: edit results sent off-centre, Meshy UV Unwrap in place (61255b8)
  • docs: publish maya.scenario.com as a handbook built from the docs with plugin-site (2385841)
  • README with pictures, recordings and diagrams from a real Maya session (5e4efc2)
  • spec v1 draft and privacy page draft (0c7c0ff)
  • spec: record decisions of 2026-10-19 (fa10cb6)

Miscellaneous Chores#

  • deps: Bump the python group with 2 updates (#14) (bfdedaf)
  • repo: align with the shared open source practices (#6) (f83f60b)
  • repo: policies, templates, CI, lint, free contract check and GUI test driver (bacc4be)
  • ruff lint and format settings, formatting pass (cd5d5b5)

Continuous Integration#

  • ci: publish maya.scenario.com behind a Vercel proxy (#18) (e7a804e)
  • deps: Bump astral-sh/setup-uv from 10.3.0 to 10.3.2 in the actions group (#8) (8208ba5)
  • deps: Bump the actions group with 5 updates (#15) (c3ce0a3)
  • release: release the plug-in as a checked ZIP with release-please (#17) (53bdda4)

Tests#

  • core: compare texture file names with os.path.basename so the test passes on Windows (45ba9b3)
  • gui: live generate stage; docs for the Image lane (f43ff24)
  • tools: GUI stages check that Maya quits by itself; name the slowest main-thread call (291b3bc)

Changelog#

Hand-written history#

Written before release automation. From the first release on, release-please writes each entry above this one from the pull request titles.

Features#

  • Sign in to Scenario with the browser (OAuth with PKCE), a code on another device, or an API key; secrets kept in the system keychain.
  • Scenario panel docked beside the Channel Box, restored with the workspace; team and project picker; job list.
  • Durable job ledger shared by every Maya session of the user, with recovery after a crash: a request cut off while being sent shows as Not confirmed and blocks an identical request until checked.
  • Drag-and-drop installer with upgrade and uninstall; module file for studio deployment.
  • Image lane: choose a model (search, team models, legacy), write a prompt, adjust the model's settings, see the exact price on Generate before sending. Results download into the project's sourceimages/scenario folder with a checksum and a scenario.json record, and land as a textured card facing the camera, a material on the selected meshes or faces, or an image plane, each removed by one Ctrl+Z.
  • Results that finish while Maya is closed are offered for download when the panel opens; interrupted downloads resume where they stopped.
  • Every landed node carries its Scenario provenance (asset, job, model, prompt, price) as plain attributes, so scenes open without the plug-in.
  • 3D results land through the plug-in's own GLB builder as one undo step: welded meshes with UVs and normals, PBR materials with textures written to the project, joints with rest orientation in jointOrient, skins, blend shapes and the first animation clip; import checks report faces, size, UV sets, non-manifold edges, missing textures, joints, clips and targets.
  • Scenario > Import GLB... brings any local GLB into the scene the same way, without signing in.
  • Updating the plug-in while a Scenario import sits in the undo history finishes after a Maya restart instead of failing.
  • 3D lane: text to 3D with Meshy 7.1 (preset to a 30,000-face game mesh), Meshy T2.5 Smart Topology, Tripo P2 or Rodin Gen-2.5. Only the GLB of each result is downloaded (chosen by the asset's format, not its position), with its preview picture for the card; Import places the model on the ground below the camera's centre of interest and reports the import checks.
  • The model catalog is cached per kind of model, so refreshing the 3D list keeps the image list.
  • A 3D result whose preview Scenario renders after the download gets it a few seconds later; until then its card shows "3D" instead of an empty square.
  • Import checks read "1 material, 3 textures" instead of "1 material(s), 3 texture(s)".
  • 3D tab, Image mode: turn one image, or up to four views of an object, into a textured model with Meshy 7.1 Image to 3D (preset to a 30,000-face game mesh), Tripo P2, Rodin Gen-2.5, Tripo 3.1 or Hunyuan 3D Pro 3.1. Add the image from a file, a capture of the viewport (grid and selection highlight hidden, no undo step) or a result of the Image tab, which is used as it is without a new upload. Files are sent to Scenario when you add them, once per session and project.
  • Image tab results have "Make a 3D model from this image" in their menu.
  • The 3D tab has a Text and an Image mode, sharing one results list; it reopens on the mode used last. Re-run fills the right mode, images included.
  • The prompt box follows the model: hidden when the model takes no prompt, marked optional when it only guides the texture.
  • A form that misses its image says "Add an image".
  • tools/render_glb.py renders a GLB in Viewport 2.0 without a window, through the plug-in's importer: stills or a turntable GIF for documentation.
  • 3D tab, Edit selection mode: remesh, UV unwrap or retexture a mesh of the scene (Tripo Retopology v3, Meshy Remesh, Tripo Smart UV, Hunyuan UV Unwrapping, Meshy UV Unwrap, Meshy 7 Retexture, Tripo 3.0 Texturing). Use selection writes the selected mesh as a GLB (object space, metres, neutral names, its UVs and base colour textures), checks it against the model's limits (format, triangle cap) before anything is sent, and sends it once per unchanged mesh. Each task remembers its own model; Retexture asks for a prompt. One mesh at a time in this version.
  • Import of an edit result places it over the mesh it came from, as a new group, fitted with one uniform scale and an offset (most edit models return the mesh resized and centred), even when the mesh moved after it was sent. The mesh itself is not changed. The fit is checked by surface distance both ways; a result that is not the same shape still lands, and the import message says so.
  • Apply... on UV unwrap and Retexture results writes them onto the mesh itself after a review (what changes, what is kept, what needs a tick): Replace UVs fills the current UV set and keeps the old one as <set>_scnPrev; Replace textures assigns a new material built from the result's maps. The result is first proven to be the same surface as the mesh (vertices, faces, winding, one UV per face corner). One Ctrl+Z undoes the whole apply; deformed, referenced and locked meshes are refused in this version.
  • tools/render_glb.py --checker N shows the UV layout with a checker instead of the materials.
  • Apply... on Remesh results replaces the mesh's geometry after a review: the result's mesh becomes the shape under your transform, with your shape's name and outgoing connections; it gets the result's material when the result has textures, otherwise keeps yours. The old shape stays, hidden, as <shape>_scnPrev with its history. The result must be the same shape by the surface-distance check; instanced meshes are refused in this version. One Ctrl+Z undoes it.
  • tools/render_glb.py --wire draws every edge, to show a topology.
  • FBX results import through Maya's own FBX importer as one Ctrl+Z, so a Tripo result with the quad setting (delivered as FBX only) can be imported. The scene's unit, up axis, playback range and frame rate are kept; textures go under sourceimages; escaped names (FBXASC045) are cleaned; the importer's materials stay, with data textures Raw and normal maps read as normals. The 3D tab downloads the GLB when a job returns one, else the FBX. tools/render_glb.py renders FBX files too.
  • 3D tab, Multi-view mode: views of one object from the front, left, back and right (and top, bottom and 45 degree views where the model takes them) into a textured model, with Tripo P2 Multi View, Tripo 3.1 Multi View or Hunyuan 3D 3.1 Pro Multiview. Capture views renders the selection from each side the model takes with temporary orthographic cameras, at one scale, clipped to the selection's box so neighbours stay out; nothing stays in the scene or the undo queue. Each view can also take a file or an Image result. Tripo P2 Multi View is the default (a clean mesh of a few thousand faces); Tripo 3.1 Multi View is the low-cost choice; Hunyuan starts at its lightest mesh (40,000 faces). Import places a result made from captured views over the object they show, at its size and facing the same way.
  • 3D tab, Motion mode: a prompt to a character that moves, with Meshy Text to Motion (the default: its own mannequin, from the prompt alone), Uthana Text to Motion 3.0 (your character or its own) or Cartwheel Text to Motion (your character, as Maya FBX). Use selection sends the selected character (a group or its meshes) as one GLB, once; Cartwheel waits for one. The model's frame-rate setting starts at the scene's rate when the model offers it. Import brings the character in with its joints, skin and clip, over the character it was made from when one was sent. The model picker of the Text and Edit selection modes no longer lists motion models.
  • tools/render_glb.py --play STEP renders a landed clip over time, for animated GIFs.
  • A clip whose keys fall between the scene's frames (made at 30 fps, imported into a 24 fps scene) is reported in the import checks.

Fixes#

  • A rigged FBX lands in one piece: its skinned meshes no longer inherit the group's transform, which turned them twice in a Z-up scene (the character came in upside down) and moved them twice when placed on the ground or fitted over an object. Its clip now starts on the scene's start frame, as a GLB clip does.
  • A GLB with vertex colours imports (creating the colour set failed on its arguments).
  • 3D results and Import GLB land at the right size in scenes set to metres or millimetres (they were 100 times too small in metres and 10 times too large in millimetres; centimetre scenes were right).

Development#

  • tools/lint.py also checks files not yet added to git, so a local run before a commit finds what CI finds.
  • The fake Scenario server answers the motion models like the live ones (Cartwheel refuses to price without a character, Uthana prices one in, results are a skinned, keyed character), and serves their recorded schemas.
  • The fake Scenario server answers the edit models like the live ones (the sent mesh back resized and centred, with new UVs, a texture or other triangles over the same shape), so Edit selection is tested end to end without spending.

Licence#

MIT, see LICENSE.

Autodesk and Maya are trademarks of Autodesk. This project is not affiliated with or endorsed by Autodesk.

The Scenario logo is a trademark of Scenario and is not covered by the MIT license.

This handbook is generated from the plug-in's docs, version 0.1.0, commit 45a7a88, 16 November 2026.