Last updated on
Jan 4, 2024
- Home
-
3D Applications
- Maya
- 3ds Max
-
MODO
- MODO overview
- Modo Plugin Release Notes
- Substance in MODO Overview
- Modo Installation
- Parameters
- Custom Materials
- Working with Normals
- Working with Emissive
- Bump and Displacement
- Working with References
- Animating Substances
- Copy/Duplicate Substance
- Environment and Rendering Setup
- Modo Switch Engine
- Tiling Modo textures
- Cinema 4D
- Houdini
-
Blender
- Blender overview
- Release Notes
- Substance in Blender Overview
- Downloading and Installing the Plugin
- Preferences
- The Substance 3D Panel
- Shortcuts and Navigation
- Workflows
- Physical size in Blender
- Substance 3D Assets Library
- Troubleshooting
- Uninstalling the Add-on
- Substance 3D Add-on for Blender Tutorials
- Creative Cloud Applications
-
Renderers
- Converting Substance outputs
- Color Management
- Arnold
- Vray
- Renderman
- Redshift
- Maxwell
- Corona
- Octane
- Keyshot
- Thea
- Maverick
- Toolbag
- Cycles and Eevee
- Partnerships
Upgrading Projects/Known Issues
Alert:
The Substance 3D plugin for Unity 3.0.0 does not support backward compatibility. So, please make sure to use Unity 2020.3.27x and higher.
Unity changed the default build architecture to x86 instead of x86_64.
Scripts will not run if they reference Substances. You will need to change back to x86_64 and the build will work.
Known Issues
- "Assertion failed on expression" error when navigating panel folders.
- This is an error that occurs on the Unity end when changes are made to the UI, usually thumbnail changes, are should be a harmless message.
- This is an error that occurs on the Unity end when changes are made to the UI, usually thumbnail changes, are should be a harmless message.
- Image inputs appear to be locked to 8bits
- This is fixed in version 3.8.0-3. The correct workflow would be for the users to change Unity's default format for the texture to RGBA64. The plugin will take care of properly sending that information to Substance Engine.