Loading...
> >

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

1…4647495152…74

Comments

  • marblemarble Posts: 7,500
    Leonides02 said:
    RayDAnt said:
    Leonides02 said:

    Has anyone explained what the new SSIM options mean under "Progressive Rendering?"

    Here's what the official Iray documentation has to say about it (there's info there about the new Matte Fog features as well.) It's actually been a documented feature there for something like 2-3 months. Been Keen to see how it performs under DS, but haven't gotten around to playing with it yet. One thing to keep in mind is that it is inherently incompatible with the ai denoiser. You can use one or the other, but not both at once.

    Hm... So it's a new denoiser option...?

    Funny how we read the same thing and come to different conclusions. I understood it (SSIM) to be a time-to-completion predictor though it uses the same AI as the denoiser so they can't both run at the same time. I wouldn't bet on my understanding being correct, however.

  • RayDAntRayDAnt Posts: 1,135
    edited April 2020
    Leonides02 said:
    RayDAnt said:
    Leonides02 said:

    Has anyone explained what the new SSIM options mean under "Progressive Rendering?"

    Here's what the official Iray documentation has to say about it (there's info there about the new Matte Fog features as well.) It's actually been a documented feature there for something like 2-3 months. Been Keen to see how it performs under DS, but haven't gotten around to playing with it yet. One thing to keep in mind is that it is inherently incompatible with the ai denoiser. You can use one or the other, but not both at once.

    Hm... So it's a new denoiser option...?

    Not exactly. It's an ai-driven replacement/upgrade of the Convergence Quality estimate mechanism. Kind of like how the denoiser is essentially an ai-driven replacement/upgrade of the Fireflies filter.

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

    Has anyone explained what the new SSIM options mean under "Progressive Rendering?"

    Here's what the official Iray documentation has to say about it (there's info there about the new Matte Fog features as well.) It's actually been a documented feature there for something like 2-3 months. Been Keen to see how it performs under DS, but haven't gotten around to playing with it yet. One thing to keep in mind is that it is inherently incompatible with the ai denoiser. You can use one or the other, but not both at once.

    Hm... So it's a new denoiser option...?

    Funny how we read the same thing and come to different conclusions. I understood it (SSIM) to be a time-to-completion predictor though it uses the same AI as the denoiser so they can't both run at the same time. I wouldn't bet on my understanding being correct, however.

    Likewise! I just ran a render with the option on, but I don't see a "timer" of any kind anywhere... Nor did I see any remarkable denoising, LOL.

  • prixatprixat Posts: 1,588
    edited April 2020

    You'll find the estimate in the render progress history.

    ...and, like the denoiser, there is no direct feedback to the renderer (yet?) so you have to stop the render manually.

     

    SSIM.jpg
    648 x 603 - 192K
    Post edited by prixat on
  • Leonides02Leonides02 Posts: 1,379
    prixat said:

    You'll find the estimate in the render progress history.

    ...and, like the denoiser, there is no direct feedback to the renderer (yet?) so you have to stop the render manually.

     

    Ah, thank you.

    Seems like an odd feature... Doesn't the renderer stop automatically when the convergence is reached?

  • HeckbarthHeckbarth Posts: 64

    Congrats to the new release! Looks promising to me so far.

    Question: if I want to use iray server (https://www.irayplugins.com/iray-server/try.php) for batch rendering - which version am I supposed to take?

     

    Thanks and best wishes,

    Heckbarth

  • SevrinSevrin Posts: 6,306

    Why doesn't Daz put up a quick demo video of new features like this?

  • marblemarble Posts: 7,500
    edited April 2020

    I've just noticed a problem with saving a short animation using the new timeline (I'm on this latest 4.12.1.109 beta). 

    I created an animation and rendered it, saved the scene and quit DAZ Studio. The render came out as expected but I noticed things I wanted to tweak so I re-loaded the scene and moved a hand and one leg. Then I rendered again but the finished animation had changed form the original. Some animated body parts and attachments (hair, for example) which had animated movement were now static. I'm trying to narrow it down but it seems to be a problem with attachments and with some morphs such as Zev0's Glute Control - I had animated some squish effects whuch were all cleared upon reload.

    Does any of this make sense? Would it help to animate with KeyMate/GraphMate instead?

    BTW: I have the Key Creation Scope set to "Node". I don't understand the options, however.

    Post edited by marble on
  • Lantia VertelLantia Vertel Posts: 19

    In this version one of each 2 canvas writes fails in my renders:

    Iray (Iteration) : 44Iray (Iteration) : 46Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 51Iray (Iteration) : 53Iray (Iteration) : 59Iray (Error) : 2.49% of image convergedIray (Iteration) : 61Iray (Iteration) : 68Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 71Iray (Iteration) : 79Iray (Iteration) : 82Iray (Error) : 3.85% of image convergedIray (Iteration) : 92Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 96Iray (Iteration) : 107Iray (Iteration) : 111Iray (Canvas) : :Render target canvas was written.Iray (Error) : 5.14% of image convergedIray (Iteration) : 122Iray (Iteration) : 126Iray (Iteration) : 137Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 141Iray (Error) : 6.60% of image convergedIray (Iteration) : 153Iray (Iteration) : 157Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 170Iray (Iteration) : 175Iray (Error) : 8.54% of image convergedIray (Iteration) : 189Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 194Iray (Iteration) : 210Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 215Iray (Error) : 10.65% of image convergedIray (Iteration) : 232Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 238Iray (Iteration) : 257Iray (Canvas) : :Render target canvas was written.Iray (Error) : 12.23% of image convergedIray (Iteration) : 264Iray (Iteration) : 271Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 292Iray (Error) : 14.23% of image convergedIray (Iteration) : 300Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 323Iray (Error) : 16.22% of image convergedIray (Iteration) : 332Iray (Canvas) : :Render target canvas was written.

    I have a 2080Ti and a 1080 with the "old" post-denoiser enabled, so I guess the 1080 is failing because the lack of tensor cores, however, this didn't happe before.

  • Richard HaseltineRichard Haseltine Posts: 100,839
    Lantia Vertel said:

    In this version one of each 2 canvas writes fails in my renders:

    Iray (Iteration) : 44Iray (Iteration) : 46Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 51Iray (Iteration) : 53Iray (Iteration) : 59Iray (Error) : 2.49% of image convergedIray (Iteration) : 61Iray (Iteration) : 68Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 71Iray (Iteration) : 79Iray (Iteration) : 82Iray (Error) : 3.85% of image convergedIray (Iteration) : 92Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 96Iray (Iteration) : 107Iray (Iteration) : 111Iray (Canvas) : :Render target canvas was written.Iray (Error) : 5.14% of image convergedIray (Iteration) : 122Iray (Iteration) : 126Iray (Iteration) : 137Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 141Iray (Error) : 6.60% of image convergedIray (Iteration) : 153Iray (Iteration) : 157Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 170Iray (Iteration) : 175Iray (Error) : 8.54% of image convergedIray (Iteration) : 189Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 194Iray (Iteration) : 210Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 215Iray (Error) : 10.65% of image convergedIray (Iteration) : 232Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 238Iray (Iteration) : 257Iray (Canvas) : :Render target canvas was written.Iray (Error) : 12.23% of image convergedIray (Iteration) : 264Iray (Iteration) : 271Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 292Iray (Error) : 14.23% of image convergedIray (Iteration) : 300Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 323Iray (Error) : 16.22% of image convergedIray (Iteration) : 332Iray (Canvas) : :Render target canvas was written.

    I have a 2080Ti and a 1080 with the "old" post-denoiser enabled, so I guess the 1080 is failing because the lack of tensor cores, however, this didn't happe before.

    I don't see any failures there - it's reporting progress (the proportion of pixels thata re converged) and that it has updated the canvas, separate things.

  • RayDAntRayDAnt Posts: 1,135
    edited April 2020
    Lantia Vertel said:

    In this version one of each 2 canvas writes fails in my renders:

    Iray (Iteration) : 44Iray (Iteration) : 46Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 51Iray (Iteration) : 53Iray (Iteration) : 59Iray (Error) : 2.49% of image convergedIray (Iteration) : 61Iray (Iteration) : 68Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 71Iray (Iteration) : 79Iray (Iteration) : 82Iray (Error) : 3.85% of image convergedIray (Iteration) : 92Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 96Iray (Iteration) : 107Iray (Iteration) : 111Iray (Canvas) : :Render target canvas was written.Iray (Error) : 5.14% of image convergedIray (Iteration) : 122Iray (Iteration) : 126Iray (Iteration) : 137Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 141Iray (Error) : 6.60% of image convergedIray (Iteration) : 153Iray (Iteration) : 157Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 170Iray (Iteration) : 175Iray (Error) : 8.54% of image convergedIray (Iteration) : 189Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 194Iray (Iteration) : 210Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 215Iray (Error) : 10.65% of image convergedIray (Iteration) : 232Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 238Iray (Iteration) : 257Iray (Canvas) : :Render target canvas was written.Iray (Error) : 12.23% of image convergedIray (Iteration) : 264Iray (Iteration) : 271Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 292Iray (Error) : 14.23% of image convergedIray (Iteration) : 300Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 323Iray (Error) : 16.22% of image convergedIray (Iteration) : 332Iray (Canvas) : :Render target canvas was written.

    I have a 2080Ti and a 1080 with the "old" post-denoiser enabled, so I guess the 1080 is failing because the lack of tensor cores, however, this didn't happe before.

    It's just a logfile formatting change. One of the changes made to DS this release was to increase the verbosity of logfile writes by the Iray plugin while doing things. Hence why you are now seeing those "(Iteration/Canvas/Error/etc)" prefixes before each line. Those are the names of the internal Iray function classes responsible for generating that data. The "(Error)" before the convergence update lines is a misnomer. That just means that it technically uses a generic "error" function class to communicate that data to screen. Most likely because there was no better fit for it category-wise, and because giving it its own unique class would've been a waste of resources.

    I have a single Titan RTX-based system and I get exactly the same output. And rendering behavior remains unchanged from the last update.

     

    ETA: Also - just to be clear - there is no "new" post-denoiser in this release (although the de-noiser itself has been updated, as per current Iray changelogs.) The SSIM predictor is a potential experimental replacement for Iray's attempts to track rendering convergance.

    Post edited by RayDAnt on
  • Leonides02Leonides02 Posts: 1,379
    prixat said:

    You'll find the estimate in the render progress history.

    ...and, like the denoiser, there is no direct feedback to the renderer (yet?) so you have to stop the render manually.

     

    Oddly, I don't see this....

    Maybe it's because I'm using canvases?

  • RayDAntRayDAnt Posts: 1,135
    edited April 2020
    Leonides02 said:
    prixat said:

    You'll find the estimate in the render progress history.

    ...and, like the denoiser, there is no direct feedback to the renderer (yet?) so you have to stop the render manually.

     

    Oddly, I don't see this....

    Maybe it's because I'm using canvases?

    Did you select on for both "Post SSIM Available" and "Post SSIM Enable" under Progressive Rendering settings? Just tried a render using Canvases and all expected info was there in the expanded render progress history window.

     

    For reference, your raw log file should look something like this:

    2020-04-23 17:33:10.228 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Scene processed in 0.243s2020-04-23 17:33:10.230 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Allocated 30.903 MiB for frame buffer2020-04-23 17:33:10.234 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Allocated 1.727 GiB of work space (2048k active samples in 0.000s)2020-04-23 17:33:10.234 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Used for display, optimizing for interactive usage (performance could be sacrificed)2020-04-23 17:33:10.472 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Allocating 1-layer frame buffer2020-04-23 17:33:10.559 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM Predictor uses CUDA device 0, "TITAN RTX" (7.5), buffers: fp32, cudnn v7500, cudart v100102020-04-23 17:33:10.608 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : layers created for resolution 928 928, inp 6, outp 1, cuDNN memory 39.4 MiB, total 409.0 MiB2020-04-23 17:33:10.725 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9792982020-04-23 17:33:11.116 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.1166592020-04-23 17:33:11.124 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00001 iterations after 1.143s.2020-04-23 17:33:11.780 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9826372020-04-23 17:33:11.785 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 2: SSIM value 0.982637, target SSIM value 0.980000 reached.2020-04-23 17:33:11.874 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.2482022020-04-23 17:33:11.876 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00002 iterations after 1.895s.2020-04-23 17:33:12.587 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.7293152020-04-23 17:33:12.590 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00008 iterations after 2.610s.2020-04-23 17:33:13.449 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8070292020-04-23 17:33:13.451 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00012 iterations after 3.471s.2020-04-23 17:33:14.330 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8607272020-04-23 17:33:14.334 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 17: SSIM value 0.860727, expected convergence to 0.980000 in iteration 2312020-04-23 17:33:14.335 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00017 iterations after 4.354s.2020-04-23 17:33:15.228 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8742072020-04-23 17:33:15.230 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 22: SSIM value 0.874207, expected convergence to 0.980000 in iteration 2622020-04-23 17:33:15.230 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00022 iterations after 5.250s.2020-04-23 17:33:16.111 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8908082020-04-23 17:33:16.114 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 27: SSIM value 0.890808, expected convergence to 0.980000 in iteration 2292020-04-23 17:33:16.119 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00027 iterations after 6.139s.2020-04-23 17:33:16.970 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8913072020-04-23 17:33:16.975 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 32: SSIM value 0.891307, expected convergence to 0.980000 in iteration 2782020-04-23 17:33:16.975 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00032 iterations after 6.995s.2020-04-23 17:33:17.888 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8941662020-04-23 17:33:17.894 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 37: SSIM value 0.894166, expected convergence to 0.980000 in iteration 3232020-04-23 17:33:17.894 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00037 iterations after 7.913s.2020-04-23 17:33:18.802 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9013842020-04-23 17:33:18.807 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 42: SSIM value 0.901384, expected convergence to 0.980000 in iteration 3472020-04-23 17:33:18.813 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00042 iterations after 8.832s.2020-04-23 17:33:19.678 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9024852020-04-23 17:33:19.681 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 47: SSIM value 0.902485, expected convergence to 0.980000 in iteration 4302020-04-23 17:33:19.681 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00047 iterations after 9.700s.2020-04-23 17:33:20.529 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9078962020-04-23 17:33:20.532 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 52: SSIM value 0.907896, expected convergence to 0.980000 in iteration 4502020-04-23 17:33:20.532 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00052 iterations after 10.551s.2020-04-23 17:33:20.606 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00057 iterations after 10.625s.2020-04-23 17:33:22.514 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.908447

     

    And the render progress history window like this:

    Iray (Iteration) : 154Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.55% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 1396Iray (Iteration) : 170Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.53% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 1668Iray (Iteration) : 188Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.60% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 1846Iray (Iteration) : 208Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.66% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 1974Iray (Iteration) : 230Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.71% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 2138Iray (Iteration) : 255Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.79% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 2178Iray (Iteration) : 282Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.81% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 2413Iray (Iteration) : 312Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.87% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 2509Iray (Iteration) : 345Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.94% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 2565Iray (Iteration) : 382Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.92% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 2950Iray (Iteration) : 422Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.01% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 2976Iray (Iteration) : 466Iray (Canvas) : :Render target canvas was written.Iray (Error) : 96.99% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 3354Iray (Iteration) : 515Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.00% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 3802Iray (Iteration) : 569Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.14% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 3550Iray (Iteration) : 628Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.16% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 3757Iray (Iteration) : 692Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.27% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 3750Iray (Iteration) : 763Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.31% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 3881Iray (Iteration) : 842Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.37% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 4066Iray (Iteration) : 930Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.46% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 4065Iray (Iteration) : 1026Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.49% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 4394Iray (Iteration) : 1133Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.54% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 4721Iray (Iteration) : 1251Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.58% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 5046Iray (Iteration) : 1381Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 1494Iray (Canvas) : :Render target canvas was written.Iray (Error) : 97.69% of image convergedIray (SSIM) : Estimated number of samples at which the desired convergence will be reached.: 5198Iray (Iteration) : 1580Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 1643Iray (Canvas) : :Render target canvas was written.Iray (Iteration) : 1688Iray (Canvas) : :Render target canvas was written.

     

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

    You'll find the estimate in the render progress history.

    ...and, like the denoiser, there is no direct feedback to the renderer (yet?) so you have to stop the render manually.

     

    Oddly, I don't see this....

    Maybe it's because I'm using canvases?

    Did you select on for both "Post SSIM Available" and "Post SSIM Enable" under Progressive Rendering settings? Just tried a render using Canvases and all expected info was there in the expanded render progress history window.

     

    For reference, your raw log file should look something like this:

    2020-04-23 17:33:10.228 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Scene processed in 0.243s2020-04-23 17:33:10.230 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Allocated 30.903 MiB for frame buffer2020-04-23 17:33:10.234 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Allocated 1.727 GiB of work space (2048k active samples in 0.000s)2020-04-23 17:33:10.234 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (TITAN RTX): Used for display, optimizing for interactive usage (performance could be sacrificed)2020-04-23 17:33:10.472 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Allocating 1-layer frame buffer2020-04-23 17:33:10.559 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM Predictor uses CUDA device 0, "TITAN RTX" (7.5), buffers: fp32, cudnn v7500, cudart v100102020-04-23 17:33:10.608 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : layers created for resolution 928 928, inp 6, outp 1, cuDNN memory 39.4 MiB, total 409.0 MiB2020-04-23 17:33:10.725 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9792982020-04-23 17:33:11.116 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.1166592020-04-23 17:33:11.124 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00001 iterations after 1.143s.2020-04-23 17:33:11.780 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9826372020-04-23 17:33:11.785 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 2: SSIM value 0.982637, target SSIM value 0.980000 reached.2020-04-23 17:33:11.874 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.2482022020-04-23 17:33:11.876 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00002 iterations after 1.895s.2020-04-23 17:33:12.587 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.7293152020-04-23 17:33:12.590 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00008 iterations after 2.610s.2020-04-23 17:33:13.449 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8070292020-04-23 17:33:13.451 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00012 iterations after 3.471s.2020-04-23 17:33:14.330 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8607272020-04-23 17:33:14.334 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 17: SSIM value 0.860727, expected convergence to 0.980000 in iteration 2312020-04-23 17:33:14.335 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00017 iterations after 4.354s.2020-04-23 17:33:15.228 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8742072020-04-23 17:33:15.230 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 22: SSIM value 0.874207, expected convergence to 0.980000 in iteration 2622020-04-23 17:33:15.230 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00022 iterations after 5.250s.2020-04-23 17:33:16.111 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8908082020-04-23 17:33:16.114 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 27: SSIM value 0.890808, expected convergence to 0.980000 in iteration 2292020-04-23 17:33:16.119 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00027 iterations after 6.139s.2020-04-23 17:33:16.970 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8913072020-04-23 17:33:16.975 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 32: SSIM value 0.891307, expected convergence to 0.980000 in iteration 2782020-04-23 17:33:16.975 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00032 iterations after 6.995s.2020-04-23 17:33:17.888 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.8941662020-04-23 17:33:17.894 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 37: SSIM value 0.894166, expected convergence to 0.980000 in iteration 3232020-04-23 17:33:17.894 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00037 iterations after 7.913s.2020-04-23 17:33:18.802 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9013842020-04-23 17:33:18.807 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 42: SSIM value 0.901384, expected convergence to 0.980000 in iteration 3472020-04-23 17:33:18.813 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00042 iterations after 8.832s.2020-04-23 17:33:19.678 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9024852020-04-23 17:33:19.681 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 47: SSIM value 0.902485, expected convergence to 0.980000 in iteration 4302020-04-23 17:33:19.681 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00047 iterations after 9.700s.2020-04-23 17:33:20.529 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.9078962020-04-23 17:33:20.532 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : Iteration 52: SSIM value 0.907896, expected convergence to 0.980000 in iteration 4502020-04-23 17:33:20.532 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00052 iterations after 10.551s.2020-04-23 17:33:20.606 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00057 iterations after 10.625s.2020-04-23 17:33:22.514 Iray [INFO] - POST:RENDER ::   1.0   POST   rend info : SSIM value: 0.908447

     

    And the render progress history window like this:

     

    Oh, I see it's working.... The "issue" was I only needed 13 passes to reach the "desired level of convergence," LOL.

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,207

    is there some reason DAZ studio public build freezes up when I try to delete something from a preload scene?

    for hours!

    is Quarter 4 instance from the Colosseum BTW, I just want one fully loaded quarter, still 2 more to go if this ever deletes, rebooted and tried twice as did kill it in taskmanager against advice above when it whited out before

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,207
    edited April 2020

    my finger is hovering the mouse pointer on end task angry

    Post edited by WendyLuvsCatz on
  • DoctorJellybeanDoctorJellybean Posts: 8,464
    WendyLuvsCatz said:

    is there some reason DAZ studio public build freezes up when I try to delete something from a preload scene?

    for hours!

    is Quarter 4 instance from the Colosseum BTW, I just want one fully loaded quarter, still 2 more to go if this ever deletes, rebooted and tried twice as did kill it in taskmanager against advice above when it whited out before

    No problem for me. I deleted all the Quarters except Quarter 1, took about a min.

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,207
    DoctorJellybean said:
    WendyLuvsCatz said:

    is there some reason DAZ studio public build freezes up when I try to delete something from a preload scene?

    for hours!

    is Quarter 4 instance from the Colosseum BTW, I just want one fully loaded quarter, still 2 more to go if this ever deletes, rebooted and tried twice as did kill it in taskmanager against advice above when it whited out before

    No problem for me. I deleted all the Quarters except Quarter 1, took about a min.

    thanks for that

    so something is going on here, my system not overloaded

    RAM is only half and CPU 29% 0 GPU load

    it is just hanging 

  • DoctorJellybeanDoctorJellybean Posts: 8,464
    WendyLuvsCatz said:
    DoctorJellybean said:
    WendyLuvsCatz said:

    is there some reason DAZ studio public build freezes up when I try to delete something from a preload scene?

    for hours!

    is Quarter 4 instance from the Colosseum BTW, I just want one fully loaded quarter, still 2 more to go if this ever deletes, rebooted and tried twice as did kill it in taskmanager against advice above when it whited out before

    No problem for me. I deleted all the Quarters except Quarter 1, took about a min.

    thanks for that

    so something is going on here, my system not overloaded

    RAM is only half and CPU 29% 0 GPU load

    it is just hanging 

    Anything in the log?

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,207
    DoctorJellybean said:
    WendyLuvsCatz said:
    DoctorJellybean said:
    WendyLuvsCatz said:

    is there some reason DAZ studio public build freezes up when I try to delete something from a preload scene?

    for hours!

    is Quarter 4 instance from the Colosseum BTW, I just want one fully loaded quarter, still 2 more to go if this ever deletes, rebooted and tried twice as did kill it in taskmanager against advice above when it whited out before

    No problem for me. I deleted all the Quarters except Quarter 1, took about a min.

    thanks for that

    so something is going on here, my system not overloaded

    RAM is only half and CPU 29% 0 GPU load

    it is just hanging 

    Anything in the log?

    it is still hanging, I haven't clicked end task yetdevil

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,207
    edited April 2020

    and no 

    just the last thing loaded looking in application data

    gonna click that button soon and fire up my Win7 machine!

    Capture.JPG
    718 x 698 - 170K
    Capture2.JPG
    3840 x 1168 - 725K
    Post edited by WendyLuvsCatz on
  • WendyLuvsCatzWendyLuvsCatz Posts: 38,207
    edited April 2020

    I am just letting DIM add my new content to my Win7 including that set

    then will test on previous beta

    then download this one and install

    and try again enlightened

    if it works I will kill this one in Task manager and try release build 4.11 also on this Win10 machine


    update now I have 2 frozen DAZ studios one on each computer angry
    my PC's just don't like this set
    killed Win 10 public build and same thing happens in the 4.11 release

    I got the set cheap so not returning it but disappointed all the same

    so

    it's not the beta

    its this set on both my computers

    Post edited by WendyLuvsCatz on
  • prixatprixat Posts: 1,588

    Playing with the new Matte Fog on 4.12.1.115.

    Does anyone else get the swapped Blue and Green colour channels?

    Red is correct and gives red fog.

     

    fog-blue-green.jpg
    1854 x 873 - 174K
    fog-green-blue.jpg
    1710 x 714 - 166K
    fog-red-red.jpg
    1698 x 693 - 184K
  • Richard HaseltineRichard Haseltine Posts: 100,839
    prixat said:

    Playing with the new Matte Fog on 4.12.1.115.

    Does anyone else get the swapped Blue and Green colour channels?

    Red is correct and gives red fog.

    This is a bug and has been fixed.

  • Hurdy3DHurdy3D Posts: 1,047

    I still think that DAZ should automatically open a new instance, if the main instance is still running.
    There's an issue that you can't start DAZ again, after you closed it, until the DAZ task is finishd with clean up, which can take a while after closing a complex scene. And propably Men's Friday have to switched to the (not recommaned) kill mode, to get it work reliably.
    So please, let DAZ open automatically new instances.

    I also would love to see soon support for NVLINK memory sharing for geometry.

  • RayDAntRayDAnt Posts: 1,135
    edited April 2020
    gerster said:

    I still think that DAZ should automatically open a new instance, if the main instance is still running.
    There's an issue that you can't start DAZ again, after you closed it, until the DAZ task is finishd with clean up, which can take a while after closing a complex scene.

    At the same time, this serves as a very straightforward way to alert the user that a previous instance has not yet shut down. Which in turn can lead to major usability problems (eg. not being able to work on/render scenes in a new instance up to the max capacity of system/GPU ram due to the previous instance holding on to things) whose true cause is otherwise very easy to overlook.

    Post edited by RayDAnt on
  • Hurdy3DHurdy3D Posts: 1,047
    RayDAnt said:
    gerster said:

    I still think that DAZ should automatically open a new instance, if the main instance is still running.
    There's an issue that you can't start DAZ again, after you closed it, until the DAZ task is finishd with clean up, which can take a while after closing a complex scene.

    At the same time, this serves as a very straightforward way to alert the user that a previous instance has not yet shut down. Which in turn can lead to major usability problems (eg. not being able to work on/render scenes in a new instance up to the max capacity of system/GPU ram due to the previous instance holding on to things) whose true cause is otherwise very easy to overlook.

    I think not starting without any warning is the most worse solution. It will confuse users, which don't know the background of the behavoir if DAZ ist just not starting.

    The best thing would be if DAZ would show a warning and offers an option in the settings that can be opted-in and automatically starts a new instance, for more advanced users.

  • barbultbarbult Posts: 24,241
    gerster said:
    RayDAnt said:
    gerster said:

    I still think that DAZ should automatically open a new instance, if the main instance is still running.
    There's an issue that you can't start DAZ again, after you closed it, until the DAZ task is finishd with clean up, which can take a while after closing a complex scene.

    At the same time, this serves as a very straightforward way to alert the user that a previous instance has not yet shut down. Which in turn can lead to major usability problems (eg. not being able to work on/render scenes in a new instance up to the max capacity of system/GPU ram due to the previous instance holding on to things) whose true cause is otherwise very easy to overlook.

    I think not starting without any warning is the most worse solution. It will confuse users, which don't know the background of the behavoir if DAZ ist just not starting.

    The best thing would be if DAZ would show a warning and offers an option in the settings that can be opted-in and automatically starts a new instance, for more advanced users.

    I agree that just not starting with no warning is very confusing.

  • Richard HaseltineRichard Haseltine Posts: 100,839

    You could add a feature request, though I'm not sure how i would work with the DS closing down case. You could use the script from https://www.daz3d.com/forums/discussion/comment/5112696/#Comment_5112696 to prepare several shortcuts for launching different instances.

  • StratDragonStratDragon Posts: 3,167

    In 4.12.15 if I have a long list of textures and that list does not fit in my display when I click on a surface detail it does not show the complete list, it cuts off on the last row that squeezed in. I had a bug report but can't find it. I was asked to take a screen shot but any time I press hot key the window closes, snip tool also closes it out. Im on Win7

Sign In or Register to comment.