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

1151618202132

Comments

  • My beta renders tend to hang once they reach 100% and never finish after several renders.  Then I have to ctl+alt+del out of DS and start over.  Is this a known issue or do I need to start a support ticket?  SHould I include my logfile?  I can't remember where to find my DS crash log.

  • nicsttnicstt Posts: 11,715

    I've got to ask the question: why are you rendering to 100%?

    99% is enough, and tbh generally far too much.

    If there are parts not clearing up, either take advantage of the new tools in 4.11 or use spot render.

  • SpottedKittySpottedKitty Posts: 7,232

    An Iray render is essentially "neverending" — unlike a 3Delight render, which takes a lot of mathematical shortcuts to precisely calculate each pixel of the final render, Iray constantly approaches but never quite reaches a "perfect" finished state; instead of finishing, it hits one of three "stop conditions". The default convergence value of 95% usually gives a pretty good quality render, but if you want something better, you should push the convergence value to 99% or more — but not all the way to 100%. You might be getting those hangs because Iray is trying to use nearly infinitely large or infinitely small numbers right at the end of the render, which tends to cause computers to pop their corks. Limit the convergence to just a fraction under 100% and see if that clears up your hangs.

  • Perhaps an overkill, but my typical Iray render settings are:

    Max Samples: 15000
    Max Time: 7200
    Rendering Converged Ratio: 95%

  • I will try some of those suggestions.  But Iam mostly testing small scenes and scene elements at the moment... like one character and no scene.  WIth a 2080Ti card they render pretty fast.  But they are just infinitely hanging.  It also happens wif/when I stopp a render after an uncertain number of renders.  I ususally have been letting it go to 100% just because it is going so fast. BUt the work disruption of hanging and crashing is wht is wasting most of my time atm.

  • wateenzijkwateenzijk Posts: 1
    edited January 2019

    happy newyear.

    Post edited by wateenzijk on
  • bueller1998_df4ca4b697 having a lot of daz studio crashes can make it even more unstable. The 1s and 0s get goofed. A clean install of studio might be needed. A while back I was having problems with Daz crashing and hanging my system. I did a clean install of windows and 99% of my stability problems went away.

  • It might be worthwhile resetting the database and reimporting the metadata before reinstalling Windows, as a corrupt database can cause instability.

  • barbult said:

    Memory optimization vs.Speed optimization does cause artifacts on non-instances in the beta.

    I submitted this report back in August. I have not retested with the latest beta, but I have not received any response on my help request to say that it has been fixed. Edit: I just retested with the scene I had saved at the time. The problem still exists in DS 4.11.0.236.

    When I set the Render Settings/Optimization/Instancing Optimization to Memory, it causes dark artifacts in my character's eyes. If I change the setting to Speed, the artifacts go away. I do not have any instances in this scene. Why does Instancing Optimization have any affect on my scene at all?
    This Becomes a big problem when I render a scene that has a lot of instances, because it is necessary to set Instancing Optimization to Memory. All my characters render with the dark eye artifacts in those scenes.
    To reproduce this problem: 
    Open DS 4.11.0.171 Beta. 
    Create a new scene with default render settings. 
    Change Render Settings/Optimization/Instancing Optimization to Memory. 
    Load Genesis 8 Male. 
    Translate Genesis 8 Male to x=0, Y=0, Z=-100. 
    Frame the camera on G8M face to get a good view of the eyes. 
    Render the scene. 
    Observe the dark artifacts in the sclera area of the eyes. 
    Change Render Settings/Optimization/Instancing Optimization to Speed. 
    Render the scene. 
    Observe that there are no dark artifacts in the eyes.
    Repeat this test with DS 4.10.0.123 and observe that the dark artifacts do not occur under the same test conditions that caused them in 4.11.0.171.

     

    Personally I get around this by creating a geoshell for the figure, hiding every part of the shell except EyeMoisture and Cornea, copying the EyeMoisture and Cornea surfaces from the figure to the geograft, and then using the Geometry Editor to hide the figure's EyeMoisture and Cornea geometry. It seems to eliminate the problem altogether. Not a solution, but it is a workaround. 

  • Avatar1912Avatar1912 Posts: 1
    edited January 2019

    Is there any chance to see a new beta soon with a up to date IRAY plugin ? 

    Or does RTX owners still have no chance to get theyer cards to run at 100% of what they are abel to do ? 

    Post edited by Avatar1912 on
  • Is there any chance to see a new beta soon with a up to date IRAY plugin ? 

    Or does RTX owners still have no chance to get theyer cards to run at 100% of what they are abel to do ? 

    nVidia will need to provide a version of Iray that uses RTX cors before Daz can integrate it into DS.

  • I have v4.10 installed and then installed beta v4.11.0.236.  Ever since the installation, my parameter favorites don't save from one session to another.  I save my scene, close Daz Studio, reopen Daz Studio and the scene, and my parameter favorites are gone.  Is this a known issue?  

  • Brainstem said:

    I have v4.10 installed and then installed beta v4.11.0.236.  Ever since the installation, my parameter favorites don't save from one session to another.  I save my scene, close Daz Studio, reopen Daz Studio and the scene, and my parameter favorites are gone.  Is this a known issue?  

    It currently works for me. Please give us an example to try.

  • Brainstem said:

    I have v4.10 installed and then installed beta v4.11.0.236.  Ever since the installation, my parameter favorites don't save from one session to another.  I save my scene, close Daz Studio, reopen Daz Studio and the scene, and my parameter favorites are gone.  Is this a known issue?  

    It currently works for me. Please give us an example to try.

    I'm not sure what you're asking for.  Did you want me to post a DUF file?  Or further explain the issue?

  • Brainstem said:
    Brainstem said:

    I have v4.10 installed and then installed beta v4.11.0.236.  Ever since the installation, my parameter favorites don't save from one session to another.  I save my scene, close Daz Studio, reopen Daz Studio and the scene, and my parameter favorites are gone.  Is this a known issue?  

    It currently works for me. Please give us an example to try.

    I'm not sure what you're asking for.  Did you want me to post a DUF file?  Or further explain the issue?

    Further explain the issue, e.g. steps we can take to try.

  • ViallyVially Posts: 343

    GraphMate and KeyMate do not appear in the Plugin listing for 4.11.

    Is Daz planning thier own solution for these plugins or were they overlooked when setting the script to lookup plugins?

  • namffuaknamffuak Posts: 4,176
    Vially said:

    GraphMate and KeyMate do not appear in the Plugin listing for 4.11.

    Is Daz planning thier own solution for these plugins or were they overlooked when setting the script to lookup plugins?

    If they were installed before you installed 4.11 you need to uninstall and reinstall them. This applies to any plugins installed before the beta - as plugins install to the plugin subdirectory of the studio executable.

  • Seven193Seven193 Posts: 1,103
    Does the beta version fix the transparent hair selection bug, where the highlighted color doesn't turn off? I couldn't find any mention of it in the notes.
  • Dave230 said:
    Does the beta version fix the transparent hair selection bug, where the highlighted color doesn't turn off? I couldn't find any mention of it in the notes.

    I don't recognise that issue - has it been reported?

  • MelanieLMelanieL Posts: 7,464
    edited January 2019

    Has anyone else encountered errors loading some products from the store which are .daz files in DS4.11.0.236?

    I noticed it first when I tried to add an Optitex dynamic dress the other day. As an experiment I tried some other Optitex dynamics and found over 50% of them would not load, all with exactly the same error (piece of log file attached)

    I then tried them in DS4.6 (the last non-Beta I installed) and they all worked just fine. I'm not sure at what point they stopped working but they certainly have a problem with the current Beta.

    According to DIM I have the latest installers for all these products (at least no updates show for me)

    I then widened the net and scanned all my mapped directories for .daz files and found a whole lot of other things that don't work in DS4.11.0.236 - I've attached a text file with a list of everything I found which failed, so it's not a small problem. Sorry if thie list is hard to decipher, I did it initially for my own benefit - the numbers in parentheses show how many of the .daz fies in that product fail where some work OK. No parentheses implies total failure.

    DynamicsError.jpg
    1211 x 102 - 47K
    txt
    txt
    dotDAZ files Not Working in DS4-11.txt
    3K
    Post edited by MelanieL on
  • MelanieL said:

    Has anyone else encountered errors loading some products from the store which are .daz files in DS4.11.0.236?

    I noticed it first when I tried to add an Optitex dynamic dress the other day. As an experiment I tried some other Optitex dynamics and found over 50% of them would not load, all with exactly the same error (piece of log file attached)

    I then tried them in DS4.6 (the last non-Beta I installed) and they all worked just fine. I'm not sure at what point they stopped working but they certainly have a problem with the current Beta.

    According to DIM I have the latest installers for all these products (at least no updates show for me)

    I then widened the net and scanned all my mapped directories for .daz files and found a whole lot of other things that don't work in DS4.11.0.236 - I've attached a text file with a list of everything I found which failed, so it's not a small problem. Sorry if thie list is hard to decipher, I did it initially for my own benefit - the numbers in parentheses show how many of the .daz fies in that product fail where some work OK. No parentheses implies total failure.

    Some .DAZ files work, others don't. A workaround is to load it with the current release and save it as a subscene. It will then load in the latest beta.

  • MelanieLMelanieL Posts: 7,464
    MelanieL said:

    Has anyone else encountered errors loading some products from the store which are .daz files in DS4.11.0.236?

    I noticed it first when I tried to add an Optitex dynamic dress the other day. As an experiment I tried some other Optitex dynamics and found over 50% of them would not load, all with exactly the same error (piece of log file attached)

    I then tried them in DS4.6 (the last non-Beta I installed) and they all worked just fine. I'm not sure at what point they stopped working but they certainly have a problem with the current Beta.

    According to DIM I have the latest installers for all these products (at least no updates show for me)

    I then widened the net and scanned all my mapped directories for .daz files and found a whole lot of other things that don't work in DS4.11.0.236 - I've attached a text file with a list of everything I found which failed, so it's not a small problem. Sorry if thie list is hard to decipher, I did it initially for my own benefit - the numbers in parentheses show how many of the .daz fies in that product fail where some work OK. No parentheses implies total failure.

    Some .DAZ files work, others don't. A workaround is to load it with the current release and save it as a subscene. It will then load in the latest beta.

    Yes that's what I had to do with the dress I needed to use (and it worked of course).

    Is there meant to be a proper fix coming for all these products? Or is it a permanent problem (which means quite a chunk of the store is going to be left with loading errors)?

  • .DAZ files are very problematic, hence the switch to .DUF. It may be that the content needs to be converted on a case by case basis.

  • MelanieLMelanieL Posts: 7,464

    Mmm - main problem (apart from the time it takes) is that it re-creates all the /data/ library contents, which is more bloat for the hard drive. The Maiden Fair Gown that I converted created /data/ files using 2.52 times the space of the original. (I actually saved as a Support Asset... Dynamic Cloth Asset - which seems to retain all the Optitex features of the original)

  • Seven193Seven193 Posts: 1,103
    edited January 2019
    Dave230 said:
    Does the beta version fix the transparent hair selection bug, where the highlighted color doesn't turn off? I couldn't find any mention of it in the notes.

    I don't recognise that issue - has it been reported?

    I mentioned it last year, and you mentioned it was a known issue:
    https://www.daz3d.com/forums/discussion/288286/hair-selection-bug

    Post edited by Seven193 on
  • Hi ! I can't see beta build in download manager ? 

    is that hidden by devs ? 

  • barbultbarbult Posts: 24,755
    sulllivan said:

    Hi ! I can't see beta build in download manager ? 

    is that hidden by devs ? 

    You have to configure your DIM download filters to show it.

  • hphoenixhphoenix Posts: 1,335
    barbult said:
    sulllivan said:

    Hi ! I can't see beta build in download manager ? 

    is that hidden by devs ? 

    You have to configure your DIM download filters to show it.

    And if you haven't, you have to "buy" it (it's free) in the store:  https://www.daz3d.com/daz-studio-beta

     

  • ok , thanks ! now I see it . 

  • OstadanOstadan Posts: 1,128

    Well, humph.  I installed the latest driver (418.81) for my Nvidia RTX 2080, and now DS 4.11 beta falls back to CPU rendering. It works to render a scene with just a single cube, but any other prop or figure causes errors like

    1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2080): an illegal instruction was encountered (while launcing CUDA renderer in core_renderer_wf.cpp:437)

    I hope an update beta will be along soon, since I have no idea how to back out of the driver update.

This discussion has been closed.