Author Topic: Custom SBSAR always crashing substance designer when imported  (Read 907 times)

I tried to decipher what is wrong with this sbsar file which I made but to no avail. All that I found based on randomly disabling the outputs is that it has something to do with the height channel but I do not know what. I think this is a bug because there is nothing special about the nodes that I used. It is worth mentioning also that this sbsar WAS working when I tested it some time ago and now it does not. I am attaching my SBS file

If you could...
Cause it to crash again, and then attach a LOG FILE here.
I'm sure that would be very helpful to the technical team.
Hobbyist
----------
Common "Help" suggestions:
- LOG FILE tips - https://forum.allegorithmic.com/index.php/topic,22451.0.html
- LICENSING issues https://www.allegorithmic.com/contact
- ATTACH files and pictures to posts: https://forum.allegorithmic.com/index.php/topic,23670.0.html

Can you please tell me where can I find that crashlog because every time the SD crashes it just closes without any report or anything really. When I start it again it just tells me to write a description report manually

I looked in the installation folder for a log file but failed to find it. I read somewhere on the web that in SP log is in the install folder

Update: I tried to copy the sbs structure in a new scene, and recreated the controls manually . Still the same result. Maybe if someone else could try to create the SBSAR from this file and try to import it in a new scene just to see if my SD is broken maybe?
Last Edit: April 04, 2018, 03:40:13 pm

See notes in my signature... follow Allegorithmic links... eventually get to a page that gives instructions for that situation.



Or... to make it easy for you... click this:  https://support.allegorithmic.com/documentation/display/SPDOC/Exporting+the+log+file

Or... to make it really convenient... look here:
  • Windows : C:\Users\*username*\AppData\Local\Allegorithmic\Substance Painter\log.txt
Last Edit: April 04, 2018, 03:42:19 pm
Hobbyist
----------
Common "Help" suggestions:
- LOG FILE tips - https://forum.allegorithmic.com/index.php/topic,22451.0.html
- LICENSING issues https://www.allegorithmic.com/contact
- ATTACH files and pictures to posts: https://forum.allegorithmic.com/index.php/topic,23670.0.html

Ok sorry my bad...
here is a log file and a dxdiag

here is dxdiag

Hi Svevlad,

Your problem comes from your tile random nodes.
When you expose a parameter you have to set a variable in it.

There are several parameters that have the same problem.
So set a variable for all of them and it should work.

On a side note, we made changes in Designer 2018 that prevent this type of crashes.
QA Analyst

Well if you added some way to find this type of errors I would definitely try it.  I spent this whole day recreating some of the nodes simply because I was unable to find invalid exposed controls.

Can you please tell me how did you find it in the logs? What should I look for if I have the same problem again? It seems to me that it's a lot simpler to search through text file than it is by clicking on every node SBS

Hi Svevlad,

Unfortunately, you can't see this in the log.
The only way to find which node(s) cause the crash is to make a dichotomous search.
I deleted the half of your graph, then published it and re-imported it in a new graph.
If it crashes, it means the problem is in this part. If not, it's in the other part.
You repeat this until you find the problematic node. It's a bit long but very efficient :)
 
But you shouldn't have this problem if you create your parameters via your nodes.
The input name is automatically created.
QA Analyst