Tweet
_____ EDIT: I've just doublechecked and it seems like I was wrong, I just did a re-run of the entire scenario in an isolated setup. And in that scenario there only one license was pulled per rendernode, disregarding the number of V-Ray instances running on that node! Sorry for causing a fuzz!
_____Anyways, the Issue about the watermark and the VFB-2 Interface is still valid.
Hey Chaos folks, I've been a loyal fan for ages now but this is the first time I gotta rant... I'm sorry.
I've just upgraded everything to V-Ray 5 because the non-implementation of VFB-2 in standalone was a deal-breaker for me in the beginning. I'm rendering with V-Ray Standalone on Linux.
After upgrading, I quickly noticed that the licensing policy has changed.
It seems that if you run two instances of VRay on a single machine, each instance grabs a render license instead of just one license for the machine. Is that a new policy with VRay 5?
If yes, I would argue that you could have done a better job communicating this essential change to the users.
Often times we have scenes that depend on a lot of assets, but then have a very short render time, meaning, we have long loading and prep-times with mostly single-threaded workloads.
Running multiple (we did run up to 16) V-Ray instances per render nodes was always a good way to balance the idle CPU times a bit. If this is a new policy, we would now need significantly more licenses for a higher price then we would have needed for "next"
Another thing is, while all licenses were in use, no error about missing licenses was thrown it just rendered a bunch of watermarks into the rendering.
Meaning every n-th image now has watermarks in it instead of just throwing an error about not having a license. Is this also a new policy?
Can we please have a command-line argument for this? Something like "throwLicenseError=1" or something like this? Instead of just rendering with CPU time that's gonna go to waste because of watermarks?
Another thing is, it's been about 6 months since the release of 5 and as far as I know, we do not have an implementation for VFB-2 in Standalone. Can you provide us with an ETA on when this is going to happen?
Sorry for the rant but I'm used to much better communication about these things from Chaos Group.
-Robert
_____Anyways, the Issue about the watermark and the VFB-2 Interface is still valid.
Hey Chaos folks, I've been a loyal fan for ages now but this is the first time I gotta rant... I'm sorry.
I've just upgraded everything to V-Ray 5 because the non-implementation of VFB-2 in standalone was a deal-breaker for me in the beginning. I'm rendering with V-Ray Standalone on Linux.
After upgrading, I quickly noticed that the licensing policy has changed.
It seems that if you run two instances of VRay on a single machine, each instance grabs a render license instead of just one license for the machine. Is that a new policy with VRay 5?
If yes, I would argue that you could have done a better job communicating this essential change to the users.
Often times we have scenes that depend on a lot of assets, but then have a very short render time, meaning, we have long loading and prep-times with mostly single-threaded workloads.
Running multiple (we did run up to 16) V-Ray instances per render nodes was always a good way to balance the idle CPU times a bit. If this is a new policy, we would now need significantly more licenses for a higher price then we would have needed for "next"
Another thing is, while all licenses were in use, no error about missing licenses was thrown it just rendered a bunch of watermarks into the rendering.
Meaning every n-th image now has watermarks in it instead of just throwing an error about not having a license. Is this also a new policy?
Can we please have a command-line argument for this? Something like "throwLicenseError=1" or something like this? Instead of just rendering with CPU time that's gonna go to waste because of watermarks?
Another thing is, it's been about 6 months since the release of 5 and as far as I know, we do not have an implementation for VFB-2 in Standalone. Can you provide us with an ETA on when this is going to happen?
Sorry for the rant but I'm used to much better communication about these things from Chaos Group.
-Robert
Comment