Sorry, I let this topic slip by me unnoticed. We had fixed this internally a little while ago, and it’ll be making its way into the next build (10.0.3). In the meantime, you can use the attached files by:
Backing up your Houdini submission folder (ie. C:\DeadlineRepository10\submission\Houdini\Main)
Unzipping the attached Houdini.zip
Moving the unzipped files into your Houdini submission folder (same folder as step 1)
We had unfortunately introduced some silly errors with the large refactor to allow for the Deadline ROP node, sorry about that. Let me know if this works for you!
Hi
Just tried you quickfix today but now i get this error when submitting Redshift jobs (not standalone):
The correct path to Houdini is defined in Configure plugins.
Error: GetConfigEntry: Attempted to access non-existent config key Houdini16.0_Hython_Executable (Deadline.Plugins.RenderPluginException)
at Deadline.Plugins.DeadlinePlugin.GetConfigEntry(String key)
at Python.Runtime.Dispatcher.TrueDispatch(ArrayList args)
at Python.Runtime.Dispatcher.Dispatch(ArrayList args)
at FranticX.Processes.ManagedProcess.RenderExecutable()
at FranticX.Processes.ManagedProcess.Execute(Boolean waitForExit)
at Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)
=======================================================
Type
at Deadline.Plugins.SandboxedPlugin.SendMessageToSandbox(DeadlineMessage messageToSend)
at Deadline.Plugins.SandboxedPlugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask(TaskLogWriter tlw)
Date: 09/19/2017 15:15:55
Frames: 26-50
Elapsed Time: 00:00:00:06
Job Submit Date: 09/19/2017 15:15:27
Job User: bonsa
Average RAM Usage: 7202181120 (6%)
Peak RAM Usage: 7202181120 (6%)
Average CPU Usage: 0%
Peak CPU Usage: 0%
Used CPU Clocks (x10^6 cycles): 0
Total CPU Clocks (x10^6 cycles): 88021
=======================================================
Slave Information
Slave Name: RENDER103
Version: v10.0.1.1 Release (218322271)
Operating System: Windows 10 Pro
Running As Service: No
Machine User: racecar
IP Address: 10.0.0.146
MAC Address: 38:D5:47:CA:3D:B8
CPU Architecture: x64
CPUs: 36
CPU Usage: 2%
Memory Usage: 6.7 GB / 127.9 GB (5%)
Free Disk Space: 1.693 TB
Video Card: NVIDIA GeForce GTX 1080 Ti
[/code]
Hmm… It appears that with the newest version of our Houdini submitter also came with some tweaks to allow for side-by-side minor versions of the Houdini application.
I’ll try to make sure I grab all the files that changed for Houdini, but I’ll mention that 10.0.3.2 was released yesterday, which will contain the most recent version of all the Houdini files.
As for files which I BELIEVE you need:
HoudiniPluginFiles.zip (10.5 KB) files should be unzipped and copied to DeadlineRepository10/plugins/Houdini
MantraPluginFiles.zip (3.19 KB) files should be unzipped and copied to DeadlineRepository10/plugins/Mantra
HoudiniMantraSubmission.zip (15.9 KB) files should be unzipped and copied to DeadlineRepository10/scripts/Submission
This bug would be occurring in repo/plugins/houdini, not the submission side. As in, on the submission side we’re now appending the minor version number, and the the plugin needs to be updated to also know about that minor version.
When I updated my repo to 10.0.3.2 to test this, I had to update the path to the executable, but it was finding the config entry (with the minor version). If you’re still experiencing this issue after updating the plugin directory, it’s probably worth to signal Deadline to update the database by going to Tools -> Configure Plugins -> Houdini and modifying the path to the executable (even if it’s correct). Deadline will think it’s “dirty” and update the db meaning everything should be good from there.