Vray unhandled exception updating render lights dating before christ and anno domini
the ray intersection with geometry and the determining of its properties, is not time significant.However, the number of raycasts during photorealistic rendering can exceed manyfold the number of rendered image pixels.There is one disgusting thing while rendering complex scenes in V-Ray. It can even fully disarm someone, killing any enthusiasm to continue any further work on the current scene. Can it really be true that to complete a big project we inevitably need to increase the amount of RAM, installed in computer?Especially unexpected and tricky this thing becomes when one is working on the commercial rendering with clearly defined deadline. Is it true, that the only way out is to go to the computer store and buy a few more sticks of RAM?For example, the HD 1920x1080 resolution render is made of more than 2 million separate pixels.
This is the initial aspect of the entire rendering process.
Our hard working ant knows that he needs to find a yellow leaf among the myriad of unnecessary for him green ones. Of course, he will have to go sequentially through a bunch of green leaves, starting from the closest to one, until he find the one and only yellow leaf.
He will have to approach first leaf and see whether it is yellow.
All forums and discussion boards about V-Ray renderer are just snowed under with the pleading requests for help in completion rendering of heavy scene : D Of course, we are talking about the lack of RAM during rendering, which is the prevailing reason of 3ds Max and V-Ray system crash. To answer these questions, let us see how V-Ray uses the memory and what tools of managing the process of its use are available to us.
In any software, the memory management and the way of placing the data there is a very complicated and routine material. There is absolutely no sense to go deep into describing the data arrays and the ways of addressing to them.