AWS Thinkbox Discussion Forums

Cinema 4D 2024.4.0 Submission Framerange Bug

When submitting multiple takes with frameranges there is this error:
TypeError:‘float’ object cannot be interpreted as an integer deadline cinema 4d
It seems that the framerange is causing the error. I think Maxon has changed the integer values that are forwarded via python to the Deadline submitter.
Is there a patch to support takes with frameranges?
Cinema 4D 2024.4.0
Deadline 10.3.2.1
Redshift 3.6.0.1

Yep! Check out Cinema4D R2023.2 submission error - #3 by Justin_B

EDIT: This only touches the frame rate not the range. If that doesn’t work could I get the whole stack trace you’re seeing? Likely the same fix but I’d rather be sure.

Here is the log of the submission:
Creating C4D submit info file
Traceback (most recent call last):
File “//share/DeadlineRepository10_3\submission/Cinema4D/Main\SubmitC4DToDeadline.py”, line 2939, in Command
if not self.SubmitJob():
^^^^^^^^^^^^^^^^
File “//share/DeadlineRepository10_3\submission/Cinema4D/Main\SubmitC4DToDeadline.py”, line 2052, in SubmitJob
startFrame = renderData.GetTime( c4d.RDATA_FRAMEFROM ).GetFrame( framesPerSecond )
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: ‘float’ object cannot be interpreted as an integer

Yep, that’s the one that’s fixed in the post I linked. Glad nothing else is breaking - give that file a shot and let us know if it gives you any trouble.

Privacy | Site terms | Cookie preferences