I was wondering if anyone has come across this, error.
I am using MAx Design 2013 with latest krakatoa build when I send my pflow for partitioning via Deadline (5.2.0.49424) I am getting this error.
Exception during render: An error occurred in RenderTasks(): RenderTask: Unexpected exception (Exception caught in 3ds max: – Unknown property: “LoadFilePartition” in $Random Walk 001
I looked at the KrakatoaPartitionTasksOnDeadline.ms script which is run for partitioning on Deadline, and the only occurrence of this property is in the code
else if classOf operator == Birth_Particle_File then
(
du.LogMessage (" >Adjusting [" + operator.name + "]")
operator.LoadFilePartition = true
operator.FilePartitionPart = operator.FilePartitionPart + incrementValue
du.LogMessage (" +File Partition Part in Birth Particle File Operator [" + operator.name + "] adjusted by ["+ incrementValue as string +"] to [" + operator.FilePartitionPart as string + "].")
)
I believe that Birth_Particle_File was an old PFlow operator that supported the loading of individual partitions from disk (before we switched to using a PRT Loader in Krakatoa_PRT_Birth), so there is no reason for your Random Walk to ever pass this classof() test.
If you type in the MAXScript Listener while in the Random Walk scene
classof $Random_Walk_001
what does it say in the Listener?
In Max 2014 where I have Data Operators, I get PresetOperIcon as the result, which is clearly not the same as Birth_Particle_File.
We will need to look deeper into what is going on there.
Does the scene works correctly when partitioning locally? The local partitioning runs the SAME code to set the random seeds, so I would expect it to cause the same error. Please let me know if it does…
Yeah, that was the old class name.
I almost suspect there is something else going wrong (in addition to your lightning.dlx problem).
We could add some more debug print lines inside the Deadline script for partitioning to see what it does and why it complains.
That error made no sense from the very beginning. Is it doing the same in Max 2014?
Can you send a SIMPLE self-contained scene that, if submitted to Deadline, replicates the problem? (does not have to be the one you are currently working on).