02-16-2014, 11:29 PM
Just a quick note with errors on rendering with mental ray. I resolved the issue but it is worth noting that old problems are still occurring in some situations.
I had a simulation of a suns corona which I had rendered successfully but when upgraded to 3.5.3 would cut black boxes out of the render the closer the camera came to the object. The sim data is generated in one file and is accessed in another scene which contains a copy of the grid with reference to the generated data, repositioned by a couple of hundred units (nothing drastic) to match the geometry and camera.
I checked again that shad segments were activated and the autovolume was on - all ok.
The preview window displayed the data that was simmed so that looked all fine, and rendering scanline looked fine as well. But the render kept going black when rendered with mentalray.
I suspected that the original sim may need to be updated so I changed some sim settings and simmed again, with the same result. this time not using the retimed post process files (which I thought may have been the issue) and just using the straight default sim, but again it rendered black after a number of frames.
Thinking there was an error with the upgrade I decided to check a couple of other sims in the same scene (a separate layer of the chromosphere) strangely this looked fine no matter how close I came.
I decided to come back to the source corona sim and rotate the fume grid so that the z axis faced the front viewport instead of the top and simmed a couple of hundred frames to test. Going back to my main file which accesses the sim data I checked these new frames and they rendered fine!
I am in the process of simming the complete sequence, and have my fingers crossed.
The main reason for this post is to let you know there are still some issues.
Anticipating the usual line...."just use scanline" - this is impossible because I need to generate a dome image to a non standard 120 degree field of view which a 5 camera rig cannot achieve (needs a 180 degree FOV). In addition, it is a great time wasting burden to generate the layers and stitch etc.
I had a simulation of a suns corona which I had rendered successfully but when upgraded to 3.5.3 would cut black boxes out of the render the closer the camera came to the object. The sim data is generated in one file and is accessed in another scene which contains a copy of the grid with reference to the generated data, repositioned by a couple of hundred units (nothing drastic) to match the geometry and camera.
I checked again that shad segments were activated and the autovolume was on - all ok.
The preview window displayed the data that was simmed so that looked all fine, and rendering scanline looked fine as well. But the render kept going black when rendered with mentalray.
I suspected that the original sim may need to be updated so I changed some sim settings and simmed again, with the same result. this time not using the retimed post process files (which I thought may have been the issue) and just using the straight default sim, but again it rendered black after a number of frames.
Thinking there was an error with the upgrade I decided to check a couple of other sims in the same scene (a separate layer of the chromosphere) strangely this looked fine no matter how close I came.
I decided to come back to the source corona sim and rotate the fume grid so that the z axis faced the front viewport instead of the top and simmed a couple of hundred frames to test. Going back to my main file which accesses the sim data I checked these new frames and they rendered fine!
I am in the process of simming the complete sequence, and have my fingers crossed.
The main reason for this post is to let you know there are still some issues.
Anticipating the usual line...."just use scanline" - this is impossible because I need to generate a dome image to a non standard 120 degree field of view which a 5 camera rig cannot achieve (needs a 180 degree FOV). In addition, it is a great time wasting burden to generate the layers and stitch etc.