3dsmax, Deadline as Svc, Plugins & Windows 11 > plugin not rendering

Beeldenfabriek · August 23, 2024, 6:23am

So i have a freshly installed Windows 11 machine, Installed max 2023, Installed deadline as service, copied some plugins into the install (e.g. floorgenerator) and it renders fine when I open max and use it.

But when I submit a job to the farm, floorgenerator objects aren’t rendering. The same actually goes for Anima which is actually installed.

Forestpack & Railclone on the other hand are rendering fine.

What am I missing here ?

Derek_E_Zavada · August 23, 2024, 6:29pm

Would it be possible for you to send the output log from the render node? This would probably help determine what is going on.

Beeldenfabriek · August 26, 2024, 6:50am

Ok, so your mention of the tasklog made me look a but closer (was looking for errors earlier, which there are none).
But upon closer inspection, I noticed these line in the tasklog:

2024-08-23 07:37:45: 0: INFO: Using user profiles: 1
2024-08-23 07:37:45: 0: INFO: 3dsmax user profile path: C:\Users\renderuseraccountname\AppData\Local\Autodesk\3dsMax\2023 - 64bit\ENU
2024-08-23 07:37:45: 0: INFO: 3dsmax plugcfg directory: C:\Users\renderuseraccountname\AppData\Local\Autodesk\3dsMax\2023 - 64bit\ENU\en-US\plugcfg
2024-08-23 07:37:45: 0: INFO: 3dsmax network directory: C:\Users\renderuseraccountname\AppData\Local\Autodesk\3dsMax\2023 - 64bit\ENU\Network
2024-08-23 07:37:45: 0: INFO: 3dsmax usermacros directory: C:\Users\renderuseraccountname\AppData\Local\Autodesk\3dsMax\2023 - 64bit\ENU\usermacros
2024-08-23 07:37:45: 0: INFO: Scripts Startup Directory: C:\Users\renderuseraccountname\AppData\Local\Autodesk\3dsMax\2023 - 64bit\ENU\scripts\startup

Which made me look there and noticing that on the nodes that were rendering properly, there was a file called Plugin.UserSettings.ini within which was this text:

[Directories]
Additional MAX plug-ins=C:\Program Files\Autodesk\3ds Max 2023\PlugIns
[Help]

So I figured I’d copy that ini file to the same directory on the faulty node and that solved the problem.
I’m just not entirely sure why that file did get created on the working node and not on the faulty node(s). Unless it’s a windows 11 thing (which both of the faulty nodes are).