Skip to main content
S
Community Manager
Shwetha23063442qtvsCommunity Manager
Community Manager
October 6, 2023
Question

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

  • October 6, 2023
  • 2 replies
  • 687 views

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.
This topic has been closed for replies.

2 replies

chromatic1
chromatic1
Participant
June 25, 2024

Hi @Shwetha23063442qtvs,

 

Are you aware that the Substance plugin causes a multisecond wait every time editor playback begins?  i..e it causes a 4 second delay after the Unity Editor play button is clicked.  Is there a way to disable the Substance editor runtime?  I'm trying to avoid this performance hit every time I hit play -- which is over a hundred times a day during development.  Right now, my only solution is to delete the Substance plugin from the project and re-add it later when I need to generate from an SBAR.

 

chromatic1
chromatic1
Participant
May 26, 2024

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!

A
Adobe Employee
Aldo_3D
Adobe Employee
May 29, 2024

Hi @chromatic1  thanks for the feedback, we're looking into the texture comperssion for generated maps and are hoping to get that into a later version, which should help with the memory issues. Stay tuned for Updates.

- Aldo

chromatic1
chromatic1
Participant
May 29, 2024

I appreciate your response. It should be noted that anyone that actually uses this tool will wreck their game by using uncompressed 4K textures with read/write enabled.  It's as bad as a virus. The tool is completely unusable in its current form.   If it didn't reset settings it would be usable -- but it reverts back to these broken settings.  

 

What it SHOULD do is use default compression settings for the chosen platform and not enable read/write.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices