If you receive error 205, try logging out of the Creative Cloud app and logging in again before launching Modeler.
- Substance 3D home
- Home
- Getting started
- Interface
- Create with Clay
- Create with Primitives
- Get started with primitives
- Primitive parameters
- Organize primitives
- Organize your scene
- Render mode
- Export Mode
- Technical support
- Release notes
- V1.15 (Current Release)
- V1.14
- V1.13
- Public Beta V1.16.50 (Current Release)
- Public Beta Archive
- V1 Archive
- V0 Archive
Troubleshooting
General troubleshooting
If you are encountering issues, try the following steps:
- Restart Modeler - this can help clear temporary issues.
- Restart your machine - this can help solve problems with Modeler starting or with configuration issues.
- 🥽 Try resetting the connection to your VR headset. Use the Reset button at the top right of the Modeler window.
- 🥽 Check that your OpenXR runtime is configured correctly. This is covered in the OpenXR section below.
Access Modeler's log files
Log files hold diagnostic information about your Modeler session, such as the order of actions you have taken, error and warning messages, and crash information. The log file is helpful for Modeler developers to understand the cause of errors and crashes, and the log file is automatically included when you submit an error report.
If you're encountering a recurring issue, you can use our Community channels to contact the Modeler team. We recommend submitting your log files when you report an issue in community channels for a faster response.
You can find Modeler's log files in your documents folder:
C:\Users\<your username>\Documents\Adobe\Adobe Substance 3D Modeler\Logs
A collection of logs are stored from previous sessions. Logs from the Beta version of Modeler have _Beta appended to the end of their name.
OpenXR configuration
Modeler uses OpenXR, and currently supports SteamVR or the Oculus app OpenXR runtimes. If you have both SteamVR and the Oculus app installed on your machine, you may need to change the default OpenXR runtime based on your headset. If Modeler doesn't enter VR mode when you put on your headset, it may be because your OpenXR runtime isn't set up correctly.
In general, if you are using an Oculus headset, you should use the Oculus app as the default OpenXR runtime. If you are using a non-Oculus headset, you should use SteamVR as the default OpenXR runtime.
While Modeler doesn't support other OpenXR runtimes currently, the SteamVR runtime can sometimes work for headsets that usually require a different OpenXR runtime.
To set Oculus as the default OpenXR runtime:
- Open the Oculus app.
- Navigate to Settings > General.
- Next to "OpenXR Runtime" click "Set Oculus as active".
To set SteamVR as the default OpenXR runtime:
- Launch SteamVR.
- In the SteamVR status window, click the menu button in the top left.
- Select Settings from the dropdown that appears.
- In the Settings window, toggle Advanced Settings to "Show".
- Select the Developer tab from the list on the left.
- This menu will show the current OpenXR runtime. Click "Set SteamVR as OpenXR runtime" to update the runtime.
Known bugs
We do not officially support Revive. If you are using Modeler with Revive, you are likely to experience more bugs and performance issues. Only bugs that have been reported without Revive are listed on this page.
This page lists known issues and their workarounds if available.
-
-
Using Modeler on another computer through Remote Desktop can result in odd behavior. For best results use Modeler on your local machine.
-
Sometimes Modeler will use the integrated GPU rather than the discrete GPU and refuse to start as a result.
- To fix this issue, install or reinstall the drivers for the integrated GPU, this helps Modeler to recognize both the integrated and discrete GPU and pick the correct one.