Daz Studio Pro BETA - version 4.11.0.335! (*UPDATED*)

12627282931

Comments

  • 3dOutlaw3dOutlaw Posts: 2,480
    3dOutlaw said:

    Whoops sorry, I have a 960M, which is Maxwell...but it's still called out above.

    The bit you quote refers to Kepler chips under Windows 8, or there's the driver requirement (which 417.x fails to meet).

    If it only refers to Kepler, then there would be no reason to list the Maxwell-based 900m, and again, I tried the 430.39 driver, and it fails (black screen and cannot find GPU device) for both 4.10 and 4.11 (though it works fine for Steam Games).  It seems like the DS Beta's are getting worse in their support of older cards.  Hate to be passed by in the next release.

  • "Integrated Iray 2018.1."

    Does this include the Iray 3d camera ability? I would like to not render every scene twice.

  • 3Diva3Diva Posts: 11,724
    3dOutlaw said:

    4.11.0.335 (April 17, 2019) - IN PROGRESS

    • NVIDIA Iray
      • Integrated Iray 2018.1.3 (312200.3564); see post for more detail
      • REQUIRES NVIDIA Driver 418.81 (or newer); see NVIDIA Driver Downloads
      • Windows 8/8.1 Users:
        • Until a new driver that addresses the issue is released by NVIDIA (potentially early May), rendering with a GPU based on the Kepler microarchitecture is likely to fail and fall back to CPU: (cards with a code name that starts with GK#)

    I run a 960M, but I run Windows 10.  The newest GEF Experience drivers caused a Black Screen render in the Beta for me.  417 drivers do the same.  What is "the issue" stated above?

    ...or is this the issue -> "rendering with a GPU based on the Kepler microarchitecture is likely to fail and fall back to CPU"

    I had installed the latest Public Build Beta and was getting nothing but black screen when I tried to render in Iray. Once I downloaded the latest NVidia driver for my card it fixed the issue. The driver was updated on 4-23, have you tried installing the latest driver since then?

  • Leonides02Leonides02 Posts: 1,379

    Hm. So I haven't downloaded the very newest beta, but at least in the last version Texture Compression doesn't seem to be working at all.

    I've set it at 4000 and 512, and 2 GiB is being sent over to my GPU's no matter what. 

    Can anyone else replicate? 

     

  • Richard HaseltineRichard Haseltine Posts: 102,344
    3dOutlaw said:
    3dOutlaw said:

    Whoops sorry, I have a 960M, which is Maxwell...but it's still called out above.

    The bit you quote refers to Kepler chips under Windows 8, or there's the driver requirement (which 417.x fails to meet).

    If it only refers to Kepler, then there would be no reason to list the Maxwell-based 900m, and again, I tried the 430.39 driver, and it fails (black screen and cannot find GPU device) for both 4.10 and 4.11 (though it works fine for Steam Games).  It seems like the DS Beta's are getting worse in their support of older cards.  Hate to be passed by in the next release.

    The 900M is a family, not a single card, and in that family the 920M is indeed Kepler based though the other members are Maxwel and so not affected. I would try doing a complete uninstall of your driver, then reinstall and see if that helps. For what it's worth, I am using the 419.35 with a 750Ti under Windows 10 and it renders OK so I'd certainly expect your card to be supported.

  • 3dOutlaw3dOutlaw Posts: 2,480
    edited April 2019

    I can try 419.35 will take 20 minutes or so to remove and reinstall.

    430.39 fails with these errors in both 4.10 and 4.11:

    2019-04-26 10:59:17.312 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : GPU 1 (GeForce GTX 960M) with CUDA compute capability 5.0 cannot be used by iray photoreal.
    2019-04-26 10:59:17.312 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : There is no CUDA-capable GPU available to the iray photoreal renderer.
    2019-04-26 10:59:18.326 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Resource assignment for host 0 has changed.
    2019-04-26 10:59:18.758 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Resource assignment for host 0 has changed.
    2019-04-26 10:59:20.574 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : GPU 1 (GeForce GTX 960M) with CUDA compute capability 5.0 cannot be used by iray photoreal.
    2019-04-26 10:59:20.575 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : There is no CUDA-capable GPU available to the iray photoreal renderer.

    ...

    2019-04-26 11:00:37.915 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using batch scheduling, architectural sampler disabled, caustic sampler disabled
    2019-04-26 11:00:37.921 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    2019-04-26 11:00:37.921 Iray Render error: Invalid parameters (NULL pointer).

    EDIT, Nevermind, I have tried 419.35 before to no avail, see:  https://www.daz3d.com/forums/discussion/comment/4441441/#Comment_4441441

    I did not try 419.67 or 425.31 yet, so I will give them a shot.

    Post edited by 3dOutlaw on
  • Richard HaseltineRichard Haseltine Posts: 102,344

    It was more the full uninstall and reinstall that I was stressing - sometimes a driver update will leave bits behind and that can cause issues.

  • 3dOutlaw3dOutlaw Posts: 2,480
    edited April 2019

    I use DDU for uninstall, and make sure to boot into safe mode for a clean uninstall as recommended.  The I choose "Clean Install" from the nVidia Driver, after the reboot is done.  Should be a pretty full/clean un and install.

    • 425.31 failed the same way, using DS 4.10.
    • 419.67 failed the same way, using DS 4.10, and 4.11.

    Rolling back to 4.17 so I can keep using DS 4.10.  sad

    Post edited by 3dOutlaw on
  • RayDAntRayDAnt Posts: 1,144
    3dOutlaw said:

    I use DDU for uninstall, and make sure to boot into safe mode for a clean uninstall as recommended.  The I choose "Clean Install" from the nVidia Driver, after the reboot is done.  Should be a pretty full/clean un and install.

    • 425.31 failed the same way, using DS 4.10.
    • 419.67 failed the same way, using DS 4.10, and 4.11.

    Rolling back to 4.17 so I can keep using DS 4.10.  sad

    Did you un-check and then re-check your GPU(s) under Photoreal Render Devices after updating the driver but before attempting to render? Depending on how major the driver update is it may cause Windows to assign new hardware IDs to your existing graphics card(s). Due to an oversight in the way Daz Studio remembers your preferences, it retains which devices were checked/unchecked between driver updates but with their old hardware IDs - leading to "no available render devices" type errors unless you actively uncheck/check everything after an update.

  • areg5areg5 Posts: 617
    3dOutlaw said:

    I use DDU for uninstall, and make sure to boot into safe mode for a clean uninstall as recommended.  The I choose "Clean Install" from the nVidia Driver, after the reboot is done.  Should be a pretty full/clean un and install.

    • 425.31 failed the same way, using DS 4.10.
    • 419.67 failed the same way, using DS 4.10, and 4.11.

    Rolling back to 4.17 so I can keep using DS 4.10.  sad

    Also, I would avoid ... like the plague ... the Geoforce Experience.  I've had horrible luck with that.  It gives me BSOD.  I do basically what you did, and make absolutely sure I only install the drivers.  You still get the control panel with that.  And definitely clean install.  Then you need to restart.

  • marblemarble Posts: 7,500
    areg5 said:
    3dOutlaw said:

    I use DDU for uninstall, and make sure to boot into safe mode for a clean uninstall as recommended.  The I choose "Clean Install" from the nVidia Driver, after the reboot is done.  Should be a pretty full/clean un and install.

    • 425.31 failed the same way, using DS 4.10.
    • 419.67 failed the same way, using DS 4.10, and 4.11.

    Rolling back to 4.17 so I can keep using DS 4.10.  sad

    Also, I would avoid ... like the plague ... the Geoforce Experience.  I've had horrible luck with that.  It gives me BSOD.  I do basically what you did, and make absolutely sure I only install the drivers.  You still get the control panel with that.  And definitely clean install.  Then you need to restart.

    Precisely what I do too - GeForce Experience seems to be aimed at gamers and I am certainly not that. So drivers only (clean install) and uncheck the rest.

  • 3dOutlaw3dOutlaw Posts: 2,480
    RayDAnt said:

    Did you un-check and then re-check your GPU(s) under Photoreal Render Devices after updating the driver but before attempting to render? Depending on how major the driver update is it may cause Windows to assign new hardware IDs to your existing graphics card(s). Due to an oversight in the way Daz Studio remembers your preferences, it retains which devices were checked/unchecked between driver updates but with their old hardware IDs - leading to "no available render devices" type errors unless you actively uncheck/check everything after an update.

    I did that with 430.39, but not with the lat two.  I never have to do that when I go all the way back to 417, it just works.  For the last two I did the final reboot again, and no help.  I have chose not to add the experience as well, during these tests, but I will eventually add it back, as I am a gamer, and I like it, and it always works well for me.

    Thanks all for the help.  I will sit with 417 again until this "fix" they talk abut in the release notes in May.  It's obvious something ain't right for my card, the new drivers and DS.

     

  • If anyone could do an accurate speed test comparing the newest beta to the previous one and 4.10 that would be highly appreciated - maybe even with RTX cards?

    After seeing all this talk about issues I'm not sure it's worth updating from the previous beta build if there isn't any signifcant speed increase for the RTX cards.

  • RayDAntRayDAnt Posts: 1,144

    If anyone could do an accurate speed test comparing the newest beta to the previous one and 4.10 that would be highly appreciated - maybe even with RTX cards?

    After seeing all this talk about issues I'm not sure it's worth updating from the previous beta build if there isn't any signifcant speed increase for the RTX cards.

    Working on it. Check back here or in the Sickleyield benchmarking thread early next week for results (have a boatload to do before Monday.)

  • Leonides02Leonides02 Posts: 1,379
    edited April 2019

    Not sure if it's possible, but it'd be great if we could save both a denoised and noised version of our renders. 

    Nvidia's algorithm can be too aggressive even on renders with 10,000+ iterations. I'm currently using the denoising feature outside of DAZ so I can combine the images in photoshop and get the best of both worlds. 

    Post edited by Leonides02 on
  • algovincianalgovincian Posts: 2,635

    Not sure if it's possible, but it'd be great if we could save both a denoised and noised version of our renders. 

    Nvidia's algorithm can be too aggressive even on renders with 10,000+ iterations. I'm currently using the denoising feature outside of DAZ so I can combine the images in photoshop and get the best of both worlds. 

    I agree completely. Non-destructive editing is always the way to go if possible. I believe you’re not losing anything since the denoising algorithm is only working with the 8-bit output and no other information from Iray (no canvases). This is my understanding of the current situation.

    I don’t render using Iray often, but when I do I always render out a 32-bit beauty canvas and tonemap/denoise outside of DS. 

    - Greg

  • Leonides02Leonides02 Posts: 1,379

    I believe you’re not losing anything since the denoising algorithm is only working with the 8-bit output and no other information from Iray (no canvases). This is my understanding of the current situation.

    This is correct, but also baffling. Outside of Daz Studio, I use the denoiser on 32-bit HDR canvases to great effect. But being able to get both the noised / denoised from Daz would save me a couple steps!

  • Richard HaseltineRichard Haseltine Posts: 102,344

    Not sure if it's possible, but it'd be great if we could save both a denoised and noised version of our renders. 

    Nvidia's algorithm can be too aggressive even on renders with 10,000+ iterations. I'm currently using the denoising feature outside of DAZ so I can combine the images in photoshop and get the best of both worlds. 

    try File>Save Last Render, which will save without closing the render, then toggle the denoiser and resume the render for a few iterations so it updates and save that.

  • PadonePadone Posts: 3,778
    edited April 2019
    pdxtobin said:

    Here is my experience so far with the denoiser..  Longer render time and much, much less detail.

    I don't know .. that seems more a blur than a denoiser. Is the nvidia denoiser really working like that ? Then there's nothing more there than applying a blur filter in GIMP. A denoiser should be aware of bump maps and be able to distinguish between details and noise by analyzing the rendering buffers. That doesn't seem to do so.

     

    EDIT. I'm wondering if 4.11 is passing all the rendering buffers to the denoiser or just the beauty canvas .. that would explain why the denoiser performs so bad.

    Post edited by Padone on
  • Leonides02Leonides02 Posts: 1,379
    edited April 2019

    try File>Save Last Render, which will save without closing the render, then toggle the denoiser and resume the render for a few iterations so it updates and save that.

    Clever, Richard! I'll try that tonight and see how it goes. Thank you for the suggestion.

    Padone said:

    I don't know .. that seems more a blur than a denoiser. Is the nvidia denoiser really working like that ? Then there's nothing more there than applying a blur filter in GIMP. A denoiser should be aware of bump maps and be able to distinguish between details and noise by analyzing the rendering buffers. That doesn't seem to do so.

    EDIT. I'm wondering if 4.11 is passing all the rendering buffers to the denoiser or just the beauty canvas .. that would explain why the denoiser performs so bad.

    I don't believe it's passing over anything other than the beauty pass. Unfortunately, skin details (pores) and even clothing textures tend to get obliterated. The denoiser works really well on inorganic items and shadowed areas. 

    Post edited by Leonides02 on
  • areg5areg5 Posts: 617

    Weird bugs:  I've already menitioned that the camera PAN tends to stck.  Also weird is that the undo feature is a bit off.  Sometime it undoes something from a few changes before instead of the latest change.

  • barbultbarbult Posts: 24,754
    areg5 said:

    Weird bugs:  I've already menitioned that the camera PAN tends to stck.  Also weird is that the undo feature is a bit off.  Sometime it undoes something from a few changes before instead of the latest change.

    Not every action is undoable.

  • Leonides02Leonides02 Posts: 1,379
    barbult said:

    Not every action is undoable.

    Word to live by!

  • Ghosty12Ghosty12 Posts: 2,065
    edited April 2019

    Well learnt one thing do not install over a previous beta, as it completely borked the Studio's layout. And that was mainly due to DiM not installing it correctly, had to delete the beta folder entirely before I could get DiM to install this current build properly..

     

    Post edited by Ghosty12 on
  • When 4.11 Release???

    Can't wait it,because my DIM never work,can't link to the sever,and can't download the beta version...LOL~~~

  • areg5areg5 Posts: 617

    When 4.11 Release???

    Can't wait it,because my DIM never work,can't link to the sever,and can't download the beta version...LOL~~~

    Sure it can.  You just need to make sure that Public download is checked in settings.

  • Not sure if it's possible, but it'd be great if we could save both a denoised and noised version of our renders. 

    Nvidia's algorithm can be too aggressive even on renders with 10,000+ iterations. I'm currently using the denoising feature outside of DAZ so I can combine the images in photoshop and get the best of both worlds. 

    try File>Save Last Render, which will save without closing the render, then toggle the denoiser and resume the render for a few iterations so it updates and save that.

    I never even knew that...thanks for sharing Richard!

  • aleyciafrancisaleyciafrancis Posts: 6
    edited April 2019
    areg5 said:

    When 4.11 Release???

    Can't wait it,because my DIM never work,can't link to the sever,and can't download the beta version...LOL~~~

    Sure it can.  You just need to make sure that Public download is checked in settings.

    Thanks for the reply! but my problem is thay DIM can't even connect to the sever...LOL~~~

    Post edited by Richard Haseltine on
  • Leonides02Leonides02 Posts: 1,379

    Not sure if it's possible, but it'd be great if we could save both a denoised and noised version of our renders. 

    Nvidia's algorithm can be too aggressive even on renders with 10,000+ iterations. I'm currently using the denoising feature outside of DAZ so I can combine the images in photoshop and get the best of both worlds. 

    try File>Save Last Render, which will save without closing the render, then toggle the denoiser and resume the render for a few iterations so it updates and save that.

    Hm. Did this, but unfotunately it doesn't save any canvases. I need the HDR beauty pass. 

  • RayDAntRayDAnt Posts: 1,144
    areg5 said:

    When 4.11 Release???

    Can't wait it,because my DIM never work,can't link to the sever,and can't download the beta version...LOL~~~

    Sure it can.  You just need to make sure that Public download is checked in settings.

    Thanks for the reply! but my problem is thay DIM can't even connect to the sever...LOL~~~

     

    Have you checked your firewall permissions? DIM can't do anything unless it has authorization to contact the outside world.

This discussion has been closed.