- Tue Oct 11, 2011 5:49 am
#347707
This has happened twice over the last three days, but slightly differently...
First time: running a co-operative render, it finished and merged the mxi files, but when I opened it there was a large section that was just black. Approximately 10-15 percent of the image was just missing. No warnings, no nothing. By the time I realized it the temporary mxi files had been overwritten by another render so I was not able to figure it out where it came from.
2nd time: same setup (but different job/file) and this time the merge failed. One mxi is corrupted the same way, but about 3/4ths of the image is just black. The Maxwell node log shows no errors at all. At least this time I can see which one it is and remove that one. It was actually the workstation that gave the bad mxi, not a networked slave.
What is going on with this? It's a major problem to lose hours of rendering this way and I can't predict how/when it will happen at this point.
/b
Screen cap of the bum render:
First time: running a co-operative render, it finished and merged the mxi files, but when I opened it there was a large section that was just black. Approximately 10-15 percent of the image was just missing. No warnings, no nothing. By the time I realized it the temporary mxi files had been overwritten by another render so I was not able to figure it out where it came from.
2nd time: same setup (but different job/file) and this time the merge failed. One mxi is corrupted the same way, but about 3/4ths of the image is just black. The Maxwell node log shows no errors at all. At least this time I can see which one it is and remove that one. It was actually the workstation that gave the bad mxi, not a networked slave.
What is going on with this? It's a major problem to lose hours of rendering this way and I can't predict how/when it will happen at this point.
/b
Screen cap of the bum render:
Brett Simms
http://www.heavyartillery.com
http://www.heavyartillery.com
- By Mark Bell
- By CDRDA