If you have not changed the job type it will keep on using same plugin it copied. So you might have changed the plugin in the Repo the Worker cache needs to updated.
To do that the easiest way to test is to re-load plugin between the tasks. It is not recommended for rendering because it takes more time to render (loading and unloading plugin on every task ). So for any job you are trying to test> right click it> Modify Job Properties> General> Re-load plugin between tasks. Then retry, if it still fails, check if you have got a copy of plugin in the [repo]/custom/plugins/3dsMax/, if you have this plugin will used rather than the one in the default folder. So you will need to make changes to that plugin. If it still fails attach the copy of 3dsmax.py you have got in [repo]/custom/plugins/3dsMax/ or if you do not have it in custom get from [repo]/plugins/3dsMax/
Hi,
thereās no custom plug-in for 3ds Max, everything is done with the standard .py file
In the meantime, I updated 3ds Max to 2023.2, with the same results. Updating Deadline requires going through some internal company loops, and Iāll test that when I can.
Out of curiosity, I created a simple scene with a cube and a light (no maps, no external references) and that did render via Deadline.
However, the moment I add a texture or an external reference (I work with XRefs a lot), problems start.
Iāve done some testing, and here are the results, logs and .py file. All have been done with the āReload plugin between tasksā checked. All tests were done with Max 2023.2, Deadline 10.1.22.5, and a scene I would normally work with.
āPluginModā indicates I used the popupignorer line found earlier in the thread, Popuphandling Enabled/Disabled is for the option @anthonygelatka suggested.
I checked the log and 3dsMax.py plugin file you have attached. In the attachment " PluginMod_PopuphandlingEnabled.zip (41.5 KB)" the job report does not seem like the job is failing on āScripting Listenerā popup. This is some other issue with Max file not being able to load.
In this case I think you should open the scene on the render node and try rendering with in Max. Do you see any errors?
The popup handling is supposed to be on and the plugin should be modified to ignore Scripting Listener.
I have a silly question about āDā is it a Network Drive?
the scene loads fine in 3ds Max and D:\ is a local drive. Due to IT policies I cannot have all the scene data on a single network drive accessed by all computers, but I have to copy scene data on all rednering machines. It has worked well since I started using Deadline some three years ago.
About the āfail to loadā error, I think it might be related to 3ds Max 2023. I am encountering a lot of problems trying to load big scenes using a lot of XRefs, though the scene I used for the examples above always loads without a hitch in 3ds Max 2023.
As mentioned in my previous post, scenes load fine as long they donāt use XRefs. If I add even a single external reference, and that reference has a cube with no materials or maps applied, the scene fails to load.
I have opened a thread in Autodeskās forums detailing the problem but so far no luck in getting a reply.
Iām trying to reproduce this issue myself, we need to test why the popup appears. Is it becuase of our code or 3dsMax itself. I have not been able to reproduce the issue. When you get a chance can you attach a test scene here.
thanks for the support.
Iām now 90% sure itās 3ds Max 2023ās fault. I created a test project and made it similar to other projects Iād normally work on in directory structure, MXP project file, Deadline presets, etc.
The test scene I rendered (found in 0-test\assets) works fine in both 3ds Max and Deadline.
Happiness.
Changed to a ārealā project, and the problems persist. Scene renders fine in 3ds Max 2023, but launching from Deadline returns to the same āfailed to loadā or the mysterious pop-up.
So, Iād say itās 3ds Max 2023 handling large XRefs incorrectly.
Unfortunately still no reply from Autodesk support on the matter (3ds Max 2023 crashes with XRefs - Autodesk Community)
I tried rendering with 3dsCmd but I always get the same error in all projects, no matter the configuration.
I am having the same problem with rendering Max2023.2.2 scene in Deadline 10.1.23.6.
Error: FailRenderException : 3dsmax startup: Error getting connection from 3dsmax: Dialog popup detected: Title āScripting Listenerā, Message "MAXScript "
I tried updated 3dsmax.py file. It helps only for simple scenes. But scenes with any plugins still generate errors in Deadline.
I have figured out that this is V-Ray 6 causing such errors. It looks like current version of Deadline cannot handle V-Ray 6. I had 3ds Max 2022 with V-Ray 5.20 working fine. But after installing V-Ray 6, render farm stopped working, causing errors, similar what I had with 3ds Max 2023 and V-Ray 6. I had to roll back to V-Ray 5.20 and wait when Deadline will be tweaked to work correct with V-Ray 6.
Hey guys
I just recently have been getting this error as well. One of my artists updated 3dsmax 2023 to a newer version than what is on our farm.
His version was:
2023.2
The farm version is:
2023.1
This caused a chamfer plugin version issue pop up.
I proceeded to update one farm node to the latest version:
2023.2.2
This is where I began to see the errors. I will probably have my artist revert and also revert the node to version 2023.1 as a temp fix.
Would like to see if there is a better fix incorporating the latest version of 2023 moving forward.
Currently on Deadline version:
10.1.23.6 Release
Hope this helps
cheers~