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 - Galen Helfter

Pages: [1] 2 3 ... 11
1
I'm not certain on this one, I haven't seen that before.

I'll see if I can reproduce it.

2
It looks like a unicode issue of some kind. I can try to reproduce it.

3
Which version of the plugin are you using?

The old plugin is very UI driven and may have issues rendering. The GPU engine may also need an X11 session to acquire an OpenGL context.

Best,
Galen

4
If many people are asking for a version for Maya 2017, then I think we should consider it for a future release.

5
This is a known limitation currently. We're evaluatin how we may be able to remove this limitation in the future.

6
I apologize for the delay.

The plugin currently shipped with Maya 2019.1 is the 1.4.1 version.

The plugin allows you to use sbsar files within Maya. To do this, you create the node called Substance in the hypershade, and use the filepath field to locate and load an sbsar file. You can locate sbsars from wherever this way.

In the 2.0.0 plugin, you will be able to drag and drop sbsars into the hypershade to make this easier. There will also be options in the shelf and menu to load and create materials.

Sbsar files are usually created as the output from Substance Designer or Substance Alchemist. The next release of the plugin will also have utilities to make loading the maps created from Substance Painter easier.

The documentation for the 1.4.1 plugin can be found here:
https://docs.substance3d.com/integrations/maya-legacy-149291349.html

Cheers,
Galen

7
Hi trist,

We have some ideas for this and we're evaluating then currently. I don't have any further details right now.

Cheers,
Galen

8
I can take a look and see what happens when doing that. If this causes an issue, then we will have to fix it. I'd recommend trying with backburner instead.

We'll want to see what we can do on our end to work with more convenient systems, such as deadline.

9
Interesting, has the camera changed location in between those two images?

It almost looks like some sort of odd sampling or aliasing issue.

10
There's an insert image button in the forum post if you can post screenshots here.

11
The new version should work distributed with Backburner for Corona. It was one of the ones we tested with for the 2.1.1 release. We're looking at ensuring it works with other systems later that may be more convenient to use.

12
Hi,

To me, it looks like the Attribute Editor code for the plugin has crashed in some manner. I don't know exactly what will have caused this. In your screenshots, it looks like the outputs have been rendered, but the interface is completely inaccessible.

To fix some of these issues, we're finishing up the 2.0.0 release of the plugin. Because of this, the 1.4.1 release will be the final version of that plugin before it is retired. We have a discord channel for the 2.0.0 beta that you can find the link to on our website here:

https://docs.substance3d.com/integrations/maya-172825672.html

We can give you access to that plugin if you ping either Wes or I on the Discord.

Cheers,
Galen

13
Thank you, that will be very helpful.

14
Are you exporting an fbx with a material using Substance applied to it?

15
Did you go into the render settings for Arnold and enable legacy 3ds Max maps? Arnold will only read the outputs if that is set.

Pages: [1] 2 3 ... 11