Skip to content

Create 3D assets

Create a textured 3D object for a game, scene or visualization from a description or reference image. Muse Code prepares an image of the object, generates the 3D model and saves the files in your project.

3D asset creation is built into Muse Code and included in every subscription plan. It counts towards your subscription allowance. You don't need to install a plugin or set up a separate 3D service.

Before you start

Install Muse Code, sign in with the account that has your active subscription, and start a session in your project:

bash
cd /path/to/your/project
muse

3D asset creation isn't available with pay-as-you-go API keys or as a public Meta Model API endpoint. See authentication and billing if you're unsure which credential your session uses.

Create an asset from a description

Describe one object and how you want to use it. Include its shape, colours, materials and any style requirements:

text
Create a textured 3D model of a small brass lantern for my browser game.
Give it a rounded handle, a square base and weathered metal surfaces.
Make the whole lantern visible in the reference image.

Muse Code first creates a reference image with Muse Image, then uses that image to generate the 3D asset. The reference image determines the object's appearance, so correct it before requesting another model if the shape, colours or parts are wrong.

For several objects, ask for one asset per object. A lantern, a crate and a character are three assets, even when they belong to the same game.

Create an asset from your image

  1. Refer to its image label and ask Muse Code to create the object:

    text
    Create a 3D model of the object in [Image #1]. Keep its shape,
    proportions, colours and materials. Use it as a prop in this project.
  2. Review the prepared reference image before using the generated model.

Muse Code prepares a new render from your image before 3D generation. This cleanup pass changes the view, background and lighting while aiming to preserve the object. The 3D model is generated from that prepared image, rather than directly from your original file.

If the render changes a part or loses a detail that matters, describe the difference and ask Muse Code to correct the reference image first.

Prepare a clear reference

For a useful reference image, ask for:

  • One object, centred and fully visible, with space around its edges.
  • A three-quarter view that shows the front, one side and the top.
  • A plain background without other objects.
  • Soft, even lighting without strong shadows or reflections.

The 3D tool accepts images prepared by the image tool in the current run. If you resume a session, ask Muse Code to prepare a fresh reference image before creating another model. Copying an earlier generated image to a new path doesn't make it eligible.

Choose quality and speed

The 3D tool works with Muse Wonder, Muse Spark and Muse Ember. You don't need Muse Wonder Full to create an asset. See 3D asset availability by plan for the variants your subscription includes.

Ask for Nano when you want a quick iteration, or Pro when you want higher quality and your plan includes it.

For a game that needs a low-poly asset, say so in the request. If you have a polygon budget, include the number of faces you want.

Use the generated files

Muse Code saves the asset in a new folder under generated_models/ and returns the path to its primary model file and any companion files. GLB is the default model format.

Ask Muse Code to import the model into your game, scene or modelling tool using that path. Keep the generated folder together so companion textures remain available. Muse Code returns files; it doesn't provide a built-in 3D viewer.

For example, after generating the lantern, continue in the same project:

text
Load the generated lantern GLB into my existing Three.js scene.
Place it beside the player, scale it to fit the scene, and keep the
original generated files unchanged.

Check the asset in your target viewer or engine. Generated models have a normalised size rather than real-world dimensions, so set the final scale in the scene.

Work within the model's limits

Each generation creates one static, unrigged object. Rigging, animation and assembling a scene are separate steps after generation.

Small text and repeated fine details, such as keyboard keys or wheel spokes, can be inaccurate. Ask Muse Code to add those details with geometry or code where your application needs them to be precise.

Recover an interrupted generation

If Muse Code reports a job ID, keep it. Ask the agent to check that job or download its completed files before asking for a new generation:

text
Check the 3D generation job you started. If it completed, download its
files instead of generating another lantern.

If the service is busy, let the agent check the existing job rather than repeatedly requesting the same asset. If the reference image is rejected, try a different image or description. If the feature is unavailable in your session, check your subscription sign-in and installed build before changing the request.

Next steps