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

1679111232

Comments

  • I just installed the latest beta (- version 4.11.0.196) next to my general release 4.10 Pro. How do I also access my content library in the beta? I am not talking about Smart Content here.

    You need to specify the content paths in Content Directory Manager, it doesn't inherit them from the General Release.

  • MasterstrokeMasterstroke Posts: 2,033
    edited August 2018

    I just installed the latest beta (- version 4.11.0.196) next to my general release 4.10 Pro. How do I also access my content library in the beta? I am not talking about Smart Content here.

    You need to specify the content paths in Content Directory Manager, it doesn't inherit them from the General Release.

    It seems, it actually does inherit them from the General Release, because my content is perfectly listed in the Content Director Manager. Still my content does not show up in the Content Library tab.

    Post edited by Masterstroke on
  • Please attach screenshots of the Content Directory Manger in the General Release, as well as this version. Make sure that the sections are expanded so that I can compare the listed paths.

  • MasterstrokeMasterstroke Posts: 2,033
    edited August 2018

    Please attach screenshots of the Content Directory Manger in the General Release, as well as this version. Make sure that the sections are expanded so that I can compare the listed paths.

    Every path is, where it suppose to be.

    DS build 4.11.0.196.jpg
    2558 x 1399 - 549K
    DSGeneral Releas 4.10.0.123.jpg
    2549 x 1398 - 498K
    Post edited by Masterstroke on
  • Ok, when you expand DAZ Studio Formats in the Content Library, is anything populated at all?

  • MasterstrokeMasterstroke Posts: 2,033

    Ok, when you expand DAZ Studio Formats in the Content Library, is anything populated at all?

    No ... ;-)

     

  • You are missing the D:/DAZ 3D/Studio/Content path (as shown in the General Release screenshot).

  • MasterstrokeMasterstroke Posts: 2,033

    You are missing the D:/DAZ 3D/Studio/Content path (as shown in the General Release screenshot).

    Yes, and the Content Library works fine in the General Release. It does not work in the Public Beta.

  • DoctorJellybeanDoctorJellybean Posts: 8,654
    edited August 2018

    Ok, let me look into this.

    Post edited by DoctorJellybean on
  • MasterstrokeMasterstroke Posts: 2,033
    edited August 2018

    Thank you :-)

    Maybe a helping hint: Opening scenes in the beta, created with the general release, work fine without any missing file error message.

    Post edited by Masterstroke on
  • MelanieLMelanieL Posts: 7,464
    edited August 2018

    Please attach screenshots of the Content Directory Manger in the General Release, as well as this version. Make sure that the sections are expanded so that I can compare the listed paths.

    Every path is, where it suppose to be.

    Erm - are you sure you haven't just minimised the Content Library upper panel - see my highlight on your screen shot, below.

    Capture.JPG
    644 x 596 - 34K
    Post edited by MelanieL on
  • MasterstrokeMasterstroke Posts: 2,033
    MelanieL said:

    Please attach screenshots of the Content Directory Manger in the General Release, as well as this version. Make sure that the sections are expanded so that I can compare the listed paths.

    Every path is, where it suppose to be.

    Erm - are you sure you haven't just minimised the Content Library upper panel - see my highlight on your screen shot, below.

    Sorry, my first thought was :Really??? lol. But looking closer at it, you're right. Thank you. You've made it. Those two tab handles are so tiny and close to each other, that even with glasses, I did not see, that those are actually two handles. After a high precicion click, VOILA the desired tab apearred . Thank you. yessmileyenlightened

  • MelanieLMelanieL Posts: 7,464

    You're welcome - I peered at your screenshot for fully two minutes before I spotted it, so it's not the most obvious! And yes, there are two closing handles there - which was a surprise to me - I just tried the upper one and found a whole section of flags I was unaware of before today!

  • Dolce SaitoDolce Saito Posts: 195
    edited August 2018

    ... Titan V ...

    I installed the new beta last night. Long story short: Denoiser still doesn't work for Titan V (latest drivers installed). But I noticed the log has changed slightly since from the last release.

    When denoiser is enabled, it renders fine until it kicks in, when it kicks in, image is like *that*. (Doesn't matter how much iteration stuff I do, always same). If I select my 980GTX only, denoiser works. But this is not acceptable for me :(

    There are two render logs in the file. First one is with denoiser, second one is without it.

    Denoiser -.png
    1920 x 1080 - 3M
    Denoiser +.png
    1920 x 1080 - 2M
    txt
    txt
    log.txt
    27K
    Post edited by Dolce Saito on
  • Dolce SaitoDolce Saito Posts: 195
    edited August 2018

    I waited for a re-test of an instant CTD bug during Activeposing which I noticed on previous beta. It still exists. Re-production rate is %100 depending of the state of the pose.

    You load a random pose for any G8(male-female doesn't matter). Pin at least two seperate character's body parts with "pin at end" or "pin both" setting. Accuracy is slowest (most accurate). Try to move a part where it produces forces towards both of the pin groups. Instant crash, no error, no log, nothing. Sometimes it requires some time to get this (it works until crash). But when it crashes, it always continues to crash despite re-loading the same scene and trying the same thing. So, I assume it is a high-reproducable bug in Activepose.

    In the end, Daz studio simply disappears (even bug report tool doesn't appear!). You left alone with your desktop (or writing this post) :P

    Post edited by Dolce Saito on
  • ckalan1ckalan1 Posts: 88

    I am not able to install this latest beta version. It is not showing up in my account. How can I solve this issue?

    Thanks,

    Craig

     

  • Richard HaseltineRichard Haseltine Posts: 102,344
    edited August 2018
    ckalan1 said:

    I am not able to install this latest beta version. It is not showing up in my account. How can I solve this issue?

    Thanks,

    Craig

    Have you been able to access previous DS 4.x Public Betas?

    Post edited by Richard Haseltine on
  • ckalan1ckalan1 Posts: 88

    Yes, I have not had a problem in the past. I am trying to install this one on a new hard drive and a clean setup.

    Craig

  • If it's a clean install of the system, check that Beta software is checked in Download Filters - available from the Ready to Download tab of DIM.

  • ckalan1ckalan1 Posts: 88

    That option is not showing. 

    Also in my online product library the beta does not show up.

    Craig

  • You may have to "buy" it.

  • Check that https://www.daz3d.com/daz-studio-beta does in fact show as purchased, though I think it's been the same product for some time now (which was why I asked if you'd been able to run previous betas). The Product Library link would be https://www.daz3d.com/downloader/customer/files#prod_12000

  • The AI De-noiser is only designed to run on one GPU that's normal if you look at the Iray documentation. The other cards Render while one card runs the AI-Denoiser as it is a separate operation from rendering   

    JD_Mortal said:

    Deprecated means marked for removal, not currently removed.

    It fails to render with it, so it is "removed"... Thus the conflict of notation, as I stated. Log excerpt below. "architectural sampler unavailable, caustic sampler disabled", both are selected in the render settings as ON

    2018-08-08 22:43:27.493 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using interactive scheduling, architectural sampler unavailable, caustic sampler disabled

    Also this...

    2018-08-08 22:44:50.674 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 3 device(s):

    2018-08-08 22:44:50.674 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 1 (TITAN Xp COLLECTORS EDITION)

    2018-08-08 22:44:50.675 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (TITAN Xp COLLECTORS EDITION)

    2018-08-08 22:44:50.675 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 2 (GeForce GTX TITAN X)

    ...

    2018-08-08 22:44:50.675 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...
    2018-08-08 22:44:50.675 Iray VERBOSE - module:category(IRAY:RENDER):   1.9   IRAY   rend progr: CUDA device 0 (TITAN Xp COLLECTORS EDITION): Processing scene...
    2018-08-08 22:44:50.676 Iray VERBOSE - module:category(IRAY:RENDER):   1.15  IRAY   rend progr: CUDA device 2 (GeForce GTX TITAN X): Processing scene...
    2018-08-08 22:44:50.677 Iray VERBOSE - module:category(IRAY:RENDER):   1.29  IRAY   rend progr: CUDA device 1 (TITAN Xp COLLECTORS EDITION): Processing scene...
    2018-08-08 22:44:50.807 Iray VERBOSE - module:category(IRAY:RENDER):   1.3   IRAY   rend stat : Geometry memory consumption: 351.482 MiB (device 1), 0 B (host)
    2018-08-08 22:44:50.829 Iray VERBOSE - module:category(IRAY:RENDER):   1.18  IRAY   rend stat : Geometry memory consumption: 351.482 MiB (device 0), 0 B (host)
    2018-08-08 22:44:50.836 Iray VERBOSE - module:category(IRAY:RENDER):   1.4   IRAY   rend stat : Geometry memory consumption: 351.482 MiB (device 2), 0 B (host)

    followed by this...

     2018-08-08 22:46:47.464 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00221 iterations after 116.789s.
    2018-08-08 22:46:55.751 Iray INFO - module:category(POST:RENDER):   1.0   POST   rend info : using cuda device 1, "TITAN Xp COLLECTORS EDITION" (6.1), buffers: fp16, cuDNN v7101, rt v9000
    2018-08-08 22:46:55.796 Iray INFO - module:category(POST:RENDER):   1.0   POST   rend info : layers created for resolution 1920 727, inp 6, outp 3, cuDNN memory 8.5 MB, total 478.2 MB
    2018-08-08 22:46:56.836 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00235 iterations after 126.161s.
    2018-08-08 22:47:03.505 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00250 iterations after 132.830s.
    2018-08-08 22:47:07.424 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00259 iterations after 136.750s.
    2018-08-08 22:47:17.353 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00276 iterations after 146.678s.
    2018-08-08 22:47:26.370 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00294 iterations after 155.695s.
    2018-08-08 22:47:32.459 Iray INFO - module:category(POST:RENDER):   1.0   POST   rend info : using cuda device 1, "TITAN Xp COLLECTORS EDITION" (6.1), buffers: fp16, cuDNN v7101, rt v9000
    2018-08-08 22:47:32.474 Iray INFO - module:category(POST:RENDER):   1.0   POST   rend info : layers created for resolution 1920 370, inp 6, outp 3, cuDNN memory 4.4 MB, total 249.2 MB
    2018-08-08 22:47:34.855 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00305 iterations after 164.180s.

    You can see that only one card is being used for POST rendering of the "Denoiser", for some reason it is displayed twice, once with 8.5MB/487.2MB then again with only 4.4MB/249.2MB

    That is after 200 iterations, where POST denoiser is setup to run. It is using CUDA device #1 and no other devices... But you see all three CUDA devices 0,1,2 are all rendering the rest.

    The POST denoiser lines are never mentioned again, anywhere in the logs, but I see it working up to the end, or it is just using that single/double image as an "overlay", from that moment, as an underlay until corrected pixel-info appears. (It should be denoising, progressively, as each new X-iteration resolves, not just once or twice, in the beginning.)

    Starting after 8 iterations is just bad... There is NOTHING resolved after 8 iterations, except the initial image-textures. You actually need some light resolved, before it can "guess" what the rest of the lighting will be. (Which is what it is trying to do, with the denoiser. It is guessing the "resolve" of the shades, of the unresolved pixels that light hasn't hit yet. But doing that only once, at iteration 8 is not good. There is not enough light resolved at that point.) Especially through "reflections and refractions", which takes 9+ to 250 iterations, before a "ray" has passed-through. (Like the eyes)

     

  • gederixgederix Posts: 390

    Active pose tool is still causing random crashes. Hour and a half's work, gone. Works fine all the way up until it doesnt, then daz just freezes for a few seconds and closes. 

  • AndySAndyS Posts: 1,438
    edited August 2018

    Hi,

    I see: a new version is available?
    has the inconsistance between diffuse and sss texture of the G8M been solved? Can't find it in the release notes.
    The further link is not valid, cause it points to the 4.10.0 change log.

    • Fixed bugs and/or made improvements in various areas; see the Change Log for details

    Have the refraction bugs for iRay and 3DL engine's interfaces been solved?

    Post edited by AndyS on
  • Richard HaseltineRichard Haseltine Posts: 102,344
    edited August 2018

    For Iray you'ds probably need to look at the Iray chnage logs, psoted in edited form below the main announcement post at the ehad of this thread. The link does include the 4.11 changes, including those in builds later than the Public beta - once you scroll past the links to previous, now released, versions (which may take up the first screen or so, depending on window size and zoom factor) you will see the first entry is for 4.11.0.1

    Post edited by Richard Haseltine on
  • nicsttnicstt Posts: 11,715

    I just installed the latest beta (- version 4.11.0.196) next to my general release 4.10 Pro. How do I also access my content library in the beta? I am not talking about Smart Content here.

    You need to specify the content paths in Content Directory Manager, it doesn't inherit them from the General Release.

    a bit late, but you can copy the studio folder over; that will get a lot of settings, and export the registry alter and inport; I would be careful messing with the registry though.

  • Does it support Nvidia's RTX Ray tracing for IRAY speed up???

  • Does it support Nvidia's RTX Ray tracing for IRAY speed up???

    The place to look would be the Iray change logs, posted at the top of the thread - however, I see no mention of it. Since RTX isn't yet available no-one will have been able to test directly, and it's always possible that it is enabled but nVidia kept it under wraps.

  • AndyS said:
    has the inconsistance between diffuse and sss texture of the G8M been solved?

    That would be a content issue, not a DS issue, presumably - have you reproted the problem? I don't recall seeing discussions or mentions on the forum.

This discussion has been closed.