Loading...
> >

Goodbye disk space!

SimonJMSimonJM Posts: 5,982
edited December 1969 in Technical Help (nuts n bolts)

This is really annoying. I have a scene that has been undergoign minor development as a friend who wishes to use it for a book cover makes requests. That's not a proble, really. All has been going well until - well, yesterday.
Now it seems that whenevr I load that scene, or any of the previous versions (I have a couple) the tdlmake processes get into a loop and churn out the same .tdl files. Again. And again. And again. Not only does this make DS a little unresponsive it also consumes disk space. If I do a render it does claim to have ended doing the optimizing (see below), but the tdlmakes are still running ...

Optimizing Images - 49/58
Optimizing Images - 50/58
Optimizing Images - 51/58
Optimizing Images - 49/58
Optimizing Images - 50/58
Optimizing Images - 51/58
Optimizing Images - 52/58
Optimizing Images - 53/58
Optimizing Images - 51/58
Optimizing Images - 52/58
Optimizing Images - 53/58
Optimizing Images - 51/58
Optimizing Images - 52/58
Optimizing Images - 53/58
Optimizing Images - 54/58
Optimizing Images - 55/58
Optimizing Images - 53/58
Optimizing Images - 54/58
Optimizing Images - 55/58
Optimizing Images - 56/58
Optimizing Images - 57/58
Optimizing Images - 55/58
Optimizing Images - 56/58
Optimizing Images - 57/58
Optimizing Images - 58/58

Anyone seen anything similar or have a clue what might be doing it? Or better yet, a way of stopping it happen? :)

Comments

  • SzarkSzark Posts: 10,634
    edited December 1969

    Never seen it but if I get TDL issues I usually clear out the Daz Studio Temp folder usually found in Drive letter:\Users\name\AppData\Roaming\DAZ 3D\Studio4\temp

  • SimonJMSimonJM Posts: 5,982
    edited December 1969

    That would deal will part of it, but they keep getting added ... ;)

  • SzarkSzark Posts: 10,634
    edited December 1969

    Sorry man I have no idea...never seen this in all my 5 years of using DS.

    Perhaps the Wizard (Richard) will know

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    SimonJM said:
    This is really annoying. I have a scene that has been undergoign minor development as a friend who wishes to use it for a book cover makes requests. That's not a proble, really. All has been going well until - well, yesterday.
    Now it seems that whenevr I load that scene, or any of the previous versions (I have a couple) the tdlmake processes get into a loop and churn out the same .tdl files. Again. And again. And again. Not only does this make DS a little unresponsive it also consumes disk space. If I do a render it does claim to have ended doing the optimizing (see below), but the tdlmakes are still running ...
    Optimizing Images - 49/58
Optimizing Images - 50/58
Optimizing Images - 51/58
Optimizing Images - 49/58
Optimizing Images - 50/58
Optimizing Images - 51/58
Optimizing Images - 52/58
Optimizing Images - 53/58
Optimizing Images - 51/58
Optimizing Images - 52/58
Optimizing Images - 53/58
Optimizing Images - 51/58
Optimizing Images - 52/58
Optimizing Images - 53/58
Optimizing Images - 54/58
Optimizing Images - 55/58
Optimizing Images - 53/58
Optimizing Images - 54/58
Optimizing Images - 55/58
Optimizing Images - 56/58
Optimizing Images - 57/58
Optimizing Images - 55/58
Optimizing Images - 56/58
Optimizing Images - 57/58
Optimizing Images - 58/58

    Anyone seen anything similar or have a clue what might be doing it? Or better yet, a way of stopping it happen? :)

    Yes, I've had it happen...but the only solution I've found...shut down DS, reboot your machine. Manually clean out the temp file...then, if it still goes through the loop, search for the offending texture and remove it...usually reloading the material/shader or LIE preset...there can be more than 1 'bad' one. And no, reloading a saved scene won't help...you need to reload the 'originals'. Sometimes I've had to load a 'blank' material (like the DS Default shader or something like that) then reload the material file.

  • SickleYieldSickleYield Posts: 7,639
    edited December 1969

    Hunt down which .jpgs are in your scene that aren't saved at a resolution of 72 dpi. That's what it's trying to do when it optimizes images, convert everything to that resolution. I go back and resave stuff as that in GIMP now when that comes up.

  • SimonJMSimonJM Posts: 5,982
    edited December 1969

    Ok, thanks mjc016 and SickleYield - that is helping firm up a suspicion of the culprit. I'll see what I can do but as the old machine I have it on has limited HDD space free I get very little time to do stuff! I may decompress the .duf and hack out what may be the offending item(s) manually.

Sign In or Register to comment.