s5.mp4 by jimmysparks
Members remain the original copyright holder in all their materials here at Renderosity. Use of any of their material inconsistent with the terms and conditions set forth is prohibited and is considered an infringement of the copyrights of the respective holders unless specially stated otherwise.
Description
The revised and corrected version of the previous posted test animation.
This one was rendered using Calyxa's 'Force Ray Trace' method of assigning a Reflection value of '.01' to the planetary terrain and then rendering with 'Enable Reflections' selected as 'true' - thereby forcing MJW to use ray-tracing to render the terrain. This helps eliminate render-artifacts associated with the native MJW QAEB render engine.
Average render times for the QAEB version were about '2:30' per frame. Render times for this ray traced version ranged between '15' and '60' minutes per frame.
Comments (4)
jimmysparks
Ray traced frames that were close to the terrain took far longer to render than farther away shots did. The part where the camera skims the top of the rock took about an hour per frame.
Daduli
An elegant, beautiful flight over the terrain. ;) That means the calculator was rendering for a few days. Wouwh! At Goldura, Kupfina and Zinkorina my PC for the final render 2000 x 1500 pixels, AA 3 and GD 5 each ran for about 4 days.
calyxa
Are you also setting the 'Search Distance' parameter down to also a tiny number? It defaults to 50000 and that's "meters".
jimmysparks
I've left the Search Distance value at default.
Should it be higher or lower?