nice! thank you!
will the oficial release take long still?
because deadline support more than just 3dsMAXâŚ
Deadline itself, AWS machine bridge, Draft, then add the narly 100 package supported out of the box, plus options, plus specificities for some software (DBR, scene state, batch mode, jigsaw , etcâŚjust for 3dsMAX, image adding maya, houdini, nuke( ââ âxâ âstudioâ âserverâ), etc etcâŚand the multiple version retro compatibily, updates on softwares that require code check and recompile, and test, etc etcâŚ
Thatâs whyâŚ
But honestly iâm ok with a quicker update, with the âpatchâ post on forum soonerâŚat least, this is an updateâŚ
I was aksing when, not why 
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.
well waiting for the official release meanwhile.
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
RenderPluginException
=======================================================
Stack Trace
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 send a ticket about this with the full logâŚ
1 Like
Canât remember the details, but there was a function to ignore dialogs, by dialog title/name.
So it is a matter of adding this ignore somewhere.
1 Like
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
2022-06-16 12:33:09: 0: INFO: Ignoring popup "MAXScript Debugger"
2022-06-16 12:33:09: 0: WARNING: Detected popup dialog "Scripting Listener".
2022-06-16 12:33:09: 0: WARNING: ---- dump of dialog ----
2022-06-16 12:33:09: 0: WARNING: Static:
2022-06-16 12:33:09: 0: WARNING: Button: MAXScript
2022-06-16 12:33:09: 0: WARNING: Button: Python
2022-06-16 12:33:09: 0: WARNING: MXS_Scintilla:
2022-06-16 12:33:09: 0: WARNING: MXS_Scintilla:
2022-06-16 12:33:09: 0: WARNING: ---- end dump of dialog ----
2022-06-16 12:33:09: 0: Done executing plugin command of type 'Start Job'
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."). "
Max2023 Support : 3ds Max 2023 Support - #16 by Qail_Mukhi
Edit for 2023.1 support (overwrite the py file with this one): (/plugins/3dsmax/3dsmax.py )
3dsmax.py (199.1 KB)
Both require 10.1.24
Thanks Thinkbox Team
2 Likes
Finally the 2023 support is here!
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)
2022-06-29 22:33:12: 0: INFO: Ignoring popup âMAXScript Debuggerâ
2022-06-29 22:33:12: 0: WARNING: Detected popup dialog âScripting Listenerâ.
2022-06-29 22:33:12: 0: WARNING: ---- dump of dialog ----
2022-06-29 22:33:12: 0: WARNING: Static:
2022-06-29 22:33:12: 0: WARNING: Button: MAXScript
2022-06-29 22:33:12: 0: WARNING: Button: Python
2022-06-29 22:33:12: 0: WARNING: MXS_Scintilla:
2022-06-29 22:33:12: 0: WARNING: MXS_Scintilla:
2022-06-29 22:33:12: 0: WARNING: ---- end dump of dialog ----
2022-06-29 22:33:12: 0: Done executing plugin command of type âStart Jobâ
Got reply from the support.
Adding to the 3dsmax.py file the following ignore command fixed it.
# For Scripting Listener
self.AddPopupIgnorer( "Scripting Listener" )
be carefull with spaces vs TAB⌠seems deadline didnât like tabs at front
2 Likes
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.
After installing release 10.1.22.5 Itâs working for me. Thanks Ignacio. The file is here if your search it: â\DeadlineRepo\plugins\3dsmax\3dsmax.pyâ
I copied the 3dsmax.py script into the folder and still running into this issue with Vray 6 and Max 2023. Any thoughts?
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.
@kauffman @SIDNEY_T_C_JUNIOR do you still have the problem with the pop up handler unchecked?
I can render with 2023.1 and V-Ray 6 with this unchecked
Still getting errors.
This seems to have worked for me. Thanks!
1 Like
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.
Is there a surefire solution to this problem?