I proceeded to install the “fix” and couldn’t make it work for me.
The render submitts but It will crash on every machine on the farm giving an error " sorry I don’t remeber what error was but something about Unicode… blabla " crashed every single version of Max not only 2023
I replaced the files that are in the zipfile.
Also the installer attached installs only for 2022? should we force it to install on 2023 when it promps about it?
I could reverse the files to the backup version and then everything worked again, not Max 2023 of course.
Will not work with 2023.1 update…(2023(.0)) is ok for MXS job and rendering job(what i use)…
But with 2023.1 we got some error, after 3dsMAX 2023.1 init itself.
Error: FailRenderException : 3dsmax startup: Error getting connection from 3dsmax: Dialog popup detected: Title “Scripting Listener”, Message "MAXScript "
…
at Deadline.Plugins.DeadlinePlugin.FailRender(String message) (Python.Runtime.PythonException)
File “C:\ProgramData\Thinkbox\Deadline10\workers\ICEBERG\plugins\62aac470c6f696c38029ba2c\3dsmax.py”, line 170, in StartJob
self.MyMaxController.StartMax()
File “C:\ProgramData\Thinkbox\Deadline10\workers\ICEBERG\plugins\62aac470c6f696c38029ba2c\3dsmax.py”, line 1277, in StartMax
self.WaitForConnection(“3dsmax startup”)
File “C:\ProgramData\Thinkbox\Deadline10\workers\ICEBERG\plugins\62aac470c6f696c38029ba2c\3dsmax.py”, line 2190, in WaitForConnection
errorMessageOperation, e.Message, self.NetworkLogGet()))
at Python.Runtime.Dispatcher.Dispatch(ArrayList args)
at __FranticX_GenericDelegate0Dispatcher.Invoke()
at Deadline.Plugins.DeadlinePlugin.StartJob()
at Deadline.Plugins.DeadlinePlugin.DoStartJob()
at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)
at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)
=======================================================
Type
at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgj, CancellationToken bgk)
at Deadline.Plugins.SandboxedPlugin.StartJob(Job job, CancellationToken cancellationToken)
at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajq, CancellationToken ajr)
I just updated and checked this and the render failed (simple teapot in scanline)
Deadline Client Version: 10.1.21.4 Release (690edd3fe)
FranticX Client Version: 2.4.0.0 Release (14916bbc6)
Repository Version: 10.1.21.4 (690edd3fe)
Integration Version: 10.1.21.4 (690edd3fe)
Have the custom bits from above but the job failed when submit to Deadline
In the submitter under the ‘Scripts’ tab there is this
When I unchecked Popup Handline it went through, not sure if this is the same issue you are having but I think this is what @mois.moshev is referring too.
Yeah this is the feature I’m writing about, but you might have to hack the plugin to add more dialogs to ignore. (Actually not sure how it works, haven’t looked at it in a while)
Here is the fix from Official support (via ticket):
"You’re getting a popup that’s not handled by any of the popuphandlers in the 3dsmax.py file. We don’t support Max 2023 yet, so I don’t have a machine to test with but adding your own handler is pretty straightforward.
In the DeadlineRepository10/plugins/3dsmax/3dsmax.py file around line 3163 add self.AddPopupIgnorer(".Scripting Listener."). "
I updated everything, and tested, in 2021 worked fine.
but in 2023 I’m getting this error.
I cropped the parts where the errors appear.
Error: FailRenderException : 3dsmax startup: Error getting connection from 3dsmax: Dialog popup detected: Title “Scripting Listener”, Message "MAXScript "
at Deadline.Plugins.DeadlinePlugin.FailRender(String message) (Python.Runtime.PythonException)
File “C:\ProgramData\Thinkbox\Deadline10\workers\pcname001\plugins\62bc547b03c334803c4be3a2\3dsmax.py”, line 170, in StartJob
self.MyMaxController.StartMax()
File “C:\ProgramData\Thinkbox\Deadline10\workers\pcname001\plugins\62bc547b03c334803c4be3a2\3dsmax.py”, line 1277, in StartMax
self.WaitForConnection(“3dsmax startup”)
File “C:\ProgramData\Thinkbox\Deadline10\workers\pcname001\plugins\62bc547b03c334803c4be3a2\3dsmax.py”, line 2190, in WaitForConnection
errorMessageOperation, e.Message, self.NetworkLogGet()))
at Python.Runtime.Dispatcher.Dispatch(ArrayList args)
at __FranticX_GenericDelegate0Dispatcher.Invoke()
at Deadline.Plugins.DeadlinePlugin.StartJob()
at Deadline.Plugins.DeadlinePlugin.DoStartJob()
at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)
at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)
I suppose you saved your scene with the scripting listener opened, and that is why it popped up on open? If you close it and save it might not be an issue. But yeah the dialog should be ignored anyway.
Im having still issues with Max2023 and Deadline… I was able to make it work using the patched 3dsmax.py file.
However only on some scenes, but on complex scenes it seems is way more prone to crashes… same file will render fine on deadline from max 2019 and max 2021, but from max 2023 will crash…
in one scene that was crashing on deadline i tried to narrow down the crash by merging parts of the scene and rendering, and at the end it seems the problem was a material that had a jpg map on a slot, but the jpg file was not available… once i remove the jpg from the material slot it rendered fine… but this took several hours to track down, and using max 2019 this would be ignored and the scene will still render just wont use any map since it would not be found…
Has anyone experience similar issues, or anyone using it in production without any issues?
I am having the same issue here, running 2023.1 and V-Ray 6.0008. I tested the same basic teapot laden scene in 2021 and 2022 with no issues. I supposed I could test V-Ray 5 and see what comes up with 3dsMax 2023.
Any news about that?
Still can´t render in MAx 2023.
I saw a post saying to use Deadline 10.1.24, but I can´t find this download.
Still using 10.1.23.6
I can say one thing, never more I will update this before at least 8 to 10 months of the release. Autodesk has been rolling this out yearly, always full of bugs.
Since we have a team and already worked on a lot of files, it will be really hard to roll back now.
I’m encountering the same problem. 3ds Max 2023.1 (25.1.0.2342) plus V-Ray 6; Deadline is 10.1.22.5.
Submitting a job with Popup Handling checked results in Dialog popup detected: Title “Scripting Listener”, Message "MAXScript "
Submitting a job with Popup Handling uncheck results in Failed to load max file
Modifying the 3dsmax.py file or using the verison attached to this thread result in the same failed to load error.
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.
