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 - mark.fonzen@kohler.com

Pages: [1]
1
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.

The install created an .ini file for Substance2 on my workstation, but on the render node there is only a substance.ini in that location.

Did something not install correctly?

I copied the Substance2.ini file on my workstation and pasted into the plugincfg on my render node, and everything is working properly! Thank you for your help!

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

The install created an .ini file for Substance2 on my workstation, but on the render node there is only a substance.ini in that location.

Did something not install correctly?

3
If we have a local render farm that has a couple render slaves with limited GPU capability, what setup type should be used to install?

4
Hi Galen,

Thanks for your reply!

We are rendering through 3ds Max/Backburner. We have a local set up that uses 4 workstation PCs, and 2 render nodes. We can access any of the files on these machines, but the nodes cannot open 3ds Max directly. We dedicate a single workstation to be the manager and server that receives jobs and stores them in the backburner queue. When a job is started with distributed rendering ticked on, it connects to all PCs/Nodes that have their Distributed Rendering Spawner turned on. These DR hosts don't launch 3ds Max directly, but provided extra cores to process the job.

Here are the configuration settings taken from the Enu folder of a node and a workstation
https://kohlerftp.kohlerco.com/main.html?download&weblink=c375697e7b1526ca3675bb1319ea2f51&realfilename=3ds$20Max$20Settings.zip


When the job starts, a V-Ray Frame buffer launches, the scene data is transferred to the DR Hosts, and DR Hosts begin processing the job along with the server that launches it. DR Hosts can connect to any licensed machine that is starting a job on our network using DR, so this issue isn't exclusive to a backburner submission.

I apologize if you already know how DR works, but I just want to tick all the boxes. I think it's important to reiterate that there is no bucket issues when another Workstation connects as a DR Host.  The problem occurs when a render node connects as a DR Host. These nodes have powerful CPUs and the same software/plugins/licensing that the workstations do, but do not have GPUs that are capable of DirectX Features.

Is there any other information I can provide to help?


5
I need help solving a problem that I'm sure many people have encountered when using distributed rendering with server nodes.

Basically, when I use distributed rendering, the buckets from the workstation CPUs read and render a substance2 material perfectly fine, but buckets from the render NODES resolve black. I don't get any errors in my dialogue about the plugin, so I'm thinking it's some kind of GPU issue.

I have two render pros from BOXX that are running ATS2400 onboard video graphics cards. Each machine is running  3ds Max 2019, V-Ray Next, and has the Substance Plugin successfully installed; however, I cannot open 3ds Max on these machines to change the Substance Settings from GPU to CPU. I changed the substance settings on my workstation to CPU to see if that would fix it, but the nodes still have their bucket issues.

Could someone shed some light on what is causing this problem and provide a solution? Is it a GPU issue? Is there a way to change the substance settings on these render nodes without opening 3ds Max?
 

Pages: [1]