Patrick Piché
3D TD at Hybride
Hi Patrick,
By design, we always start processes with below normal priority, that
way you can still use a machine while it’s rendering. So it’s strange
that you would be running into a problem like this.
Is this problem related to a specific plugin (maya, max, etc), or is it
in general? Any specific details you can provide about your setup and
software will help us try to track down this issue for you.
Kind regards,
- Ryan
We have some “STALLED SLAVE REPORT” with XSI and we think this is because of this Priority value of the process…
I’ll check if it’s the same priority level on Maya.
Patrick Piché
3D TD at Hybride
It's the same for Maya... The process is set at Realtime priority... The DeadlineClient set this priority when he start the process?
Patrick Piché
3D TD at Hybride
I found that on some machines there is no 'belownormal' priority and on others there is.
ex.:
One is set like:
->Realtime
High
Normal
Low
The other:
Realtime
High
AboveNormal
Normal
->BelowNormal
Low
Maybe it's passing to Realtime because it can't find the BelowNormal priority.
Any idea why we don't have the Above Normal and Below Normal Options on those computers???
Windows 2000 SP4 on all machines... :(
Thanks..
Patrick Piché
3D TD at Hybride
Just out of curiosity, does the following warning message appear in the
slave log on the machines that have this priority problem:
“Failed to reduce the priority of the render process.”
We output this when setting the priority to BelowNormal fails. We’re
just wondering if your situation is actually being recognized by Deadline.
Thanks!
- Ryan
We’ve implemeted a workaround where if setting the priority to
BelowNormal fails, then it is set to Normal instead. This fix will be
included with the next release of Deadline.
It turns out that Windows NT and Windows ME/98/95 do not support the
BelowNormal and AboveNormal settings. But you’re running Windows 2000,
so that’s strange…
Regards,
- Ryan
Can we have a quick fix? How many time before the next release?
It's hard to render stuff at night.
Patrick Piché
3D TD at Hybride
Pat… it’s time to go XP 
Here are the new XSI and Maya plugin files (they're actually the same file with different names). Just copy them to their respective plugin directories in the repository (make sure to back up the originals just in case).
The new plugin files should be compatible with Deadline 1.2.15710 (they for sure won't work with any older versions).
Let us know if this solves your problem. If so, the new release will include the fix as well.
Kind regards,
- Ryan
I replaced the XSI.deadline file in the XSI plugin and (even after restarting the client) we get this error:
Scheduler Thread - Render Thread 0 threw an error:
Scheduler Thread - Object reference not set to an instance of an object.
Scheduler Thread - Unexpected Error Occured
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Exception Details
NullReferenceException -- Object reference not set to an instance of an object.
Exception.TargetSite: Void .ctor(Deadline.Jobs.Job, Deadline.Jobs.Task, Deadline.Slaves.Slave, Deadline.Plugins.Plugin, Deadline.Repositories.JobRepository)
Exception.Source: Deadline
Exception.StackTrace:
at Deadline.Slaves.TaskLogging.TaskLogWriter..ctor(Job job, Task task, Slave slave, Plugin plugin, JobRepository jobRepository) in C:\rrussell\Development\DeadlineProject\Deadline\Slaves\TaskLogging\TaskLogWriter.cs:line 28
at Deadline.Slaves.SlaveRenderThread.ThreadMain() in C:\rrussell\Development\DeadlineProject\Deadline\Slaves\SlaveRenderThread.cs:line 111
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Patrick Piché
3D TD at Hybride
We’re going have to revert our code to the version that was released and
make the changes there so that it’s (hopefully) compatible. I’ll post
the two new plugin files as soon as we do. In the meantime, just revert
back to the previous plugin files.
Any news about?
Patrick Piché
3D TD at Hybride
Hi Patrick,
I think it might be best to wait for the new Deadline release, which
will include this workaround. This way we avoid any compatibility issues
like we ran into before. If for some reason the new version doesn’t fix
your problem, we will be able to create patches to try and fix the
problem without worrying about whether or not they will be compatibile.
The new release is tentatively scheduled for next week, and we will make
an announcement on the webboard when the release occurs.
Thanks for your patience regarding this issue.
Kind regards,
- Ryan