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 4 ... 11
16
Interesting, has the camera changed location in between those two images?

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

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

18
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.

19
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

20
Thank you, that will be very helpful.

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

22
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.

23
There is a stickied post now for 2.2.0. More communications may come later, but it was made clear to us that releasing sooner was more important.

24
For the local render farm, I would run the uninstallers for the 2.1.1 plugin, and then install the new msi package. You can run a silent install of the package using msiexec on powershell, like this:

msiexec /I C:\Path\To\SubstanceIn3dsMax-2.2.0-2020.msi /quiet

Replacing the path with where you have the file located.

After that, if you need to switch to the CPU engine, there is a .ini file located at:

C:\Users\{username}\AppData\Local\Autodesk\3dsMax\2020 - 64bit\ENU\en-US\plugcfg\Substance2.ini

You can change the Engine field to Engine=CPU to alter the settings there.

25
Hello everyone,

We have updated the 3ds Max plugin to version 2.2.0. This version is released for 3ds Max 2018, 2019 and 2020.

There is a big shift in the installation infrastructure for this version. We have switched to an MSI format for the installer, which is different than the previous installer. The cleanest upgrade is to go into the 3ds Max install folders and run the uninstallers for 2.1.1, then installing 2.2.0. Installing over 2.1.1 shouldn't cause issues, although it is less tidy and not recommended.

With the change to an MSI installer, the plugin now has separate installers for each version of 3ds Max that it supports.

2.2.0 Release:
  • Added support for 3ds Max 2020
  • Updated to the Substance Engine V7, adding support for value processors from Designer 2019.1
  • The plugin now loads the Substance engines relative to itself
  • Change to MSI format, proper silent install/uninstall via Microsoft tools
  • Installer and files are now properly signed
  • The installer no longer modifies any files from the original plugin
  • Fixed issue where the menu would not load in 3ds Max 2019 (and 2020)
  • Added native support for the ART renderer
  • Fixed issue with Corona workflow script when there is no glossiness output
  • Workflow scripts are now distributed as plain .ms files, and can be inspected
  • Smaller cosmetic changes and stability improvements

The installer for 3ds Max 2018 is the main one on the Downloads page. As of now, the installers for 3ds Max 2019 and 2020 need to be downloaded from our page for 3ds Max, located here:

https://www.substance3d.com/integrations/substance-in-3ds-max

Cheers,
Galen

26
Hi Mark,

The settings on your local workstation will not affect the render nodes, they contain separate configuration files. I think the settings are stored in a .ini file, I'll have to see where that is saved to tomorrow when I get back to a Windows machine. That can be edited if you can access the machines remotely.

Can you provide more information on your distributed rendering setup? Is it rendering through 3ds Max, or are they rendering with vray standalone?

Thanks,
Galen

27
Those little speckles are called fireflies, they're a rendering artifact that can be common in path tracers. You can fix this in a few ways. First, increase the samples for the render and second, try applying a denoiser of some kind afterwards.

https://docs.chaosgroup.com/display/VRAY3MAX/V-Ray+Denoiser+%7C+VRayDenoiser

Here's the docs on the VRay denoiser, you can see they have similar rendering artifacts in the before/after image.

28
Yes, there are some issues with the current installer. With an MSI, it should be easier to manage using msiexec, I can create some examples when it is released.

They will also be split differently by version instead of a single installer, so the plugin for 3ds Max 2018, 2019 and 2020 will each have different MSI packages.

The current installer system isn't doing what we need it to, so it needed to be changed.

29
I tested in the next version, it looks like updating the Substance Engine will let it render correctly in 3ds Max. This should be released soon, we're finishing up on it.

30
The 2.1.1 plugin does do silent install, but I don't think /SILENT is the right flag. I believe it should be /S or /SD.

We're switching to an MSI format for 2.2.0, which you should be able to install silently using Microsoft's tools for that.

I've not tested it yet, but some of the changes in 2.2.0 may also make it easier to move outside of the current install location. It's at least moving in this direction if still not feasible.

Pages: 1 [2] 3 4 ... 11