Memory management is an issue with Shaderlight v0.1. It is the nature of the application to use significant amounts of memory which, at this stage of development, has not been thoroughly optimized.

 

Unlike a traditional renderer, Shaderlight keeps a lot of information in memory to store its intelligent pixels, so that it can continuously update the rendered image. This means that there will be less memory available for 3ds Max or other applications you might run at the same time. 3ds Max may be less responsive than you are used to, but we think that the work-flow benefits outweigh any inconvenience. When interactively rendering very complex images, you may find that Shaderlight uses all the memory it can safely use, and it will warn you that its memory limit has been reached. You may continue, and Shaderlight will do its best to finish the image, but it may make your computer unresponsive as a whole, and you will need to use the Windows Task Manager to shut down Shaderlight.

 

You will also find that the kind of tricks you had to use with your old renderer to make it faster – like reducing polygon count – don’t have as much effect with Shaderlight. Shaderlight’s speed and memory usage depend less on the complexity of the 3D scene, and more on the complexity of the 2D image. An intelligent pixel that includes contributions from many lights and materials uses more memory, and takes more time to process, than one that only shows a contribution from one light and one material.

 

Certain settings in Shaderlight will use large amounts of memory, so although we encourage you to experiment with as many features as possible, please be aware of the following large memory features:

 

 

We have noted considerable performance differences between XP and Vista, with Vista outperforming XP by over 50%. This is related to better memory management functions in Vista.

 

 

Page url: https://artvps.com/media/onlinehelp/index.html?memorymanagement.htm