Loading...
> >

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

1…910121415…32

Comments

  • VEGAVEGA Posts: 86

    I've done a test run on render with condition of 100% converged ratio same picture which took 1 hour and 4400 iterations.

    1. I waited on render to hit 99.80 % and then use post denoiser for one tick 

    2. I set post denoiser to start at 2000 iterations and let it complete by itself

    Result was both pictures were the same, resulting in washed skin details but really good blended soft shadows.

  • deathbycanondeathbycanon Posts: 1,227

    Dow do I get LAMH and LAMH catalizer into the betta version?? 

  • FishtalesFishtales Posts: 6,161

    Go to the Plugin folder on the studio installation and drag it into the Beta installation.

  • deathbycanondeathbycanon Posts: 1,227
    Fishtales said:

    Go to the Plugin folder on the studio installation and drag it into the Beta installation.

    Thank you! 

  • Daywalker DesignsDaywalker Designs Posts: 3,586
    second.technician.rimmer_9571136c47 said:

    And the bounding box isn't what one wants to drop his little people onto, but the actual surface of the targeted object.

    In the end, Richard, what I am hinting at in a oh so not subtle way is: we have iRay, we have dForce, and figures that can be shaped into anything from a munchkin to a giant ogre or a Hugh Hefner babe... but we have nothing when it comes to simple bump-into-this-and-stop collisions, vertically or otherwise.We have to cheat and use cheap tricks with dials, drop beacons and such. I am not a coder. I can't build a 3d program but the layman that I am can't help and wonder why we can have Dfoce (which understands the concepts of gravity and collisions) and Fluidos (another amazing thing, that one, for even more difficult simulations) and not have the kind of feature I described to be even *planned* for the future.It has to be less complicated than the two tools I just mentioned, no? If I am horribly wrong, I'll stand corrected and all :)

     

    In all honesty, I suspect it's actually almost as complicated as dForce, and probably something that they're considering as an add-on for that at some point.
  • Second Technician RimmerSecond Technician Rimmer Posts: 484

    That would be great if it happened, DD. It's been plaguing me for years XD

  • davemc0davemc0 Posts: 8

    So I just got my GeForce RTX 2080 up and running with DAZ Studio 4.10 and Iray wouldn't work. I tracked it down to a bug in the code for launching Iray. The following messages were in the log to tell the story:

    2018-09-29 11:22:42.337 Iray INFO - module:category(IRAY:RENDER):   1.1   IRAY   rend info : NVIDIA display driver version: 411.63
    2018-09-29 11:22:42.337 Iray INFO - module:category(IRAY:RENDER):   1.1   IRAY   rend info : Your NVIDIA driver supports CUDA version up to 10.0; iray requires CUDA version 8.0; all is good.
    2018-09-29 11:22:42.338 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.1   IRAY   rend warn : CUDA device 0 (GeForce RTX 2080): compute capability 7.5: unsupported by this version of iray, please look for an update with your software provider.
    2018-09-29 11:22:42.342 Iray INFO - module:category(IRAY:RENDER):   1.1   IRAY   rend info : Using iray plugin version 4.6-beta, build 287000.7672 n, 23 May 2017, nt-x86-64-vc11.
    2018-09-29 11:22:42.342 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.1   IRAY   rend warn : GPU 1 (GeForce RTX 2080) with CUDA compute capability 7.5 cannot be used by iray photoreal.
    2018-09-29 11:22:42.342 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.1   IRAY   rend warn : There is no CUDA-capable GPU available to the iray photoreal renderer.

    There is no reason that an old Iray cannot run on a new GPU or driver because Nvidia's CUDA drivers are backward compatible with code compiled to old compute capabilities. So the bug is that the logic is checking that the GPU's CUDA Compute Capability exactly matches that which the Iray kernels were compiled for. The fix is to check that the GPU's compute capability is *at least* that of the kernel. I know it's Iray that is doing this check, so this is an Nvidia bug. 

    Fortunately I was able to install this beta, which has an Iray compiled with a newer compute capability so it made it past the overly stringent check and it ran fine.

    Regards,
    Dave

  • davemc0davemc0 Posts: 8

    Once I got my GeForce RTX 2080 up and running with this beta I found a problem - the limit of 15,000 iterations is just not enough for my scene to converge, with or without the AI denoising. See the two attached images. The scene is glass cubes with the Sun/Sky model. These renderings both ran to 15,000 iterations and you can see that there's still plenty of noise. I hit the limit in under two hours of rendering at 4000x6000. Could you please change the slider for the number of iterations to have no maximum limit?

    Thanks,

    Dave

    noise.png
    800 x 1200 - 1M
    denoise.png
    800 x 1200 - 1M
  • davemc0davemc0 Posts: 8
    VEGA said:

    I've done a test run on render with condition of 100% converged ratio same picture which took 1 hour and 4400 iterations.

    1. I waited on render to hit 99.80 % and then use post denoiser for one tick 

    2. I set post denoiser to start at 2000 iterations and let it complete by itself

    Result was both pictures were the same, resulting in washed skin details but really good blended soft shadows.

    The way the post denoiser works is that it takes the in-progress rendering and passes that to the denoiser, which then displays it. The rendering then continues modifying the in-progress rendering. So if you denoise an image that had N iterations, you will get the same result, whether or not you have denoised images with fewer iterations earlier in the render.

  • barbultbarbult Posts: 24,755
    edited September 2018
    davemc0 said:

    Once I got my GeForce RTX 2080 up and running with this beta I found a problem - the limit of 15,000 iterations is just not enough for my scene to converge, with or without the AI denoising. See the two attached images. The scene is glass cubes with the Sun/Sky model. These renderings both ran to 15,000 iterations and you can see that there's still plenty of noise. I hit the limit in under two hours of rendering at 4000x6000. Could you please change the slider for the number of iterations to have no maximum limit?

    Thanks,

    Dave

    You can click the gear icon to the right of the Max Samples and select Parameter Settings. Then you can turn off limits or set a higher limit. After doing that, you can save a Render Preset for future use. Or even save a scene with those settings to use as your default scene to load at startup (Edit/Preferences), so you always start with those new settings.

    Edited for spelling

    Post edited by barbult on
  • barbultbarbult Posts: 24,755
    davemc0 said:
    VEGA said:

    I've done a test run on render with condition of 100% converged ratio same picture which took 1 hour and 4400 iterations.

    1. I waited on render to hit 99.80 % and then use post denoiser for one tick 

    2. I set post denoiser to start at 2000 iterations and let it complete by itself

    Result was both pictures were the same, resulting in washed skin details but really good blended soft shadows.

    The way the post denoiser works is that it takes the in-progress rendering and passes that to the denoiser, which then displays it. The rendering then continues modifying the in-progress rendering. So if you denoise an image that had N iterations, you will get the same result, whether or not you have denoised images with fewer iterations earlier in the render.

    Thank you. That is useful information.

  • davemc0davemc0 Posts: 8

    I'm hitting a crash when running Iray on a particular scene in this beta. Sometimes it just crashes the renderer but other times it crashes all of Daz Studio. The crash happens when I do larger render sizes. I can do 3200x3200 but not 3800x3800 in this scene. Note that in other scenes I can do 4500x6000 without a crash.

    Here is a log of a time that it crashed the renderer but not DAZ Studio:

     

    2018-10-01 11:34:12.159 Rendering image

    2018-10-01 11:34:12.315 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray WARNING - module:category(POST:RENDER):   1.0   POST   rend warn : Degraining filter radius 5 too large, clamped to 4

    2018-10-01 11:34:12.320 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating geometry.

    2018-10-01 11:34:12.330 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using OptiX Prime ray tracing (5.0.1).

    2018-10-01 11:34:12.330 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Importing scene graph.

    2018-10-01 11:34:12.330 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Importing geometry for motion time 0

    2018-10-01 11:34:12.330 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Geometry import (1 object with 480 triangles, 1 instance yielding 480 triangles) took 0.000232

    2018-10-01 11:34:12.334 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating materials.

    2018-10-01 11:34:12.335 Iray INFO - module:category(MATCNV:RENDER):   1.0   MATCNV rend info : found 0 textures, 0 lambdas (0 unique)

    2018-10-01 11:34:12.335 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating environment.

    2018-10-01 11:34:12.335 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating backplate.

    2018-10-01 11:34:12.335 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lens.

    2018-10-01 11:34:12.339 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lights.

    2018-10-01 11:34:12.339 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating object flags.

    2018-10-01 11:34:12.339 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating caustic portals.

    2018-10-01 11:34:12.339 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating decals.

    2018-10-01 11:34:12.542 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Allocating 1-layer frame buffer

    2018-10-01 11:34:12.775 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled

    2018-10-01 11:34:12.775 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Initializing local rendering.

    2018-10-01 11:34:12.809 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 1 device(s):

    2018-10-01 11:34:12.809 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce RTX 2080)

    2018-10-01 11:34:12.814 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...

    2018-10-01 11:34:12.814 Iray VERBOSE - module:category(IRAY:RENDER):   1.9   IRAY   rend progr: CUDA device 0 (GeForce RTX 2080): Processing scene...

    2018-10-01 11:34:12.832 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend stat : Geometry memory consumption: 36.0313 KiB (device 0), 0 B (host)

    2018-10-01 11:34:12.837 Iray INFO - module:category(IRAY:RENDER):   1.2   IRAY   rend info : Importing lights for motion time 0

    2018-10-01 11:34:12.841 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend stat : Texture memory consumption: 0 B for 0 bitmaps (device 0)

    2018-10-01 11:34:12.842 Iray INFO - module:category(IRAY:RENDER):   1.2   IRAY   rend info : Initializing light hierarchy.

    2018-10-01 11:34:12.842 Iray INFO - module:category(IRAY:RENDER):   1.2   IRAY   rend info : Light hierarchy initialization took 0.00s

    2018-10-01 11:34:12.843 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend stat : Lights memory consumption: 196 B (device 0)

    2018-10-01 11:34:12.848 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend stat : Materials memory consumption: 20.6172 KiB (GPU)

    2018-10-01 11:34:12.849 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend stat : Material measurement memory consumption: 0 B (GPU)

    2018-10-01 11:34:12.876 Iray INFO - module:category(IRAY:RENDER):   1.9   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Scene processed in 0.063s

    2018-10-01 11:34:12.896 Iray INFO - module:category(IRAY:RENDER):   1.9   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Allocated 470.009 MiB for frame buffer

    2018-10-01 11:34:12.901 Iray INFO - module:category(IRAY:RENDER):   1.9   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Allocated 1.6875 GiB of work space (2048k active samples in 0.000s)

    2018-10-01 11:34:12.901 Iray INFO - module:category(IRAY:RENDER):   1.9   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Used for display, optimizing for interactive usage (performance could be sacrificed)

    2018-10-01 11:34:14.239 Iray INFO - module:category(IRAY:RENDER):   1.9   IRAY   rend info : Allocating 1-layer frame buffer

    2018-10-01 11:34:19.682 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(POST:RENDER):   1.0   POST   rend error: A CUDA error occurred: unspecified launch failure

    2018-10-01 11:34:19.682 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.3   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): Kernel [5] (ShadowEvalFS      ) failed after 2.185s

    2018-10-01 11:34:19.682 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.3   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while launching CUDA renderer in core_renderer_wf.cpp:771)

    2018-10-01 11:34:19.687 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(POST:RENDER):   1.0   POST   rend error: Exception during postprocessing: unspecified launch failure

    2018-10-01 11:34:19.687 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.3   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): Failed to launch renderer

    2018-10-01 11:34:19.687 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Internal error in postprocessing pipeline.

    2018-10-01 11:34:19.691 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): Device failed while rendering

    2018-10-01 11:34:19.691 Iray Render error: Internal rendering error.

    2018-10-01 11:34:19.691 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray WARNING - module:category(IRAY:RENDER):   1.9   IRAY   rend warn : All available GPUs failed.

    2018-10-01 11:34:19.691 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray WARNING - module:category(IRAY:RENDER):   1.9   IRAY   rend warn : No devices activated. Enabling CPU fallback.

    2018-10-01 11:34:19.695 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while initializing memory buffer)

    2018-10-01 11:34:19.695 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: All workers failed: aborting render

    2018-10-01 11:34:19.695 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.700 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.700 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.704 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.704 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.709 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.709 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.714 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.714 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.719 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

    2018-10-01 11:34:19.719 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): unspecified launch failure (while de-allocating memory)

     

    And here is a log of a DAZ Studio crash:

    2018-10-01 11:15:03.359 Rendering image

    2018-10-01 11:15:03.476 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray WARNING - module:category(POST:RENDER):   1.0   POST   rend warn : Degraining filter radius 5 too large, clamped to 4

    2018-10-01 11:15:03.476 Iray INFO - module:category(POST:RENDER):   1.0   POST   rend info : Postprocessing denoiser is enabled

    2018-10-01 11:15:03.476 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating geometry.

    2018-10-01 11:15:03.481 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using built-in ray tracing (1.0.0).

    2018-10-01 11:15:03.486 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Importing scene graph.

    2018-10-01 11:15:03.486 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Importing geometry for motion time 0

    2018-10-01 11:15:03.487 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Geometry import (1 object with 480 triangles, 1 instance yielding 480 triangles) took 0.000222

    2018-10-01 11:15:03.487 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating materials.

    2018-10-01 11:15:03.491 Iray INFO - module:category(MATCNV:RENDER):   1.0   MATCNV rend info : found 0 textures, 0 lambdas (0 unique)

    2018-10-01 11:15:03.491 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating environment.

    2018-10-01 11:15:03.491 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating backplate.

    2018-10-01 11:15:03.491 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lens.

    2018-10-01 11:15:03.491 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lights.

    2018-10-01 11:15:03.495 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating object flags.

    2018-10-01 11:15:03.495 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating caustic portals.

    2018-10-01 11:15:03.495 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating decals.

    2018-10-01 11:15:03.620 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Allocating 1-layer frame buffer

    2018-10-01 11:15:03.763 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled

    2018-10-01 11:15:03.768 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Initializing local rendering.

    2018-10-01 11:15:03.788 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CPU: using 8 cores for rendering

    2018-10-01 11:15:03.788 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 1 device(s):

    2018-10-01 11:15:03.788 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CPU

    2018-10-01 11:15:03.788 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...

    2018-10-01 11:15:03.793 Iray VERBOSE - module:category(IRAY:RENDER):   1.4   IRAY   rend progr: CPU: Processing scene...

    2018-10-01 11:15:03.793 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : Importing lights for motion time 0

    2018-10-01 11:15:03.793 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : Initializing light hierarchy.

    2018-10-01 11:15:03.793 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : Light hierarchy initialization took 0.00s

    2018-10-01 11:15:03.797 Iray VERBOSE - module:category(IRAY:RENDER):   1.3   IRAY   rend stat : Native CPU code generated in 5.55e-07s

    2018-10-01 11:15:03.797 Iray INFO - module:category(IRAY:RENDER):   1.4   IRAY   rend info : CPU: Scene processed in 0.004s

    2018-10-01 11:15:03.966 Iray INFO - module:category(IRAY:RENDER):   1.4   IRAY   rend info : CPU: Allocated 308.991 MiB for frame buffer

    2018-10-01 11:15:31.645 Iray INFO - module:category(IRAY:RENDER):   1.4   IRAY   rend info : Allocating 1-layer frame buffer

    2018-10-01 11:16:15.549 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

    2018-10-01 11:16:30.780 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray WARNING - module:category(POST:RENDER):   1.0   POST   rend warn : Postprocessing is running on the CPU, but Denoiser is requested. Denoising is not available on CPU.

    2018-10-01 11:20:13.202 +++++++++++++++ DAZ Studio 4.11.0.196 starting +++++++++++++++++

  • davemc0davemc0 Posts: 8
    barbult said:
    davemc0 said:
    You can click the gear icon to the right of the Max Samples and select Parameter Settings. Then you can turn off limits or set a higher limit. After doing that, you can save a Render Preset for future use. Or even save a scene with those settings to use as your default scene to load at startup (Edit/Preferences), so you always start with tThose new settings.

    Thanks. That's quite helpful. I guess it helps to know the tools well. :) 

  • IceCrMnIceCrMn Posts: 2,141

    I am able to compile a fully functional dforce kernel with the new beta for my R9 200x "Pitcarin" AMD GPU. Thank you Daz team :)

    I'll update my bug report as fixed.

  • Trigger_31Trigger_31 Posts: 19

    Just informing that the same error I already reported when importing .daz files is still there...

    So I guess we won't be able to import .daz files anymore since this is not getting fixed as it seems.

    LOG :2018-10-02 16:04:15.043 Opening file Xyz.daz...
    2018-10-02 16:04:15.153 WARNING: QObject::connect: Cannot connect (null)::currentValueChanged() to DzSkeleton::handleDrawGLBonesChanged()
    2018-10-02 16:04:15.153 Error reading file D:/3D/DAZ 3D/DAZStudio3/content/Scenes/Xyz.daz : C Exception: Memory Access Violation - Attempted to read memory at address 0x00000000

  • Richard HaseltineRichard Haseltine Posts: 102,344

    Some .daz files have been failing for a long time, but some shold still be openable.

  • DoctorJellybeanDoctorJellybean Posts: 8,654
    vtx32_5a16989487 said:

    Just informing that the same error I already reported when importing .daz files is still there...

    So I guess we won't be able to import .daz files anymore since this is not getting fixed as it seems.

    LOG :2018-10-02 16:04:15.043 Opening file Xyz.daz...
    2018-10-02 16:04:15.153 WARNING: QObject::connect: Cannot connect (null)::currentValueChanged() to DzSkeleton::handleDrawGLBonesChanged()
    2018-10-02 16:04:15.153 Error reading file D:/3D/DAZ 3D/DAZStudio3/content/Scenes/Xyz.daz : C Exception: Memory Access Violation - Attempted to read memory at address 0x00000000

    As Richard said, some do load. A workaround is to load the ones which don't into the General Release and save it as a scene\subscene. You can then load the saved scene in this version.

  • antares_23573antares_23573 Posts: 26

    Btw ...

    Thank you for this and all the other updates!

    It's is very nice to see how this software develops and gets great functionalities.

  • RainbowArtistRainbowArtist Posts: 101

    Thanks DAZ team for the improvements to the Custom Action Scripts process in 4.11.0.231. Much easier to organize them than before.yessmiley

  • IceDragonArtIceDragonArt Posts: 12,548

    Oh my gosh you fixed the dforce kernel issue and I can now use dforce in the beta on my laptop.   Thank you, thank you, thank you!

  • nonesuch00nonesuch00 Posts: 18,293

    Yes, it's fixed on mine too. Almost the oldest intel integrated GPU that supports openCL 1.2 (Intel HD Graphics 4000, I think only the Intel HD Graphics 2500 is older that supports it)

  • barbultbarbult Posts: 24,755

    Don't try to do dForce simulation on a polyline object. I tried several times. It crashed DS 4.11.0.231 every time. I submitted a help request.

    This is what I did:
    1) Create new primitive sphere 
    2) Select sphere in Scene pane 
    3) Run sample script Generate_Polyline_Wireframe.dsa 
    4) Select the Sphere Polylines in the Scene pane 
    5) Edit/Geometry/Add dForce Modifier:Dynamic Surface 
    6) Open Simulation Settings pane 
    7) Click the Simulate button. 
    Daz Studio 4.11.0.231 crashed immediately.

  • Ghosty12Ghosty12 Posts: 2,065

    One question is why with every new version of studio do I have to reinstall certain content such as AoA's Advanced Spot and Distant Lights? What happens when I do use the new Studio version some of the options such as shadows vanish from the parameters section..

  • SpottedKittySpottedKitty Posts: 7,232
    ghosty12 said:

    One question is why with every new version of studio do I have to reinstall certain content such as AoA's Advanced Spot and Distant Lights? What happens when I do use the new Studio version some of the options such as shadows vanish from the parameters section..

    Light sets are a typical example of when this might happen. It's because there are two different types of plugin (something that adds to the functionality of DAZ|Studio, not just content you can use in a scene). One type only uses scripts that are installed into your content folder, the other also uses actual code that gets installed to your D|S program location (there's a plugins folder there). The AoA lights are an example of the code type, since they include instructions to D|S for defining how the new lights work. This type of plugin generally (but not always, just to confuse you) needs an update every time the D|S program gets updated; if there's a mismatch between the version numbers of the program and plugin, the plugin functions won't work.

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

    One question is why with every new version of studio do I have to reinstall certain content such as AoA's Advanced Spot and Distant Lights? What happens when I do use the new Studio version some of the options such as shadows vanish from the parameters section..

    That shouldn't happen. Your first beta, yes, as the application folder is in a different place, and the stnadard Daz plug-ins get updated with DS - but shaders, scripts, and most third-party plug-ins should not need reinstalling unless you are changing the install folder.

  • Ghosty12Ghosty12 Posts: 2,065
    edited October 2018
    SpottedKitty said:
    ghosty12 said:

    One question is why with every new version of studio do I have to reinstall certain content such as AoA's Advanced Spot and Distant Lights? What happens when I do use the new Studio version some of the options such as shadows vanish from the parameters section..

    Light sets are a typical example of when this might happen. It's because there are two different types of plugin (something that adds to the functionality of DAZ|Studio, not just content you can use in a scene). One type only uses scripts that are installed into your content folder, the other also uses actual code that gets installed to your D|S program location (there's a plugins folder there). The AoA lights are an example of the code type, since they include instructions to D|S for defining how the new lights work. This type of plugin generally (but not always, just to confuse you) needs an update every time the D|S program gets updated; if there's a mismatch between the version numbers of the program and plugin, the plugin functions won't work.

    Ahh thank you for that, I always wondered why with every iteration of Studio I had to reinstall the lights and some other plugins, thank you for why this happens.. :)

    Richard Haseltine said:
    ghosty12 said:

    One question is why with every new version of studio do I have to reinstall certain content such as AoA's Advanced Spot and Distant Lights? What happens when I do use the new Studio version some of the options such as shadows vanish from the parameters section..

    That shouldn't happen. Your first beta, yes, as the application folder is in a different place, and the stnadard Daz plug-ins get updated with DS - but shaders, scripts, and most third-party plug-ins should not need reinstalling unless you are changing the install folder.


    I know it shouldn't but it does, I have to map in my content folders since it is a new version beta and that is it.. Anyways will show you what happens.. First two images are of the current release of Studio.. The second two are of the current beta and what happens..

     

    DS410.png
    207 x 255 - 10K
    DS410-1.png
    176 x 232 - 11K
    DS411b.png
    222 x 264 - 10K
    DS411b-1.png
    187 x 300 - 14K
    Post edited by Ghosty12 on
  • Richard HaseltineRichard Haseltine Posts: 102,344
    ghosty12 said:
    SpottedKitty said:
    ghosty12 said:

    One question is why with every new version of studio do I have to reinstall certain content such as AoA's Advanced Spot and Distant Lights? What happens when I do use the new Studio version some of the options such as shadows vanish from the parameters section..

    Light sets are a typical example of when this might happen. It's because there are two different types of plugin (something that adds to the functionality of DAZ|Studio, not just content you can use in a scene). One type only uses scripts that are installed into your content folder, the other also uses actual code that gets installed to your D|S program location (there's a plugins folder there). The AoA lights are an example of the code type, since they include instructions to D|S for defining how the new lights work. This type of plugin generally (but not always, just to confuse you) needs an update every time the D|S program gets updated; if there's a mismatch between the version numbers of the program and plugin, the plugin functions won't work.

    Ahh thank you for that, I always wondered why with every iteration of Studio I had to reinstall the lights and some other plugins, thank you for why this happens.. :)

    Richard Haseltine said:
    ghosty12 said:

    One question is why with every new version of studio do I have to reinstall certain content such as AoA's Advanced Spot and Distant Lights? What happens when I do use the new Studio version some of the options such as shadows vanish from the parameters section..

    That shouldn't happen. Your first beta, yes, as the application folder is in a different place, and the stnadard Daz plug-ins get updated with DS - but shaders, scripts, and most third-party plug-ins should not need reinstalling unless you are changing the install folder.


    I know it shouldn't but it does, I have to map in my content folders since it is a new version beta and that is it.. Anyways will show you what happens.. First two images are of the current release of Studio.. The second two are of the current beta and what happens..

    That is installing content to the application folder, so if you use a new application folder (as installing a beta for the first time) or clear the application folder (the DS uninstaller won't, but if you use a third party tool to handle uninstalls it might) then you will need to reinstall.

  • jiujitsudadjiujitsudad Posts: 7
    edited October 2018

    I found a problem and I'm not sure if it's related to 4.11 or not.

    Before 4.11 I had rendered jewelry with no problems. However now I try to render jewelry and things like gold, silver, diamonds, platnum and so on all have black reflections when the enviroment is set to scene only, and I have emmissives, or spotlights of any shape. Even with 80 million watts, it still has weird black reflections that. With Dome and Scene on, this problem goes away. Here are some images that show what I'm talking about, and I just gave links because the images might be a bit large to upload here.

    Dome off

    http://www.lexigamesvn.com/images/braclet_scene_only.png

    Dome on

    http://www.lexigamesvn.com/images/braclet_domeandscene_on.png

    Dome off

    http://www.lexigamesvn.com/images/Earrings_scenelights_only.png

    Dome on

    https://www.lexigamesvn.com/images/Earrings_domeandscene_on.png

     

    Does anyone know if this is a 4.11 thing, or what is causing it? I've uninstalled and reinstalled everything, including windows, daz, updated drivers. I thought they might be the wrong shaders at first, but even after making sure that iray shaders were used, it still doe its.

    Also this happens with ALL jewelry from all artists, all packages, and all gold, silver, diamond, and any other shader related to jewelry. Mirrors and reflective handrails are unaffected.

    Thanks,

    Chatterbox

    Post edited by jiujitsudad on
  • DoctorJellybeanDoctorJellybean Posts: 8,654

    Your links don't show any images.

  • jiujitsudadjiujitsudad Posts: 7
    DoctorJellybean said:

    Your links don't show any images.

    That's really weird. The links appear to be correct, but it all leads to my Patreon page. WTF?

     

This discussion has been closed.