constantly switching between blurry and clear as they are swapped into and out of memory due to lack of space). The idea here is to provide the scene textures with their own “pool” of graphics memory, so they are no longer competing for graphics memory with all the other textures obtained from the region and the viewer’s UI textures, and should thus result in fewer issues of visible textures being “thrashed” (e.g. With the 2.4.1.9 release of Black Dragon, Niran has split how graphics memory is used between “global” textures – which include all the UI elements, etc., and the graphics memory currently being used to render the current scene – what you are actually seeing in-world at any moment in time. Up until the 2.4.1.9 release, Black Dragon, like most viewers, offered a single slider for setting the amount of video memory which could be dedicated to texture processing by the viewer The is generally set to 512 Mb by default.

Generally, the viewer has one slider for setting a limit on the amount of texture memory, which encompasses everything you see in the viewer, including all of the UI elements. The first of the changes Niran has made relates to the way in which graphics memory is used with textures. Taken together, they are part of a larger update Niran has been planning, but as he comments in the release notes, he wanted to get these particular changes out to show people, and will save the rest for his upcoming version 2.4.2 release. The update also includes a number of other fixes to some long standing rendering issues that Niran has been attempting to fix. On Tuesday, March 10th, NiranV Dean released version 2.4.1.9 of his Black Dragon viewer, which includes his recent work on volumetric lighting for Second Life, which I reported on at the start of March.

Dragon viewer for second life