Troubleshooting

Fix the problems people run into most often with Meshy DCC Core.

Common problems

The following table lists common problems and how to fix them.

Problem	Fix
`meshy-dcc: command not found`	Open a new terminal. If it still fails, add `~/.local/bin` to your `PATH`.
My app doesn't appear under Connected now	Check that its connector is installed. For Unity, Godot, Unreal Engine, and other per-project apps, check that it's installed in this project. Then restart the app. It appears within a few seconds of starting.
The Blender install asks where Blender is	Blender isn't in its usual place, or there is more than one copy. Enter the full path of the Blender app you use.
The Unity install fails	Install the Unity Editor version that the project's `ProjectSettings/ProjectVersion.txt` names, close the project, and try again.
The Unreal Engine install fails while building	Install Xcode on macOS, or Visual Studio 2022 with Game development with C++ on Windows. On macOS, the Xcode version must be one your engine accepts.
My agent doesn't know Meshy DCC	In the window, go to Agents, turn on your agent, and start a new chat.
The window says it can't reach the service	Run `meshy-dcc ui` again. The service stops by itself when no app has been open for a while.
The agent asks which app or project to use	More than one open app fits the request. Name the app, scene, or project.
Windows warns about an unknown app	The Windows files aren't signed. Choose More info > Run anyway only if you installed from `cdn.meshy.ai`.
Windows blocks the app and offers no way to run it	Smart App Control blocks unsigned apps and can't make an exception for one. Use Meshy DCC Core on a PC where Smart App Control is off.

Check your setup

To check your setup, run:

meshy-dcc doctor

The command checks the installed files, the local service, and the apps that have registered. It doesn't change anything.

Report a problem

To report a problem, follow these steps:

In the window, go to Settings > Report a problem.
Describe what you asked your agent to do and what happened, then click Preview. The window shows the exact report. It holds your description, the versions and your operating system, a diagnostic summary without paths or IDs, and your agent's recent error reports.
Click Send. Meshy DCC Core sends nothing until you click Send. Meshy turns the report into a public issue in the meshy-dcc-core repository on GitHub, so leave private details out of your description.

From a terminal, run meshy-dcc report --summary "what happened" to see the same preview, and add --yes to send it. Your agent can do the same. It asks you before it sends anything.

To report without the form, open an issue in the repository or email support@meshy.ai. Paste the output of meshy-dcc doctor, with anything private removed, such as folder names. To see recent failures, slow requests, and problem logs on your computer, click Open the Debug Workbench in Report a problem.

Uninstall Meshy DCC Core

You can ask your agent to uninstall Meshy DCC Core. To do it yourself, follow these steps:

Remove the connectors you installed. See Uninstall a connector.

Remove the skill from your agents:

meshy-dcc agent-skill --remove --execute

Delete meshy-dcc and meshy-dcc-server from ~/.local/bin. If you installed with npm, run npm uninstall -g meshy-dcc instead.
Optional: delete the ~/.meshy-dcc folder. It holds your settings and your custom skills, so keep a copy of any skills you want.