Tweet
Hi everybody,
I have an urgent issue concerning vray swarm (version 1.4.1 together with Rhino 5 and vray 3.4):
After seeing all those promising ads for vray 3.4 and vray swarm, I decided to upgrade my whole system. Not only the software but also the hardware: 4 render machines were purchased for quite some money.
Now, after several weeks of testing and production it turns out that this setup doesn't work as promised.
First, there are the well-known bugs that Micha and others have already listed since quite some time that reduce the professional usability to a very low value.
Second I have some problems with the vray swarm (I've already adressed the support but their answer was not really solving the solution). I thought swarm is supposed to work as a plug and play solution. Well, it doesn't. Even if I neglect the very time consuming procedure of setting it up on 4 slaves, it won't run stable. It's randomizing the identification of the license machine as well as of the different machines in the network. Sometimes all the machines contribute, sometimes one or two are missing or they are only assigned but not rendering. Sometimes they are rendering although no rendering was started. All of these symptoms appear while the are running and also after restarting. It appears very random to me.
It is very annoying, that I have to reconfigure everything before starting a render job and even then it's not said that everything will work accordingly. Actually this is not the purpose of a local render farm.
So, I'm asking chaosgroup to really take care of this issue. Not only by answering that this might be a firewall issue. It might be a firewall issue (although I don't think it's the ony thing), but this is something that swarm should automatically configure, since this is a key feature of distributed rendering. Please take care of this. I'll be avaiable for RDP so we can find out together.
Best regards
Toni
I have an urgent issue concerning vray swarm (version 1.4.1 together with Rhino 5 and vray 3.4):
After seeing all those promising ads for vray 3.4 and vray swarm, I decided to upgrade my whole system. Not only the software but also the hardware: 4 render machines were purchased for quite some money.
Now, after several weeks of testing and production it turns out that this setup doesn't work as promised.
First, there are the well-known bugs that Micha and others have already listed since quite some time that reduce the professional usability to a very low value.
Second I have some problems with the vray swarm (I've already adressed the support but their answer was not really solving the solution). I thought swarm is supposed to work as a plug and play solution. Well, it doesn't. Even if I neglect the very time consuming procedure of setting it up on 4 slaves, it won't run stable. It's randomizing the identification of the license machine as well as of the different machines in the network. Sometimes all the machines contribute, sometimes one or two are missing or they are only assigned but not rendering. Sometimes they are rendering although no rendering was started. All of these symptoms appear while the are running and also after restarting. It appears very random to me.
It is very annoying, that I have to reconfigure everything before starting a render job and even then it's not said that everything will work accordingly. Actually this is not the purpose of a local render farm.
So, I'm asking chaosgroup to really take care of this issue. Not only by answering that this might be a firewall issue. It might be a firewall issue (although I don't think it's the ony thing), but this is something that swarm should automatically configure, since this is a key feature of distributed rendering. Please take care of this. I'll be avaiable for RDP so we can find out together.
Best regards
Toni
Comment