Loading...
> >

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

1…2021232526…32

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,344

    I too have my sources, Daz Studio devs, and they report that nVidia expects a Spring release (so any time up to June) in a public comment by Alexander Fuchs (Sr. Product Manager Software @ NVIDIA). And as I said above, once it's available it has to be tested and integrated by Daz before we will gt a chnace to see it.

  • Pantros2Pantros2 Posts: 84

    Is there a way other than the DIM to get the Beta? I have an Nvidia 2080ti and need daz 4.11 but my DIM is crashing when I try to download anything.

  • heinzerbrew_f94794efffheinzerbrew_f94794efff Posts: 235

    To my knowlodges no legitmate way. Hopefully, someone proves me ignorant.

  • Richard HaseltineRichard Haseltine Posts: 102,344
    Pantros2 said:

    Is there a way other than the DIM to get the Beta? I have an Nvidia 2080ti and need daz 4.11 but my DIM is crashing when I try to download anything.

    If it's downloading, you can download the zips from the Product Library page and place them in the Install Manager Downloads folder.

  • ChoholeChohole Posts: 33,604
    Rob says

    ""This BETA version is not available as a standalone installer. It must be downloaded and installed using Install Manager." --- https://www.daz3d.com/downloader/customer/files#prod_12000";
  • 3dOutlaw3dOutlaw Posts: 2,480

    Any chance the new version is going to have a way to increase folder size, since we can now assign images to folder icons?  Would make that feature useful!

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

    Any chance the new version is going to have a way to increase folder size, since we can now assign images to folder icons?  Would make that feature useful!

    You'd need to make a featrue request by submitting a Technical Support ticket https://www.daz3d.com/help/help-contact-us - though to answer the question with a guess since images on folders have been around for ages, I wouldn't think a change was "likely".

  • Leonides02Leonides02 Posts: 1,379
    edited March 2019

    Hello everyone!

    Is anyone else finding that the Beta is significantly slower than 4.10? I just tested it with one scene and found...

    • In 4.10 the scene rendered 3765 iterations in 6 minutes and 36 seconds.
    • In 4.11 the scene rendered 3765 iterations in 8 Minutes and 52 Seconds.

    That is about a 34% drop in speed!

    I'll run a couple more tests to see if it's this one scene or what....

    Post edited by Leonides02 on
  • Richard HaseltineRichard Haseltine Posts: 102,344
    Leonides02 said:

    Hello everyone!

    Is anyone else finding that the Beta is significantly slower than 4.10? I just tested it with one scene and found...

    • In 4.10 the scene rendered 3765 iterations in 6 minutes and 36 seconds.
    • In 4.11 the scene rendered 3765 iterations in 8 Minutes and 52 Seconds.

    That is about a 34% drop in speed!

    I'll run a couple more tests to see if it's this one scene or what....

    There's some discussion of this up-thread, but yes there's a bug-fix that can make for slower (but more correct) rendering in some situations.

  • Leonides02Leonides02 Posts: 1,379
    Richard Haseltine said:
    Leonides02 said:

    Hello everyone!

    Is anyone else finding that the Beta is significantly slower than 4.10? I just tested it with one scene and found...

    • In 4.10 the scene rendered 3765 iterations in 6 minutes and 36 seconds.
    • In 4.11 the scene rendered 3765 iterations in 8 Minutes and 52 Seconds.

    That is about a 34% drop in speed!

    I'll run a couple more tests to see if it's this one scene or what....

    There's some discussion of this up-thread, but yes there's a bug-fix that can make for slower (but more correct) rendering in some situations.

    What was the bug?

  • RayDAntRayDAnt Posts: 1,144
    edited March 2019
    Leonides02 said:
    Richard Haseltine said:
    Leonides02 said:

    Hello everyone!

    Is anyone else finding that the Beta is significantly slower than 4.10? I just tested it with one scene and found...

    • In 4.10 the scene rendered 3765 iterations in 6 minutes and 36 seconds.
    • In 4.11 the scene rendered 3765 iterations in 8 Minutes and 52 Seconds.

    That is about a 34% drop in speed!

    I'll run a couple more tests to see if it's this one scene or what....

    There's some discussion of this up-thread, but yes there's a bug-fix that can make for slower (but more correct) rendering in some situations.

    What was the bug?

    There is no big. It's just that the Iray rendering engine has gone through substantial under-the-hood tweaks and feature expansions since the release of DS 4.10 that result in more lifelike renders at the cost of increased per iteration rendering time.

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

    Hello everyone!

    Is anyone else finding that the Beta is significantly slower than 4.10? I just tested it with one scene and found...

    • In 4.10 the scene rendered 3765 iterations in 6 minutes and 36 seconds.
    • In 4.11 the scene rendered 3765 iterations in 8 Minutes and 52 Seconds.

    That is about a 34% drop in speed!

    I'll run a couple more tests to see if it's this one scene or what....

    There's some discussion of this up-thread, but yes there's a bug-fix that can make for slower (but more correct) rendering in some situations.

    What was the bug?

    There is no big. It's just that the Iray rendering engine has gone through substantial under-the-hood tweaks and feature expansions since the release of DS 4.10 that result in more lifelike renders at the cost of increased per iteration rendering time.

    frown The renders looked identical, as far as I could tell. 

    If the tweak increases render time by a third without any appreciable difference in quality, I imagine that will be a problem for most folks.

     

  • RayDAntRayDAnt Posts: 1,144
    Leonides02 said:
    RayDAnt said:
    Leonides02 said:
    Richard Haseltine said:
    Leonides02 said:

    Hello everyone!

    Is anyone else finding that the Beta is significantly slower than 4.10? I just tested it with one scene and found...

    • In 4.10 the scene rendered 3765 iterations in 6 minutes and 36 seconds.
    • In 4.11 the scene rendered 3765 iterations in 8 Minutes and 52 Seconds.

    That is about a 34% drop in speed!

    I'll run a couple more tests to see if it's this one scene or what....

    There's some discussion of this up-thread, but yes there's a bug-fix that can make for slower (but more correct) rendering in some situations.

    What was the bug?

    There is no big. It's just that the Iray rendering engine has gone through substantial under-the-hood tweaks and feature expansions since the release of DS 4.10 that result in more lifelike renders at the cost of increased per iteration rendering time.

    frown The renders looked identical, as far as I could tell. 

    See this post and the ensuing conversation for just one example of the observable differences. If achieving photoreal results is your goal, then you're gonna want the more recent Iray - performance differences and all.

    If the tweak

    It's not just one tweak that has shifted things. It's the combination of many many tweaks, feature additions, and most importantly of all bugfixes spread over years of active development. See ALL of pages 7-23 of "relnotes.pdf" from this recent release of up-to-date Iray documentation directly from Nvidia for the full laundry list of what's changed. It's a dry read, but for those who really wanna know...

  • Richard HaseltineRichard Haseltine Posts: 102,344
    Leonides02 said:
    Richard Haseltine said:
    Leonides02 said:

    Hello everyone!

    Is anyone else finding that the Beta is significantly slower than 4.10? I just tested it with one scene and found...

    • In 4.10 the scene rendered 3765 iterations in 6 minutes and 36 seconds.
    • In 4.11 the scene rendered 3765 iterations in 8 Minutes and 52 Seconds.

    That is about a 34% drop in speed!

    I'll run a couple more tests to see if it's this one scene or what....

    There's some discussion of this up-thread, but yes there's a bug-fix that can make for slower (but more correct) rendering in some situations.

    What was the bug?

    It was related to normals, and making sure they were consistent. it means the shader has to do more work in certain circumstances.

  • Leonides02Leonides02 Posts: 1,379

    I appreciate the explanation, Ray and Richard. Since I'm more interested in speed than fancy caustics, I'll probably stick with 4.10. 

     

     

  • RayDAntRayDAnt Posts: 1,144
    edited March 2019
    Leonides02 said:

    I appreciate the explanation, Ray and Richard. Since I'm more interested in speed than fancy caustics, I'll probably stick with 4.10. 

     

     

    Keep in mind that you can optimize Iray in 4.11 to perform more in line with Iray in 4.10 (at the cost of finer quality of course) by setting optimization parameters like Max Path Length to something other than -1 (disabled.) Also 4.11+ gives you access to a Post Denoiser, which effectively allows you to achieve greater render quality at significantly lower numbers of iterations (by leveraging deep learning - see this guide) once again at the loss of finer quality. But if the quality you are getting in 4.10 is already good enough for your purposes, that shouldn't be a problem.

    Post edited by RayDAnt on
  • JarelJarel Posts: 18
    edited March 2019
    barbult said:

    Glossy Roughness seems to have changed between DS 4.10.0.123 and DS 4.11.0.236. I don't see anything in the change log highlights that I interpreted to explain this. The same glossy roughness map is much glossier in DS 4.11. I used a 16 bit grayscale PNG with black stripes on white background as my glossy roughness map. The lighting is the default HDRI.

    Does anyone else see this?
    Is this an intentional bug fix or an unexpected behavior?

     

    There was a bug with using maps in the glossy, shown by your example.  Nice to see it fixed.

    Post edited by Jarel on
  • dobanymdobanym Posts: 0
    Mr Donoho said:

    I'm still not able to save/retrieve parameter favorite settings.  I had Daz3D v4.10 and v4.11 installed.  I uninstalled both, and reinstalled v4.11 (beta).  I created a new scene and put G8M on it, and click on his head and selected the favorite heart in Bend, Twist, and Side-Side.  I saved the scene, closed the program, reopened, loaded the scene, and the favorites are not checked.  

     

    Favorites don't save here either.

    No matter what i do, after saving, quitting and reloading the file, everything i set as favorites are cleared. 

    Only exceptions are lights and cameras. 

    Favorites at Paramteres, Shaping, Posing, Render settings, etc.. are never saved

     

    This happens in 4.10 and the latest 4.11.0.236 beta too.

     

  • 3dOutlaw3dOutlaw Posts: 2,480
    edited March 2019

    Ugh...I just updated my NVidia driver to get a little more Ooomph for the Witcher 3, and killed my Daz Beta:

    2019-03-15 13:25:22.324 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    2019-03-15 13:25:22.331 Iray Render error: Invalid parameters (NULL pointer).

    Then it finishes with a blank render (on the positive side, it didn't crash, and it was only a 46 sec render!).  Did we have anything on this in the past 23 pages anyone can remember about this, or do I need to rollback the driver?

    ,,,and DS 4.10 is dead as well...argh!

    Post edited by 3dOutlaw on
  • stormqqstormqq Posts: 76

    does this beta works with GTX 1660 TI? 

  • RayDAntRayDAnt Posts: 1,144
    stormqq said:

    does this beta works with GTX 1660 TI? 

    Can't see why not. The 1660 is still technically a Turing card. And I can confirm those absolutely work with this beta.

  • RayDAntRayDAnt Posts: 1,144
    3dOutlaw said:

    Ugh...I just updated my NVidia driver to get a little more Ooomph for the Witcher 3, and killed my Daz Beta:

    2019-03-15 13:25:22.324 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    2019-03-15 13:25:22.331 Iray Render error: Invalid parameters (NULL pointer).

    Then it finishes with a blank render (on the positive side, it didn't crash, and it was only a 46 sec render!).  Did we have anything on this in the past 23 pages anyone can remember about this, or do I need to rollback the driver?

    ,,,and DS 4.10 is dead as well...argh!

    What Driver Version are you updated to? There was some bad code introduced near the end of last year that broke Iray support which was only recently fixed. 419.35 is the most recent good version iirc.

  • 3dOutlaw3dOutlaw Posts: 2,480

    I rolled back to 416.34 and it is working again, but what I upgraded to was 419.35...which is what broke it.  Running a GTX960M.

  • RobotHeadArtRobotHeadArt Posts: 917

    When manipulating objects in the viewport when the Iray Preview mode is on I will randomly get a total crash and the following error.

    2019-03-16 08:22:39.706 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray FATAL - module:category(DB:DATABASE):   1.0   DB     db   fatal: Access of invalid tag 32278

    I upgraded to 419.35 hoping it would resolve it but I am still experiencing the issue.  This doesn't happen the 4.10 release.

  • bluejauntebluejaunte Posts: 1,919
    edited March 2019

    delete

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

    I rolled back to 416.34 and it is working again, but what I upgraded to was 419.35...which is what broke it.  Running a GTX960M.

    Re-install 419.35. Then go into Advanced Render Settings and re-enable your GTX 960M under Photoreal Devices. Sometimes driver updates cause your devices to uncheck themselves from that list - leading to the error reports you were seeing.

  • 3dOutlaw3dOutlaw Posts: 2,480
    edited March 2019
    RayDAnt said:

    Re-install 419.35. Then go into Advanced Render Settings and re-enable your GTX 960M under Photoreal Devices. Sometimes driver updates cause your devices to uncheck themselves from that list - leading to the error reports you were seeing.

    OK, thanks for the idea, but that did not work  :(  I upgraded again, and checked that and the GeForce GTX 960M is checked.  The CPU was not, and I checked that, and it renedered, but only using the CPU....very slowly.  Anyone have any other thoughts before I once again roll back the driver?

    Before upgrade in the log it does:

    Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
    2019-03-15 15:41:55.149 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Initializing local rendering.
    2019-03-15 15:41:55.757 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 1 device(s):
    2019-03-15 15:41:55.772 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 960M)
    2019-03-15 15:41:55.772 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...
    2019-03-15 15:41:55.772 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend progr: CUDA device 0 (GeForce GTX 960M): Processing scene...

    After upgrade it gets:

    Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
    2019-03-18 15:29:16.973 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    2019-03-18 15:29:17.002 Iray Render error: Invalid parameters (NULL pointer).

    Post edited by 3dOutlaw on
  • 3dOutlaw3dOutlaw Posts: 2,480
    edited March 2019

    NM, I am rolling back...I have no patience, LOL!  In case anyone else scrolls by...

    GeForce GTX 960M + Nvidia 419.35 Driver = No Iray  (for me...)

    ...and now I can't seem to get the Post Denoiser to work anymore at all, even after a rollback, the GPU fails and it falls back to CPU render.  Ugh...

    Post edited by 3dOutlaw on
  • 3dOutlaw3dOutlaw Posts: 2,480
    edited March 2019

    Hi @sylvie1998, Yes, I tried that.  It does see/use my NVidia card now, and renders with it (since I rolled back), but if I enable the Post Denoiser, it dies a painful death, as seen in the annotated log, also linked below.

    It seems to infer a memory error, but I rendered this scene last week with the Denoiser (and posted here in the forums) and it worked fine.  It has only been dying since I tried to upgrade, and re-downgraded.

    DS LOG TEXT LINK

    Post edited by 3dOutlaw on
This discussion has been closed.