In DAZ 4.7 what's this Optimizing images x/x when Rendreing 3DDelight?

nokoteb99

This never happened in DAZ 3 but in DAZ 4.7 , not always but many times, i start rendering and it says "Optimizing Images 1/20" or something and it goes all the way to 20/20 then the render starts.

It's annoying especially if i had to render and animation and it did that for every frame. ( I don't know yet if it would do that for every frame but i'm just speculating)

Richard Haseltine

All versions have done this, but the timing has varied. It's making the multi-resolution .tdl files used by 3Delight to manage memory use. If you allow DS to sit, or do non-rendering stuff after loading, most of the optimisation will happen in the background; if you load and render, or adjust the gamma settings, then the optimisation will have to be done as part of the render process.

bshugs@hotmail.com

Richard Haseltine said:

All versions have done this, but the timing has varied. It's making the multi-resolution .tdl files used by 3Delight to manage memory use. If you allow DS to sit, or do non-rendering stuff after loading, most of the optimisation will happen in the background; if you load and render, or adjust the gamma settings, then the optimisation will have to be done as part of the render process.

I've been wondering about this myself, mostly because the number of images seemed inconsistent. If I follow what you're saying, the optimization is taking place in the background while I play around with poses. Does this explain why sometimes I have 120 images, and other times only 30?

Also, is there any way to make those .tdl files persistent? Particularly for a scene where I might change a lot of posing information, or add a prop or two, but not change my my character's textures? Do the render settings or the nature of the original textures (resolution, format, etc) have any effect on optimization?

Sometimes it can take a while on my older machine to optimize the images; often longer than the time to render the image itself. Any ideas would be appreciated.

Bejaymac

What happens is that every single texture in your scene is converted with tdlmake, it converts them into a mip-mapped TIF format with a .TDL file extension.

Now as Poser content isn't native to DS it has to be converted as your loading it, during this tdlmake starts to convert the textures, and is usually finished by the time you see the item in the viewport.

It's always been a different story when it's DS native formats your loading, depending on what your doing it can take tdlmake a few minutes to realize it should have converted the textures.

So loading a scene file and hitting render, or chopping and changing textures on an item or two and then hitting render, can really catch tdlmake out and is why you see optimizing all the time.

StratDragon

if you have a scene with 120 textures they will be converted to TDL's the first time you render them, on subsequent renders it won't need to do this unless you quit out of DS or crash or close the scene.

if you decide after to add a new figure, replace an existing figure mat, etc, the next tine you render those new textures just added will need to be converted before the rendering process begins.