Tweet
Our studio seems to be having a strange issues with licenses, which we only started having after upgrading our Vray to 3.6.02
Normally, we have enough Vray licenses for only our lighting team, even though we install Vray on our animation workstations in order to have Vray nodes load properly in Maya for our animators.
This has been working out perfectly fine since Vray only pulls a license when you actually hit the render button. After we updated, however, the animator workstations started pulling licenses just by loading up a scene file with Vray nodes in it.
My question is: Has there been a change to when Vray pulls a floating license?
Is there a workaround for this? (Perhaps a way to blacklist Animator machine from pulling a license, while still having Vray loaded so they can properly work in scenes that have vray nodes in them).
Is this a situation where we would need to have more licenses for animators, even though they are not rendering with Vray?
I would appreciate some clarity on this.
Thanks much!
-ChrisB
Normally, we have enough Vray licenses for only our lighting team, even though we install Vray on our animation workstations in order to have Vray nodes load properly in Maya for our animators.
This has been working out perfectly fine since Vray only pulls a license when you actually hit the render button. After we updated, however, the animator workstations started pulling licenses just by loading up a scene file with Vray nodes in it.
My question is: Has there been a change to when Vray pulls a floating license?
Is there a workaround for this? (Perhaps a way to blacklist Animator machine from pulling a license, while still having Vray loaded so they can properly work in scenes that have vray nodes in them).
Is this a situation where we would need to have more licenses for animators, even though they are not rendering with Vray?
I would appreciate some clarity on this.
Thanks much!
-ChrisB
Comment