Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - keston

Pages: 1 2 [3] 4 5 ... 15
With the known issues, what does this actually mean? "Substance materials are not persistent when exported/imported using a Unity package".

If I create a Unity Package and include substance graphs with multiple instances, are those OK, or is it just the property values that are not persistent?

@stefan Sorry for the confusion. This should read "Substance material properties are not persistent when exported/imported using a Unity package". This means that the tiling/rendering modes etc. will be set back to default when imported while contained in a Unity package.

Hey I just tested this out.  So far no errors but there is still an issue with tiling settings not being detected and thus I cant figure out how to check in a material with tiling into source control.  So basically tiling changes are not carrying over across machines etc.

Repo steps:  Using a project under source control check everything in  so git report nothing to commit.  Then make changes to the tiling of the material under the sbsar file in unity inspector.  Git shows no changes.

I reported this issue awhile ago here,23756.msg102417.html#msg102417

Substance plugin 2.2.0 on unity 2018.3

@jaran ,

Sorry for the late reply. There is a bug here with Unity + Substance 2.2 plugin + Git. I have put in a ticket for this. Thank you for reporting it and sorry for the inconvenience it causes.  :-\


Just import package "Substance in Unity" then import any .sbsar file

@j_a_c_k_o_3 These errors appeared in 2.1.1, but should be fixed in 2.2. Can you verify that you have an About button in the Substance menu at the top? If not, then the package is still 2.1.1, because this was added in 2.2.

Sometimes the Unity asset store keeps an old package around, just checking to make sure.

Anyone get these errors in Unity official release  2018.3.1f1?

Just import package then import .sbsar file from SD 2018.1.2

What version of Unity are you using? How are you able to reproduce this issue?


The plugin doesn't seem to be loading fully for me here. I haven't touched any of the plugin folders. Is there another step I'm missing to get this working? Thanks!

How were you able to reproduce this issue?

Glad to have the plugin back in my 2018.3 project.

Don't know if this is the place to report bugs, but every time I exit play mode, a null reference exception appears in the console:
Code: [Select]
NullReferenceException: Object reference not set to an instance of an object
Substance.Game.NativeCallbacks.DisableScripts () (at <4d83584dfe7c4e0d9d1b5ec79410fc6c>:0)
Substance.Editor.EntryPoint.StateChange (UnityEditor.PlayModeStateChange state) (at <ea810960b57e457690325c90558fa06d>:0)
UnityEditor.EditorApplication.Internal_PlayModeStateChanged (UnityEditor.PlayModeStateChange state) (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:302)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) (at ?)

Also, I would really like to be able to put the plugin in a folder besides the root Assets directory. It's a bit frustrating when you've got an organizational system to keep directory clutter to a minimum and then a plugin demands that it must sit at the root directory :/


Hey @me_41 ,

How are you able to reproduce this issue? I might need you to send me a project where this occurs, because I cannot reproduce it.

Also, I understand your frustration of the plugin location. I'll have a talk with the dev team today about this issue.

I have just tried this and I'm not sure that I have the latest version of the plugin. I have imported the plugin and a sbsar file and have found that the instance is still name mat. and I can't see anyway of renaming an instance.

I have cleared my asset store app data folder and re downloaded the plugin.
The plugin folder's engine_build_info.txt has Plugin commit: 3684 and Plugin Build : 790

Is there an easy way to check the version of the plugin?

@kelly4d3d ,

Yes that seems to be the old version of the plugin. The 2.2 release has an About option in the Substance menu that tells you everything about the plugin version. Unity's Asset Store is a bit weird sometimes. Were you given the option to Update the plugin in the Asset Store? What version of Unity are you using?

Since the SHOPs context is obsolete, it would be helpful if the Houdini plugin could be updated to suit the MAT context and H17.0 as a whole.

I understand if this is low priority, but any work on bringing this plugin up to date is greatly appreciated.

We are currently in the process of updating the Houdini plugin :) However, unfortunately I cannot give a time frame.

oh , i forgot about that  ;D

Talking with the UE4 dev, this is apparently a known issue with our GPU engine. We are currently in the process of fixing this. Sorry for the inconvenience.  :(

Yes , thank you for your reply.

Hey @thanhtoan_ptt ,

It seems some dependencies are missing with the sbs file. Would you be able to provide those as well? You can do this by right clicking on the sbs in Designer and clicking 'Export with Dependencies'.

Hey guys, i 've got this problem when trying import sbsar file into UE4 .

The basecolor look like this in Substance Designer :

and in UE4 :

This is the Substance's setting i use in UE4 :

SD's graph size is Parent x 1 . I tried to change the Substance Engine in UE4 to CPU , it looks better but still wrong on some informations like missing small stones , incorrect color variation for big stones ...

Would you be able to send the sbs file to us so we can take a look?  :)


We're a UE4 licensee and build it directly from source, so we don't use the Epic Games Launcher to get our version of the engine. However, it seems to get the latest Substance, we must always first download a matching engine in the Launcher, and then download the plugin from the marketplace.

Would you be able/willing to make the plugin available for direct download so that we can integrate it directly into our engine source, bypassing Epic Games Launcher? This is how most third party plugins work (e.g. Wwise, Houdini, etc.).


What version of UE4 are you using? The latest 4.21 release is available for direct download here: . Alternatively, 4.19 and 4.20 are available for direct download from their sticky threads here at the top of the forum.

Hey @Mostafa Nabil 0  and @tm_akman ,

The crash that occurs when opening Substance Source has been resolved. Let us know if you have any other issues. :)

Pages: 1 2 [3] 4 5 ... 15