fatal error Rendering

edited December 1969 in New Users

first of all sorry about my english

fatal error!

Rendering Image
WARNING: QColor::setHsv: HSV parameters out of range
WARNING: QColor::setHsv: HSV parameters out of range
WARNING: QColor::setHsv: HSV parameters out of range
WARNING: QColor::setHsv: HSV parameters out of range
WARNING: QColor::setHsv: HSV parameters out of range
WARNING: QColor::setHsv: HSV parameters out of range
Created RenderCacheBlock
Created RenderCacheBlock

and stop
Please Help

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,783
    edited December 1969

    DAZ Studio, presumably, but what are your render settings? Does a simple primitive (File>New, Create>New Primitive>Accept) render? If so, what is in the scene that won't render?

  • edited December 1969

    my last render.

    demo02.jpg
    900 x 495 - 418K
  • edited December 1969

    DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Documents and Settings\Public\Documents\My DAZ 3D Library\DAZ 3D\DAZStudio4\dz3delight.dll" at 0033:00000000E8908C36, Dz3DelightDll::DSlo_DetailtoStr()+2318262 byte(s)

    -------------------------------------------------------
    log
    Rendering Image
    WARNING: QColor::setHsv: HSV parameters out of range
    WARNING: QColor::setHsv: HSV parameters out of range
    WARNING: QColor::setHsv: HSV parameters out of range
    WARNING: QColor::setHsv: HSV parameters out of range
    WARNING: QColor::setHsv: HSV parameters out of range
    WARNING: QColor::setHsv: HSV parameters out of range
    Created RenderCacheBlock
    Created RenderCacheBlock

  • JimmyC_2009JimmyC_2009 Posts: 8,891
    edited June 2015

    Do you have the DAZ Studio program installed into your 'My DAZ 3D Library' folder, and is that what you meant to do?

    It is normally stored in Program Files, since it is an application.

    Your scene has at least 7 figures visible in it, have you tried rendering a Primitive cube or something smaller to see if that works?

    What are your system specs, CPU, RAM etc.

    Post edited by JimmyC_2009 on
  • mjc1016mjc1016 Posts: 15,001
    edited June 2015

    This is the same problem as

    http://www.daz3d.com/forums/discussion/58479/

    (And there are a couple of others like this floating around)

    The Access_Violation errors are always in the renderer, either Iray or 3Delight and can be with any scene on any hardware...so it is a real bug, not just something in the scene.

    It's also NOT limited to amount of memory used.

    Access_violations are somewhat tricky to track down and may not always be caused by what is showing in the error. The full crash log files are needed to see what's going on...and many times this error can be a permissions related one...or even indicative of bad RAM.

    Please file a support ticket.

    Post edited by mjc1016 on
Sign In or Register to comment.