While working on a DAZ scene recently, I loaded V3 into the scene. I applied a ready made texture, then applied another texture that I had made for the majority of the figure. Then I added another light to the scene. I then got a message while rendering, something in regards to 3Delight Message 3, #2. Following the render, all of the textures that I had applied went white. I would post an image of this - however, in a fit of red beef anger, I deleted the file and started over on it (which now will not render at all!!!!) and cannot get it to repeat this behavior.
Does this mean that I have too many textures loaded into 1 scene for my graphics card? Just wondering if this is a common scenario?
This brings to mind another question - it does not seem that there is a method of removing a texture once it is loaded into a scene, or at least a way that I can find? For your consideration, I thank you.

I had the same problem occasionally (more so when version 2 first came out and had loads of bugs). It happens with one particular scene I'm working on which has lots of small objects and reflective surfaces. The message reads as yours, then 'severity #2' (I think), and then one small item has no texturing. Haven't worked out why yet. You could try to re-load the texture direct from the texture file in the surfaces tab - don't know if that will work, haven't tried myself yet, just an idea. You could also perhaps report it to Daz via their contact page or when you're in D|S click on 'Help' and select 'Report a Bug'. That might get some results. If you want to remove a texture, go to the surfaces tab and then under 'Diffuse' click on the drop down menu that is located just under the Diffuse colour bar and select 'None'. By the same method you can add whatever texture you like to any object. Hope you get it resolved ok:)

Beginners tutorials for Bryce

Bryce Arena

Thanks - I will try the diffuse tab today. I have a strong suspicion that my graphics card cannot handle too many mega textures at once - but I am not sure about that either. I know that if I have a texture where I apply too much reflection, this can cause DAZ to sit and act constipated, and the render seems to never take place. Thanks again.

P.S. forgot to mention that I have relegated myself back to using the old version of DAZ, only because most of my installed content does not function with the currently offered update - does anyone know if the bugs with the distorted figures has been resolved? Hope so - I look forward to using the updated D.S.

If you're having a lot of problems do check that you have go the very latest version which is 1.2.01. Version 1.2 had loads of bugs which seem to have been resolved now. You may like to have a look at the very first thread on this page in one of the Daz forums: http://forum.daz3d.com/viewforum.php?f=16 You could try posting a message in one of the forums - the feedback is usually very good and helpful:)

Beginners tutorials for Bryce

Bryce Arena

The problem with over-application of morphs if you inject (or remove and then inject) a second character to a loaded figure hasn't been fixed in 1.2.0.1, unfortunately. It sounds as if that is what you are experiencing. Your video card won't affect your 3Delight renders - it matters only for OpenGL renders and the preview. Try going to Render>Render settings>Advanced and reduce the bucket size. You can also try reducing the Max Raytrave depth setting if the ernder is choking on reflections, though if you pull it too low you may find things aren't reflecting correctly (it controls how often a line-of-sight from the camera can bounce before it's curent value is taken: set it too low and it may stop at a mirror rather than reaching the object that should be reflected).

Hello, That would make perfectly logical sense - that a 3DDelight software render warning message should not be card related, but I somehow have this feeling in my veins that it might somehow be distantly related to texture overload (only because of the chain of events leading up to the incident itself). I also just tried reducing the bucket size and that does assist in my render times. I was hoping that someone would know why the 3DDelight Warning was popping up - and that associated texture loss, or whatever one might call that. The weird thing is that I cannot replicate the error - if it comes up again, I will copy and post it, as well as the image in question. I may run a post on DAZ's site and see if someone lurking there has encountered and diagnosed this. Thanks all.

After pouring through the log file I found this - 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd2_SBody.tdl" not found. 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd1_SBody2a.tdl" not found. 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd3_SHeadDef.tdl" not found. 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd6_SLashes.tdl" not found. 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd7_SRef1L.tdl" not found. 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd8_SEyeDefL.tdl" not found. 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd4_SHeadDet.tdl" not found. 3Delight message #3 (Severity 2): "C:Program FilesDAZStudiotempd9_SRef1R.tdl" not found What is a .tdl file? Is that a temporary 3Delight texture file?

What is a .tdl file? Is that a temporary 3Delight texture file? Yes, one of the D|S "helper" programs is called tdlmake as soon as you load an object that has textures, or apply textures with a script preset, tdlmake begins converting all the new textures into .tdl format. They're stored in the StudioTemp folder. A few seconds after you quit D|S, these temp files are automagically deleted. This used to be different back in the Beta days, originally the .tdl conversion didn't happen until you hit the "Render" button, which slowed down renders. This way you can still play around with posing stuff as soon as it's loaded, although there is a slight speed/performance hit, while the conversion is going on in the background. Except sometimes it doesn't quite work right, which seems to be the glitch that's tripping you up.

So D|S is converting the textures into another format to accomodate the quirks of the render engine and not just slapping the jpegs, tifs or whatever onto the objects?

So D|S is converting the textures into another format to accomodate the quirks of the
render engine and not just slapping the jpegs, tifs or whatever onto the objects?

Yes, that's it. I don't know the details, but I suppose it's to create a common pic format so the renderer doesn't have to worry about "is this a jpeg, tiff, or whatever?" just consider how many different file formats get used for textures. It's just a bit of preprocessing to speed up the actual render once you hit the button.

I find that rather odd, to be honest. Considering that the vast majority of textures would be jpegs, or the common uncompressed formats of say, tif, bmp and maybe tga, I would have thought that writing plug-ins that handle these common formats would have been a simpler way to do things. Pre-processing already common formats seems to me to be a slower method, rather than faster. Ah well.

Actually, tdlmake is part of the 3Delight package.