Deadline erroring on tyrender.dlo
#1
Hey everyone, I have a strange issue happening.

Our render farm has several types of machines on it (intel/amd) and the beta portion was working well on all the nodes.  (No errors).  Recently, we have a bank of machines that now gives this error below saying there is no tyflow.dlo and that tyrender will be used instead.  I have the node locked pro license on my workstation.
The issue is that these machines are giving errors even when the job submitted has nothing related to tyflow in it.  Before we go on further investigation, am I supposed to put the the tyflow.dlo AND tyrender.dlo in the plugins folder?  Is the error doing a search for the tyflow.dlo during load and not finding it?  I was under the impression the tyrender.dlo node file would solve that because the rest of the farm is set up the same way as this bank of machines and its working fine.


Attached Files Thumbnail(s)
           
  Reply
#2
Hi, that's not an error per se...it's just tyFlow notifying you that 'tyFlow_xxxx.dlo' was not found, but 'tyFlow_xxxx_render.dlo' was found....so it's using that for rendering instead (which is fine). That message will be displayed regardless of whether or not tyFlow is used because it's just a note that is printed when all available plugins are loaded while Max starts). It's not something that's necessarily relevant to any actual errors or crashes that are occurring...

And yes, it's fine to have both tyFlow_xxxx.dlo and tyFlow_xxxx_render.dlo in the same place...in fact, that's the way it should be. If you have them in separate places, legitimate errors may actually occur because if they're not in the same place they may both end up loading, resulting in duplicate class ID errors. This is all explained in the docs:

https://docs.tyflow.com/license/render

So the setup you should aim for is:

Workstations: tyFlow_xxxx.dlo (licensed)

Render machines: tyFlow_xxxx.dlo (unlicensed) AND tyFlow_xxxx_render.dlo

Or if you're loading all dlo files from a shared network location across both licensed and unlicensed workstations, just put tyFlow_xxxx.dlo and tyFlow_xxxx_render.dlo in that same folder and the nodes/workstations will load what they need when they need it (that's what those deadline messages are notifying you about...they're telling you what was found and consequently what is being loaded)
  Reply
#3
(04-20-2022, 03:26 PM)tyFlow Wrote: Hi, that's not an error per se...it's just tyFlow notifying you that 'tyFlow_xxxx.dlo' was not found, but 'tyFlow_xxxx_render.dlo' was found....so it's using that for rendering instead (which is fine). That message will be displayed regardless of whether or not tyFlow is used because it's just a note that is printed when all available plugins are loaded while Max starts). It's not something that's necessarily relevant to any actual errors or crashes that are occurring...

And yes, it's fine to have both tyFlow_xxxx.dlo and tyFlow_xxxx_render.dlo in the same place...in fact, that's the way it should be. If you have them in separate places, legitimate errors may actually occur because if they're not in the same place they may both end up loading, resulting in duplicate class ID errors. This is all explained in the docs:

https://docs.tyflow.com/license/render

So the setup you should aim for is:

Workstations: tyFlow_xxxx.dlo (licensed)

Render machines: tyFlow_xxxx.dlo (unlicensed) AND tyFlow_xxxx_render.dlo

Or if you're loading all dlo files from a shared network location across both licensed and unlicensed workstations, just put tyFlow_xxxx.dlo and tyFlow_xxxx_render.dlo in that same folder and the nodes/workstations will load what they need when they need it (that's what those deadline messages are notifying you about...they're telling you what was found and consequently what is being loaded)

Ok thanks, I'll try placing both .dlo files in plugins and see if that solves the issue on that bank of machines. Its just bizarre that the same set up works on other banks but not this one; I'll post the results! Thank you
  Reply


Forum Jump: