Loading...
> >

Does anyone understand this?? SOLVED

TrishTrish Posts: 2,625
edited January 2014 in New Users

I don't know what this means....It came up while I was rendering.....Thanks Trish

Message.jpg
381 x 386 - 88K
Post edited by Trish on

Comments

  • JaderailJaderail Posts: 0
    edited December 1969

    Severity 1 2 and 3 errors are Render Engine code that mean what was just sent to it is now (NORMALY) done another way. They are fixed on the fly by the render engine if do able (99.9% are). Most of the time the render is FINE. It's really code in the Render engine for the coders. I see that most often when I use a shader on a item that is a few steps older than the render engine now included in DAZ Studio. Unless your render FAILS you can ignore low numbered errors from the render engine.

  • TrishTrish Posts: 2,625
    edited December 1969

    Ok thanks I will wait to see if it finishes the render.....

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    In that particular case, though, there may be a problem in the render...with an unexpected result.

    There's a ShaderMixer shader being used that has some function that is trying to assign a 'float' (numeric) value to another function's input that is set to receive a color value. Depending on what those functions are, the results could be fine...or totally messed up. Usually a float value in a color slot translates to grey with 0 being black and 1 being white...and that may be acceptable for whatever the shader is doing.

    But it, in the scheme of things, isn't that big of a deal...as far as 3Delight is concerned.

  • mark128mark128 Posts: 1,029
    edited December 1969

    I see these kind of errors every so often.

    What I do is:

    1) Save the scene
    2) Exit DAZ Studio
    3) Go to the task manager and wait for the DAZ studio process to really quit. This can take anywhere from 1 sec to a few minutes depending on how big the scene was.
    4) Restart DAZ Studio
    5) Open the scene again
    6) Do the render again.

    I think this is some problem with shaders in the temporary work area. Letting the DAZ process completely quit makes sure this area gets cleaned up. If you start another DAZ process too quickly, before the previous one has really quit, it can sometimes corrupt files in the temporary area. This at least is my theory.

  • TrishTrish Posts: 2,625
    edited December 1969

    Thanks so much everyone... I ended up moving the whole thing to Bryce...appreciate the help...Trish

Sign In or Register to comment.