Skip to main content
Gizmo is an alpha product under active development. If something isn’t working the way you expect, this guide covers the most common issues and how to resolve them. If you run into something not listed here, please reach out — your feedback directly shapes the product.
Gizmo is currently in alpha. You may encounter rough edges, unexpected behavior, or temporary outages. Fast iteration is the priority, and every bug report or piece of feedback is genuinely appreciated.

​
Common Issues

Gizmo is currently access-gated during the alpha period. Not everyone can sign up freely — access is granted on a request basis.To request access:Send an email to viswajit@antimlabs.com with the subject line Gizmo Alpha Access Request and a brief note about your use case (e.g., Isaac Sim workflows, MuJoCo simulation research). The team will get back to you to grant access.If you have already been granted access and are still seeing an “access denied” error, try signing out and signing back in. If the issue persists, email the same address with the error message you’re seeing.
AI-powered 3D asset generation involves significant compute and typically takes one to two minutes per asset. This is expected behavior during the alpha.What to do:
  • Wait at least 2 minutes before assuming something is wrong.
  • Do not navigate away from the page or close the tab while generation is in progress.
  • If generation appears stuck for more than 5 minutes with no progress indicator update, try refreshing the page and submitting your prompt again.
If the problem happens repeatedly for the same prompt, please report it to viswajit@antimlabs.com with the prompt text so the team can investigate.
The quality of generated assets is highly dependent on how specific and descriptive your text prompt is. Vague prompts often produce incomplete or unexpected results.Tips for better results:
  • Include material (e.g., “stainless steel”, “black plastic”, “powder-coated aluminum”)
  • Specify dimensions where relevant (e.g., “1.2 meters tall”, “standard doorway width”)
  • Describe color explicitly (e.g., “bright yellow”, “matte gray”)
  • Clarify purpose or context (e.g., “used in a warehouse packing station”, “medical IV pole on casters”)
Example of a weak prompt: a shelfExample of a stronger prompt: a heavy-duty metal warehouse shelving unit, 2 meters tall, 5 shelves, powder-coated gray steelIf you’ve tried refining your prompt and still get a poor result, please email viswajit@antimlabs.com with both the prompt you used and a description (or screenshot) of what was generated. This feedback is critical for improving the model.
If your exported file fails to load in NVIDIA Isaac Sim, check the following:1. Verify you selected the correct export format. Isaac Sim supports two formats from Gizmo:
  • USD — recommended for most Isaac Sim workflows; preserves scene hierarchy and materials.
  • URDF — use when you need a robot description format compatible with ROS-based Isaac Sim pipelines.
Make sure you selected the format that matches your intended workflow before exporting.2. Check Isaac Sim version compatibility. Gizmo targets recent versions of Isaac Sim. If you are running an older version, the USD schema version or URDF features used may not be supported. Updating to the latest Isaac Sim release is recommended.3. Look at the Isaac Sim console output. When loading fails, Isaac Sim often prints a detailed error to its console. Check the output panel for messages about missing references, unsupported prim types, or schema mismatches — these point to the specific issue.If none of the above resolves your issue, email viswajit@antimlabs.com with the export format, your Isaac Sim version, and the error message from the console.
If your exported MJCF/XML file fails to load in MuJoCo, try the following steps:1. Check the MJCF format version. Gizmo exports MJCF targeting a recent MuJoCo version. If you are using an older version of MuJoCo, some XML attributes or elements may not be recognized. Update MuJoCo to the latest release if possible.2. Use the Python API for detailed error messages. The MuJoCo Python bindings provide much more descriptive error output than the standalone viewer. Load your file programmatically to get a precise error location:
import mujoco

model = mujoco.MjModel.from_xml_path("your_exported_asset.xml")
Any parse or validation errors will be raised as exceptions with line numbers and attribute names, making them much easier to diagnose.3. Validate XML structure. Open the file in a text editor and check that it is well-formed XML (no unclosed tags, no special characters in attribute values). Export issues during alpha may occasionally produce malformed output.If you identify a reproducible export error, please report it to viswajit@antimlabs.com with the XML file attached and the error message from MuJoCo.
If the Gizmo scene editor freezes, stops responding to clicks, or appears blank, try the following in order:1. Refresh the page. A simple page refresh (Cmd+R / Ctrl+R) resolves most transient UI issues. Your scene data is saved server-side, so you should not lose work.2. Clear your browser cache. Stale cached assets can sometimes cause the editor to misbehave after a Gizmo update. Clear your browser cache and hard-reload the page (Cmd+Shift+R / Ctrl+Shift+F5).3. Use a supported browser. Gizmo is tested on Google Chrome and Mozilla Firefox on desktop. Other browsers (Safari, Edge, mobile browsers) are not officially supported during alpha and may have compatibility issues.4. Check your GPU / WebGL support. The 3D scene editor requires WebGL. Make sure hardware acceleration is enabled in your browser settings and that your graphics drivers are up to date.If the editor remains unresponsive after trying all of the above, please email viswajit@antimlabs.com with your browser version and a description of what you were doing when it became unresponsive.
Bug reports are incredibly valuable during the alpha — thank you for taking the time to report one.Please email viswajit@antimlabs.com with:
  • A clear description of the bug
  • Step-by-step instructions to reproduce it
  • What you expected to happen vs. what actually happened
  • Any screenshots, screen recordings, or error messages
  • Your browser name and version (for UI bugs)
  • The export format and simulator version (for export bugs)
Use the subject line Gizmo Bug Report so it gets routed correctly. The team reviews all reports and iterates quickly.

​
Still Need Help?

Frequently Asked Questions

Browse answers to common questions about Gizmo’s capabilities, alpha access, supported simulators, and API availability.

Contact Support

Email the Gizmo team directly at viswajit@antimlabs.com for anything not covered here.