expose custom input for normal map and mask

[MarkG2014]

Hello, 

ive created a material which i want to use in external software, Vstitcher (browzwear), all the exposed parameters that i want to work with are working properly except the custom inpute in the graph. 

i am using multi switch node to bring normal maps which i import to the graph in addition i want the user to have an option to bring his own normal map. the same thing i want to have for a mask which gives me the combination of two colors and normal maps in the same material. the input of the custom normal and mask are shown at vstitcher but i dont see any change in the viewport, i do not see the effect when i want to have my custom mask or normal. 

what the problem could be ? i think i tried everything.... please help. 

ive attached some screenshots. 

[MarkG2014]

[Cyril Dellenbach]

Hi @MarkG2014,

Thank you for the message.

So just to be clear, the custom input slot is visible in Vstitcher? Can you show me a screenshot of how Vstitcher displays your .SBSAR parameter?

Let me know.

[MarkG2014]

Hi Cyril,

thank you for your quick reply.

i have attached screenShots from inside vstitcher.

as you can see when i select a mask that i brought from substance designer the mask works. 

but when i select the option of the input - custom and uploaod my new mask it doesnt effect. 

[Cyril Dellenbach]

Hmmm, this could be an issue from Vstitcher plugin... Does the .SBSAR work in other applications? As instance, does it work properly in Substance 3D Painter?

If it doesn't, I advise you to try setting the Input's Output size to Absolute. I suspect the Custom Input to get a low resolution once out of Designer, making it very subbtle once in Vstitcher.

Best regards,

[MarkG2014]

Hi Cyril, 

thank you for your answer, 

i tried what you suggested (i changed the input to absolute) and still it doesnt show the effect that i want in vstitcher...

i opened the sbsar in painter and it is working as expected..

i upload some screenshots from painter  and vstitcher for you to see. 

hope you can help me with that...

thank you,

mark

[Cyril Dellenbach]

Thank you for the details! Considering the custom map is working as it should in Substance Apps, I'm afraid the problem comes from Vstitcher's integration.

I'm gonna move this thread to the "Substance Plugin" community where they might be able to give you a hand, but there are chances you'll need to contact VStitcher directly, so they can solve the problem.

Best regards,

[Shwetha23063442qtvs]

Hi, The Substance plugin in Vsticher is developed by the Brozwear team. We'll share this issue with them. 

[Damien Climent]

@Cyril Dellenbach @Shwetha23063442qtvs @MarkG2014 
Hi Everyone,

This issue is happening because of Substance Engine version mismatch.

The SBSAR was made with Substance Designer leveraging the Substance Engine Version 9 while the file was imported into Vstitcher 2024.1 which is implented with the Substance Engine Version 8.

There is a setting into Substance Designer to create an SBSAR running a previous version of the Substance engine by goint into:

To the Substance Team:
According to the documentation you've shared with us, an engine version mismatch should only cause issues if the user leverages functionality that exists solely in the newer engine version. However, in this case—and in several others we’ve encountered—we haven’t been able to identify any nodes or features that are exclusive to Version 9.

Hope this answer will help.

Best,

Damien Climent (Former Substance Angel that turned into Substance Demon)

[Shwetha23063442qtvs]

Thanks for the heads up, @Damien Climent! We'll check if there is a way we can add backward compatbility, but regardless we'll need the users to use the latest version of Desginer.