• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

New Release: Substance Plugin for Unity v3.9 Now on Asset Store!

Adobe Employee ,
Oct 06, 2023 Oct 06, 2023

Copy link to clipboard

Copied

Hi everyone,
The Unity plugin version 3.9 is now available on the Unity asset store. Please test it out and share your feedback. The plugin can be downloaded here: https://assetstore.unity.com/packages/tools/utilities/substance-3d-for-unity-213208#description


Release notes for v3.9

Updated:

  • Sbsar files can now be dragged and dropped into the project. The .sbsar object can be applied to a mesh as expected in Unity 2022.3.
  • Enhanced documentation for the plugin.

Fixed:

  • Fixed an issue where the Unity plugin was not functional on Android.
  • Addressed naming constraints in the Unity plugin. When a file name contained a ".", the plugin didn't load the file correctly.
  • Fixed an issue where unchecking "Generate all outputs" didn't automatically delete the extra texture.
  • Fixed the incorrect import of SBSAR materials in Unity 2021.3 standard projects. Now, in the standard template project, SBSAR materials can be imported into the assets folder and applied to a 3D mesh without errors.
  • Fixed the incorrect import of SBSAR materials in Unity 2021/2022 HDRP projects. Now, in the HDRP template project, SBSAR materials can be imported into the assets folder and applied to a 3D mesh without errors.
  • Fixed a compilation error when generating the Android build to produce the APK: "Compilation failed; see the compiler error output for details."
  • Fixed an issue causing the build project process to fail with errors on Windows.
  • Fixed an issue causing the build project process to fail with errors on Android: UnityEditor.BuildPlayerWindow+BuildMethodException.
  • Addressed the UnityException encountered when changing SubstanceGraph inputs at runtime. Previously, invoking the SubstanceRuntimeGraph.SetTexturesResolution and the - - SubstanceRuntimeGraph.Render() led the SubstanceGraph to render incorrect results.
  • Corrected a typographical error in SubstanceEditorTools.cs.
TOPICS
Unity

Views

121

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
44m ago 44m ago

Copy link to clipboard

Copied

LATEST

This tool has potential but it is deeply flawed -- the point of being broken.

 

- It generates all textures with read/write enabled. This doubles texture memory consumption by keeping a shadow copy on the CPU.

- It disables texture compression.  That means a DXT5 texture which is normally ~2MB becomes a 32MB texture. If you have multiple texture maps (i.e. albedo, occlusion, etc), that means you are taking a 32MB hit PER texture.

- By making shadow copies and disabling compression, 10MB of texture data becomes 1GB.   If you try to fix the settings, the export process reapplies the above broken settings.  WTF.  This tool is really terrible, and should be avoided until these issues are addressed!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation
Download Latest Versions