What is up with these messages I keep getting?
deleted user
Posts: 1,204
I don't know what these messages are.
When I go to render an image I get all these crazy messages.
I don't know what they even mean, or how serious they really are.
Anybody with a clear answer "in English" not in greeklish gets a cookie.
Rendering in 3Delight
Rendering image
Creating shadow map for "SpotLight 1"
3Delight message #43 (Severity 0): R2093: object '/B25SRShoe/B25SSRBackHeel' (displacement 'DAZ/Uber/displacement/omDispStandard', surface 'DAZ/Uber/surface/omShadowSurface') used only 0% of its displacement bound
Creating shadow map for "SpotLight 2"
3Delight message #13 (Severity 1): R2054: primitive (or parts of) '' discarded during eye-split
3Delight message #43 (Severity 0): R2093: object '/B25SRShoe/B25SSRBackHeel' (displacement 'DAZ/Uber/displacement/omDispStandard', surface 'DAZ/Uber/surface/omShadowSurface') used only 0% of its displacement bound
Creating shadow map for "SpotLight 3"
3Delight message #13 (Severity 1): R2054: primitive (or parts of) '' discarded during eye-split
3Delight message #43 (Severity 0): R2093: object '/B25SRShoe/B25SSRBackHeel' (displacement 'DAZ/Uber/displacement/omDispStandard', surface 'DAZ/Uber/surface/omShadowSurface') used only 0% of its displacement bound
Creating shadow map for "SpotLight 4"
3Delight message #13 (Severity 1): R2054: primitive (or parts of) '' discarded during eye-split
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Severity 1 and 0 are simple warnings the render puts out to say it's okay It will work fine but I had to fix it a little bit. The lower the number the better.
I can haz cookie?
"Throws cookie at Jade" As far as milk. Your on your own ; )
This indicates that a part of the geometry was discarded at render time. In almost all cases, this is not a visible part of the geometry, and won't adversely affect the render. They can be discarded for several reasons, but the most common is that the camera is close enough to an object that displaced scenery may pass through the camera's field of view. In such cases, 3Delight discards the displaced polygons which are off-screen unless they're needed for reflection calculations.
Also I would like to know why when you preview lights, its pitch black, even though the render is well lite. Also the eyes move out of aim sometimes looking right above their heads. instead of at them, like I had adjusted for eye contact, but in preview lights their eyes are nowhere near looking at each other.
I hope there is a good reason for that. And not just lazy programming.
This indicates that a part of the geometry was discarded at render time. In almost all cases, this is not a visible part of the geometry, and won't adversely affect the render. They can be discarded for several reasons, but the most common is that the camera is close enough to an object that displaced scenery may pass through the camera's field of view. In such cases, 3Delight discards the displaced polygons which are off-screen unless they're needed for reflection calculations.Nibbles my cookie reading the geek speak that was plainly asked not to be given. Good cookie too. (Wink)
Well here is one example of something I'm having an issue with.
Its really demonic looking! I dont know whats going on.
When I preview lights the eyes go all demonic on me lol!
Also in the other shot. it look me about 14 renders to get the girl to look at her mom because even though it was accurate in the preview with and without the lights, the render always came out where she was looking above her head. OR at her chest or anything BUT eye contact.
This one right here took my about 14 renders...
There is actually quite a few different versions of those error messages that 3Delight likes to cough up, but the cause is the same thing on all of them, badly done Bump & Displacement maps, or if your using the ShaderMixer then pretty much anything you plug into Bump/Displacement will cause it.
The displacement warning is potentially useful, to people who are creating their own maps or shaders, as looking for displacement where there isn't any wastes a little time - spread over a film's worth of frames that can add up to the point where it would be worth reworking the material settings toa void the unnecessary work. What it usually means is that the map being applied to displacement strength doesn't go all of the way to black and white, so the Min and Max values are never reached - that can be down to bad maps, but it can also be down to a good map not using the full dynamic range on one surface while it does on another.
As for the lighting, the OpenGL preview is limited in the number of lights it will show (usually 7) - if you have more lights than that then the ones previewed may not be the ones lighting the area you are looking at. You can turn the lighting preview off, cmd/ctrl-L or Window>Preview lights.
Adding on to what Richard said, some lights don't show properly or at all in preview mode. The 'fix' is what Richard already said, ctl+L or menu... to turn the 'headlamp' back on.
As for the eyes, or anything you want directed to a specific area, there is a function called 'point at.' To use it, you select the item you want directed at something, eyes for instance, go to the 'Parameters' tab and put 'point' in the search box. It will say 'none...' click the button and navigate the tree until you see what you want that object pointing at (camera, other character's eyes, etc...) This is a very handy feature and can be used in a lot of different ways. One could do a whole thread just on creative ways to use the 'point at' function :)