Error: RenderTask: Unexpected exception - Octane Render 2023.1 - 1403

Deadline
1

Hi I’m getting the next error log only when I used the new Octane Render 2023.1. I hope it helps and you can help me to get this solved as soon as possible:

> Error: RenderTask: Unexpected exception (Exception caught in 3ds max: – Syntax error: at …, expected

2

Without more of the task report it’s impossible to say what’s going wrong. It looks like there’s an issue in a maxscript you’re using, so maybe remove anything you’ve recently added to the pipeline as a test?

To see if the issue is caused by Deadline, check out this guide on isolating the render from Deadline.

3

Hi @Justin_B, I’m attaching the log from deadline. Sorry for the late reply on this, I was in hurry with many projects and I just revert to previous Octane Render version that worked fine to submit to Deadline. I hope hear news soon!

Kind regards…

deadline_log.zip (5.5 KB)

4

Here I’m attaching another log using 3ds max 2024 and the latest version of the plugin of Octane Render 2023.1.2 - 1409 and as the previous one, I’m unable to get things done successfully!

Job_2024-02-24_20-38-32_65daa8295436f5ee6e76ba25.zip (5.7 KB)

5

Hi again,

I’m attaching a new log, this time I was trying to submit using Deadline Monitor and seems it works well, with this I’m assuming that the problem comes from the 3ds max submitter. I hope have news soon because not having the ability to send from 3ds max UI, I have to spend more time submit jobs from Monitor.

Kind regards…

Job_2024-02-24_20-55-26_65daac1f5436f5ee6e76ba2a.zip (7.3 KB)

6

Did you have a chance to go through the troubleshooting guide to see if you can re-create the failure outside of Deadline?

Given it works when submitted via the Monitor submitter, and the error is about a syntax issue is there maybe a pre-render script that’s set in the failing jobs and not in the successful ones?

You can compare the jobs that have been created by double clicking them in the Monitor and going to ‘Submission Params’. Those two files are what make a job a job in Deadline. And since one submitter makes working jobs and one doesn’t, the difference in those files is the solution to the issue.

7

Greetings
I seem to be having having the same issue as above. The scene does render fine locally on the worker machine “dfc-peter”.
Attached is the error report:
deadline-error.py (106.5 KB)

3dsmax 2024.2.1 update
OctaneRender 2023.1 - 14.03
Deadline Client Version: 10.3.2.1 Release (1a66fe40f)
Repository Version: 10.3.2.1

cheers~
~p

8

It looks like this is a 3dsmax 2024 submitter issue as i am able to launch manually from monitor.
This is not ideal as we use many of the functions in the submitter including state sets for our workflows.
Any help would be appreciated.
Thanks!
~p

1 Like
9

Giving this a bump because I’m having the same issues as above even after a solid week of troubleshooting many versions and solutions.

3ds Max 2024.2.3
Octane Render 2023.1.3 - 14.13
Deadline Repo & Client Version 10.4.0.8

I should mention that I can submit from the monitor okay with 3dsmax/3ds Command but this isn’t viable for our team of artists, because we need the extra features of the integrated submitter in order to roll this into production.

Please help! Thanks in advance :smiley:

1 Like
10

UPDATE!! A fix has been discovered. Tested with Deadline Repo & Client Version 10.4.0.10 (hopefully the devs can roll this fix into future releases)

I have attached an amended .ms file - use this to replace the file found here:
\DeadlineRepository10\submission\3dsmax\Main\SubmitMaxToDeadline_Functions.ms

Why this works:

3dsMax has changed with regards to arrays. There are several Octane properties which are parsed as arrays. If there are more than 20 items in the array it will print the extra values as dots. So we add:

				(
					with PrintAllElements on
					(
					try(format "%_%=%\n" rendererID (p as string) (getProperty renderers.current p) to:JobInfoFile)catch()
					)
				)

After line 7066 and line 8518.

Upon fixing this, another bug was discovered when ‘use data from 3ds max batch render’ is checked if you have multiple jobs to send off at once:

image
image751×687 23.2 KB

It will sometimes throw up this error:

“-- Runtime error: Attempt to access deleted < MixinInterface >”
“-- Line number: 10611”

This happens because the RestoreMaxFileCopy function is causing the next batch render job to delete upon reload.

To fix this we enter the following to our script after line 10595:

					local old_view_props = for p in (getpropnames theView) collect (getproperty theView p)
					if old_view_props[1] != undefined do old_view_props[1] = old_view_props[1].name -- canera --> camera.name
					SMTDFunctions.RestoreMaxFileCopy originalPath
					if not (assert (numViews == batchRenderMgr.numViews) message:"different number of views after RestoreMaxFileCopy") do
						throw "different number of views after RestoreMaxFileCopy"
					views = (for j = 1 to numViews collect (batchRenderMgr.getView j))
					theView = views[i]
					for p,j in (getpropnames theView) do
                    (
						local val = (getproperty theView p)
                        if j == 1 and val != undefined do val = val.name -- canera --> camera.name
						if not (assert (val == old_view_props[j]) message:"batchRenderViewOps property values different after RestoreMaxFileCopy") do
							throw "batchRenderViewOps property values different after RestoreMaxFileCopy"
					)

TLDR: Make a backup of your current SubmitMaxToDeadline_Functions.ms file in the repository and replace it with the attached.

SubmitMaxToDeadline_Functions.zip (111.2 KB)

1 Like
11

Thanks Sean!
I’ll test this out this weekend
cheers~
~p

1 Like