why whn i render it optimzes my whole render images

whats going on today im super laggy, my rendering is acting retarted whn I try to render animations I ctd aaaaaargh BIG ISSUE RIGHT NOW IS I think my motion blure was to high or something so I switch my motion blure and render back to default now I don't ctd but now its freaking optimizing my whole render images I have in my file and its taking for ever OMG WHATS GOIN OOOOOON!!!!!!!!@.@
Comments
Sometimes the optimising images process gets stuck. If it has been sitting there for ages, and expanding the progress bar (clicking the History>>> button) shows it's working on a single image you may need to force close DS via Task Manager (assuming you've saved) and restart it.
if you HAVEN'T saved the scene then don't despair
don't use Task Manager to close DS, close the "optimizing images" window via the red cross in the top right hand corner
you can't do any rendering at this point, and DS is kinda stuck, but you CAN save the file in the normal fashion. you won't get a save progress bar but you'll know when the save has completed because it will display a thumbnail of the saved file. at that point close DS. reopen and continue
which brings me to my own question, and reason for coming here:
this problem has been going on ever since the "optimize" feature was introduced. as an example (and i've had many many such examples in the past), i've got a scene i'm working on at the moment. i was working on it yesterday quite happily. today it wants to "optimize" 112 textures. and each time it tries, it fails
why is it even doing it?
and, how can i STOP it from doing it?
(oh, and, why hasn't someone FIXED it by now?)
...while I do not do animations, I've had this occur numerous times after launching a render, but never never had it stall or crash. Still, it can take some time, especially with a large or very busy scene that has a lot of different elements. In a scene I rendered last night it ran though something like 162 objects taking about four minutes in addition to the rendering time.
Now multiply that by say 30 individual frames and yes, it will add up.
FWIW, I never launch a render process without the History pane expanded just so I can monitor it for any 3Delight warnings/errors.
"Optimisation" is converting the images to the .tdl format that 3Delight wants. DS ha always done it, though exactly when has varied between on loading the textures or when starting to render. It is an unavoidable step. Check the location of your temp folder, in Edit>Preferences, and if it's a disc with little space try changing it to a larger disc.
is that mutiple "tdlmake.exe" processes that take place when loading a full scene?
Yes, that's right.