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

1272830323374

Comments

  • marblemarble Posts: 7,500
    edited November 2019

    @marble You didn't say which DAZ Studio version. Also, you need to tell us if your CPU fallback with Iray preview happens immediatelly with an empty scene or not.

    Isn't this always the case: I duly opened DAZ Studio (Beta 4.12.1.16) and switched to IRay preview. No crash to CPU. I loaded a base G8F - still no crash. I loaded another character (instead of base G8F) - still no crash. I don't understand because just a few days ago it was crashing to CPU if I looked at it sideways. Maybe my own memory is faulty and all this was happening before I removed the GTX970. Or maybe some objects/materials trigger the CPU fall-back while others don't?

    The CPU fall-back is still happening when I swap shaders in and out, though. And I noticed yesterday, when rendering an image series, that there is still a jump in VRAM usage between frame one and frame two after which it remains steady. If that jump remains within my 8GB it doesn't fall back but it is getting increasingly difficult to make a scene fit within 8 GB - even after running the obligatory Scene Optimizer.

    Post edited by marble on
  • marblemarble Posts: 7,500

    I see there's an update today so I'll try that. However, the update post only mentions RTX so I fear that any fixes for those of us with GTX cards might have been de-prioritised.

  • The update comes straight from NVIDIA.

  • Tested the new 4.12.1.40 just now with same Babina/Lingerie Robe set test.  Same result as 4.12.1.16.  Drop to CPU on 4th load of Lingerie Robe wearable set.  Will update ticket with new log.

  • If you read back to the 13th of November you will see that I said that there were no problems with the latest release and beta versions of DAZstudio so long as the Nvidia drivers v431.86 were used.  I have not yet tested Nvidia Studio drivers 440.28.

  • HeckbarthHeckbarth Posts: 64
    edited November 2019

    CPU fallback problem w/ empty scene render here.

    Configuration:

    Hardware

    i9-9980HK CPU @ 2.40GHz, 2401 Mhz, 8 Cores

    64 GByte RAM

    NVIDIA GeForce RTX 2080

    NVIDIA GeForce RTX 2070 (as eGPU via USB-C).   

    Software

    Windows 10 Pro 64bit (1903 - Build # 18362.476)

    DAZ Studio 4.12.1.16

    NVidia Driver 441.28 DHC Studio AND 441.20 DHC Game driver

     

    Empty scene render log (Dome based default settings) attached.

     

    Is there any chance disabling OptiX support? I'd like to test if w/o OptiX support the problem remains.

    Unfortunately the checkbox seems to have gone. And what b.t.w. is dzneuraymgr?

    On the one hand, both DAZ and NVidia use Iray to market their offerings, on the other hand, they neither work together (see this NVidia forum post: https://devtalk.nvidia.com/default/topic/1067115/attn-david-hart-all-drivers-after-430-86-are-breaking-iray-for-daz-studio-4-12/?offset=10) nor they seem to pay for sufficient and professional quality engineering. Who pays is the customer, with their money (look at my hardware alone) and - much worse - lifetime.

    I'm going to report this to DAZ support, too, just to make clear there's an issue to be solved.

     

    PS: Doh, upload doesn't work. Here's the logfile content:

    2019-11-26 14:08:17.085 *** Scene Cleared ***
    2019-11-26 14:08:17.087 File loaded in 0 min 0.0 sec.
    2019-11-26 14:08:17.088 Loaded file: reset.duf
    2019-11-26 14:08:51.540 Rendering image
    2019-11-26 14:08:51.606 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.
    2019-11-26 14:08:51.606 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.
    2019-11-26 14:08:51.606 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0
    2019-11-26 14:08:51.606 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (0 objects with 0 triangles, 0 instances yielding 0 triangles) took 0.000s
    2019-11-26 14:08:51.612 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.
    2019-11-26 14:08:51.613 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 0 textures, 0 lambdas (0 unique)
    2019-11-26 14:08:51.613 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
    2019-11-26 14:08:51.613 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
    2019-11-26 14:08:51.613 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
    2019-11-26 14:08:51.618 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
    2019-11-26 14:08:51.618 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
    2019-11-26 14:08:51.618 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
    2019-11-26 14:08:51.618 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
    2019-11-26 14:08:51.637 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
    2019-11-26 14:08:51.665 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
    2019-11-26 14:08:51.665 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
    2019-11-26 14:08:51.696 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 2 device(s):
    2019-11-26 14:08:51.696 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CUDA device 0 (GeForce RTX 2080)
    2019-11-26 14:08:51.696 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CUDA device 1 (GeForce RTX 2070)
    2019-11-26 14:08:51.701 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2019-11-26 14:08:51.701 Iray [VERBOSE] - IRAY:RENDER ::   1.9   IRAY   rend progr: CUDA device 0 (GeForce RTX 2080): Processing scene...
    2019-11-26 14:08:51.702 Iray [VERBOSE] - IRAY:RENDER ::   1.7   IRAY   rend stat : Geometry memory consumption: 0.000 B (device 0), 0.000 B (host)
    2019-11-26 14:08:51.702 Iray [VERBOSE] - IRAY:RENDER ::   1.10  IRAY   rend stat : Geometry memory consumption: 0.000 B (device 1), 0.000 B (host)
    2019-11-26 14:08:51.706 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Using OptiX version 6.1.2
    2019-11-26 14:08:51.707 Iray [VERBOSE] - IRAY:RENDER ::   1.4   IRAY   rend progr: CUDA device 1 (GeForce RTX 2070): Processing scene...
    2019-11-26 14:08:51.710 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Initializing OptiX for CUDA device 0
    2019-11-26 14:08:51.710 Iray [INFO] - IRAY:RENDER ::   1.10  IRAY   rend info : Initializing OptiX for CUDA device 1
    2019-11-26 14:08:51.854 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.10  IRAY   rend error: "buildInputs[0].instanceArray", "numInstances" is non-zero, but "instances" is null
    2019-11-26 14:08:51.859 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.7   IRAY   rend error: "buildInputs[0].instanceArray", "numInstances" is non-zero, but "instances" is null
    2019-11-26 14:08:51.859 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.10  IRAY   rend error: optixAccelBuild( context,nullptr, &opt,&inst_input,1, get_address(m_d_scratch),tlas_size.tempSizeInBytes, get_address(m_tlas.data),tlas_size.outputSizeInBytes, &m_tlas.traversable, &bbox_desc,1) failed: Invalid value
    2019-11-26 14:08:51.864 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.7   IRAY   rend error: optixAccelBuild( context,nullptr, &opt,&inst_input,1, get_address(m_d_scratch),tlas_size.tempSizeInBytes, get_address(m_tlas.data),tlas_size.outputSizeInBytes, &m_tlas.traversable, &bbox_desc,1) failed: Invalid value
    2019-11-26 14:08:51.864 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 1 (GeForce RTX 2070): Scene setup failed
    2019-11-26 14:08:51.868 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): Scene setup failed
    2019-11-26 14:08:51.868 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce RTX 2080): Device failed while rendering
    2019-11-26 14:08:51.868 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 1 (GeForce RTX 2070): Device failed while rendering
    2019-11-26 14:08:51.873 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : All available GPUs failed.
    2019-11-26 14:08:51.873 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : No devices activated. Enabling CPU fallback.

    2019-11-26 14:08:51.873 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: All workers failed: aborting render
    2019-11-26 14:08:51.878 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU: using 16 cores for rendering
    2019-11-26 14:08:51.878 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):
    2019-11-26 14:08:51.878 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CPU
    2019-11-26 14:08:51.878 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2019-11-26 14:08:51.878 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : Using Embree 2.8.0
    2019-11-26 14:08:51.878 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : Initializing Embree
    2019-11-26 14:08:51.883 Iray [VERBOSE] - IRAY:RENDER ::   1.9   IRAY   rend progr: CPU: Processing scene...
    2019-11-26 14:08:51.883 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : Importing lights for motion time 0
    2019-11-26 14:08:51.883 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : Initializing light hierarchy.
    2019-11-26 14:08:51.883 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : Light hierarchy initialization took 0.000s
    2019-11-26 14:08:51.886 Iray [VERBOSE] - IRAY:RENDER ::   1.4   IRAY   rend stat : Native CPU code generated in 0.000s
    2019-11-26 14:08:51.891 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CPU: Scene processed in 0.012s
    2019-11-26 14:08:51.918 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CPU: Allocated 96.000 MiB for frame buffer
    2019-11-26 14:08:52.214 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : Allocating 1-layer frame buffer
    2019-11-26 14:08:52.261 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iterations after 0.559s.
    2019-11-26 14:08:52.629 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 0.926s.
    2019-11-26 14:08:52.984 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00003 iterations after 1.281s.
    2019-11-26 14:08:53.326 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00004 iterations after 1.624s.
    2019-11-26 14:08:53.682 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00005 iterations after 1.980s.
    2019-11-26 14:08:54.032 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00006 iterations after 2.330s.
    2019-11-26 14:08:54.411 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00007 iterations after 2.709s.
    2019-11-26 14:08:54.778 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00008 iterations after 3.075s.
    2019-11-26 14:08:55.111 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00009 iterations after 3.409s.
    2019-11-26 14:08:55.450 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00010 iterations after 3.748s.
    2019-11-26 14:08:55.809 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00011 iterations after 4.107s.
    2019-11-26 14:08:56.164 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00012 iterations after 4.462s.
    2019-11-26 14:08:56.871 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - POST:RENDER ::   1.0   POST   rend warn : renderer iray has no more devices available. Postprocessing falling back to CPU.
    2019-11-26 14:08:56.950 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00014 iterations after 5.248s.
    2019-11-26 14:08:58.315 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00018 iterations after 6.612s.
    2019-11-26 14:08:59.238 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00021 iterations after 7.536s.
    2019-11-26 14:09:00.309 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00024 iterations after 8.607s.
    2019-11-26 14:09:01.775 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
    2019-11-26 14:09:01.806 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00028 iterations after 10.104s.
    2019-11-26 14:09:03.525 Iray [VERBOSE] - IRAY:RENDER ::   1.0   IRAY   rend progr: 83.50% of image converged
    2019-11-26 14:09:03.631 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00032 iterations after 11.930s.
    2019-11-26 14:09:05.328 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00037 iterations after 13.626s.
    2019-11-26 14:09:06.100 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00039 iterations after 14.397s.
    2019-11-26 14:09:06.860 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00041 iterations after 15.157s.
    2019-11-26 14:09:07.665 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00043 iterations after 15.962s.
    2019-11-26 14:09:08.422 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00045 iterations after 16.719s.
    2019-11-26 14:09:09.366 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00047 iterations after 17.664s.
    2019-11-26 14:09:10.038 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00049 iterations after 18.336s.
    2019-11-26 14:09:10.838 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00051 iterations after 19.136s.
    2019-11-26 14:09:11.590 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00053 iterations after 19.888s.
    2019-11-26 14:09:12.334 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00055 iterations after 20.631s.
    2019-11-26 14:09:13.045 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00057 iterations after 21.343s.
    2019-11-26 14:09:13.796 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00059 iterations after 22.094s.
    2019-11-26 14:09:14.646 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00061 iterations after 22.944s.
    2019-11-26 14:09:15.649 Iray [VERBOSE] - IRAY:RENDER ::   1.0   IRAY   rend progr: 100.00% of image converged
    2019-11-26 14:09:15.649 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00063 iterations after 23.947s.
    2019-11-26 14:09:15.788 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Convergence threshold reached.
    2019-11-26 14:09:16.681 Saved image: C:\Users\Karsten\AppData\Roaming\DAZ 3D\Studio4 Public Build\temp\render\r.png
    2019-11-26 14:09:16.695 Finished Rendering
    2019-11-26 14:09:16.733 Total Rendering Time: 25.27 seconds
    2019-11-26 14:09:16.770 Loaded image r.png
    2019-11-26 14:09:16.829 Saved image: C:\Users\Karsten\AppData\Roaming\DAZ 3D\Studio4 Public Build\temp\RenderAlbumTmp\Render 1.jpg
    2019-11-26 14:10:33.992 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

     

    Post edited by Heckbarth on
  • Update: Just noticed there's a DAZ Studio 4.12.40 (Public Beta) and it is able to render both empty and "full" scenes alike:

    2019-11-26 14:44:46.443 Rendering image
    2019-11-26 14:44:46.464 Iray [INFO] - IMAGE:IO ::   1.0   IMAGE  io   info : Loading image "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\resources\DTHDR-RuinsB-500.hdr", pixel type "Rgb_fp", 512x256x1 pixels, 1 miplevel.
    2019-11-26 14:44:46.523 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (0 objects with 0 triangles, 0 instances yielding 0 triangles) took 0.000s
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.
    2019-11-26 14:44:46.532 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 0 textures, 0 lambdas (0 unique)
    2019-11-26 14:44:46.532 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
    2019-11-26 14:44:46.540 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
    2019-11-26 14:44:46.542 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
    2019-11-26 14:44:46.542 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
    2019-11-26 14:44:46.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
    2019-11-26 14:44:46.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
    2019-11-26 14:44:46.549 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
    2019-11-26 14:44:46.569 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
    2019-11-26 14:44:46.593 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
    2019-11-26 14:44:46.599 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 2 device(s):
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CUDA device 0 (GeForce RTX 2080)
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CUDA device 1 (GeForce RTX 2070)
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2019-11-26 14:44:46.641 Iray [VERBOSE] - IRAY:RENDER ::   1.7   IRAY   rend progr: CUDA device 0 (GeForce RTX 2080): Processing scene...
    2019-11-26 14:44:46.641 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Using OptiX version 7.0.0
    2019-11-26 14:44:46.642 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Geometry memory consumption: 0.000 B (device 1), 0.000 B (host)
    2019-11-26 14:44:46.642 Iray [VERBOSE] - IRAY:RENDER ::   1.5   IRAY   rend progr: CUDA device 1 (GeForce RTX 2070): Processing scene...
    2019-11-26 14:44:46.647 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Initializing OptiX for CUDA device 1
    2019-11-26 14:44:46.647 Iray [INFO] - IRAY:RENDER ::   1.8   IRAY   rend info : Initializing OptiX for CUDA device 0
    2019-11-26 14:44:46.649 Iray [VERBOSE] - IRAY:RENDER ::   1.8   IRAY   rend stat : Geometry memory consumption: 0.000 B (device 0), 0.000 B (host)
    2019-11-26 14:44:46.779 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Importing lights for motion time 0
    2019-11-26 14:44:46.779 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Initializing light hierarchy.
    2019-11-26 14:44:46.785 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Texture memory consumption: 0.000 B for 0 bitmaps (device 1)
    2019-11-26 14:44:46.785 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Light hierarchy initialization took 0.000s
    2019-11-26 14:44:46.787 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Lights memory consumption: 196.000 B (device 1)
    2019-11-26 14:44:46.789 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Material measurement memory consumption: 0.000 B (GPU)
    2019-11-26 14:44:46.795 Iray [VERBOSE] - IRAY:RENDER ::   1.8   IRAY   rend stat : Texture memory consumption: 0.000 B for 0 bitmaps (device 0)
    2019-11-26 14:44:46.796 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Materials memory consumption: 13.891 KiB (GPU)
    2019-11-26 14:44:46.796 Iray [VERBOSE] - IRAY:RENDER ::   1.8   IRAY   rend stat : Lights memory consumption: 196.000 B (device 0)
    2019-11-26 14:44:46.900 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Scene processed in 0.260s
    2019-11-26 14:44:46.905 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : CUDA device 1 (GeForce RTX 2070): Scene processed in 0.260s
    2019-11-26 14:44:46.911 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Allocated 96.000 MiB for frame buffer
    2019-11-26 14:44:46.913 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : CUDA device 1 (GeForce RTX 2070): Allocated 96.000 MiB for frame buffer
    2019-11-26 14:44:46.965 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Allocated 1.688 GiB of work space (2048k active samples in 0.055s)
    2019-11-26 14:44:46.970 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Used for display, optimizing for interactive usage (performance could be sacrificed)
    2019-11-26 14:44:46.981 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : CUDA device 1 (GeForce RTX 2070): Allocated 1.688 GiB of work space (2048k active samples in 0.067s)
    2019-11-26 14:44:47.012 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Allocating 1-layer frame buffer
    2019-11-26 14:44:47.059 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iterations after 0.419s.
    2019-11-26 14:44:47.103 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 0.463s.
    2019-11-26 14:44:47.141 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00003 iterations after 0.501s.
    2019-11-26 14:44:47.254 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00007 iterations after 0.614s.
    2019-11-26 14:44:47.301 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00013 iterations after 0.661s.
    2019-11-26 14:44:47.393 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00015 iterations after 0.752s.
    2019-11-26 14:44:47.482 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00022 iterations after 0.842s.
    2019-11-26 14:44:47.628 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00026 iterations after 0.988s.
    2019-11-26 14:44:47.881 Iray [VERBOSE] - IRAY:RENDER ::   1.0   IRAY   rend progr: 100.00% of image converged
    2019-11-26 14:44:47.881 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00034 iterations after 1.241s.
    2019-11-26 14:44:47.993 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Convergence threshold reached.
    2019-11-26 14:44:48.446 Saved image: C:\Users\Karsten\AppData\Roaming\DAZ 3D\Studio4 Public Build\temp\render\r.png
    2019-11-26 14:44:48.457 Finished Rendering
    2019-11-26 14:44:48.491 Total Rendering Time: 2.10 seconds

     

    Weird, but at least I'm happy it*s working again.

     

  • Heckbarth said:

    Update: Just noticed there's a DAZ Studio 4.12.40 (Public Beta) and it is able to render both empty and "full" scenes alike:

    2019-11-26 14:44:46.443 Rendering image
    2019-11-26 14:44:46.464 Iray [INFO] - IMAGE:IO ::   1.0   IMAGE  io   info : Loading image "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\resources\DTHDR-RuinsB-500.hdr", pixel type "Rgb_fp", 512x256x1 pixels, 1 miplevel.
    2019-11-26 14:44:46.523 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (0 objects with 0 triangles, 0 instances yielding 0 triangles) took 0.000s
    2019-11-26 14:44:46.524 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.
    2019-11-26 14:44:46.532 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 0 textures, 0 lambdas (0 unique)
    2019-11-26 14:44:46.532 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
    2019-11-26 14:44:46.540 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
    2019-11-26 14:44:46.542 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
    2019-11-26 14:44:46.542 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
    2019-11-26 14:44:46.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
    2019-11-26 14:44:46.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
    2019-11-26 14:44:46.549 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
    2019-11-26 14:44:46.569 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
    2019-11-26 14:44:46.593 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
    2019-11-26 14:44:46.599 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 2 device(s):
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CUDA device 0 (GeForce RTX 2080)
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CUDA device 1 (GeForce RTX 2070)
    2019-11-26 14:44:46.635 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2019-11-26 14:44:46.641 Iray [VERBOSE] - IRAY:RENDER ::   1.7   IRAY   rend progr: CUDA device 0 (GeForce RTX 2080): Processing scene...
    2019-11-26 14:44:46.641 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Using OptiX version 7.0.0
    2019-11-26 14:44:46.642 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Geometry memory consumption: 0.000 B (device 1), 0.000 B (host)
    2019-11-26 14:44:46.642 Iray [VERBOSE] - IRAY:RENDER ::   1.5   IRAY   rend progr: CUDA device 1 (GeForce RTX 2070): Processing scene...
    2019-11-26 14:44:46.647 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Initializing OptiX for CUDA device 1
    2019-11-26 14:44:46.647 Iray [INFO] - IRAY:RENDER ::   1.8   IRAY   rend info : Initializing OptiX for CUDA device 0
    2019-11-26 14:44:46.649 Iray [VERBOSE] - IRAY:RENDER ::   1.8   IRAY   rend stat : Geometry memory consumption: 0.000 B (device 0), 0.000 B (host)
    2019-11-26 14:44:46.779 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Importing lights for motion time 0
    2019-11-26 14:44:46.779 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Initializing light hierarchy.
    2019-11-26 14:44:46.785 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Texture memory consumption: 0.000 B for 0 bitmaps (device 1)
    2019-11-26 14:44:46.785 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Light hierarchy initialization took 0.000s
    2019-11-26 14:44:46.787 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Lights memory consumption: 196.000 B (device 1)
    2019-11-26 14:44:46.789 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Material measurement memory consumption: 0.000 B (GPU)
    2019-11-26 14:44:46.795 Iray [VERBOSE] - IRAY:RENDER ::   1.8   IRAY   rend stat : Texture memory consumption: 0.000 B for 0 bitmaps (device 0)
    2019-11-26 14:44:46.796 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Materials memory consumption: 13.891 KiB (GPU)
    2019-11-26 14:44:46.796 Iray [VERBOSE] - IRAY:RENDER ::   1.8   IRAY   rend stat : Lights memory consumption: 196.000 B (device 0)
    2019-11-26 14:44:46.900 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Scene processed in 0.260s
    2019-11-26 14:44:46.905 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : CUDA device 1 (GeForce RTX 2070): Scene processed in 0.260s
    2019-11-26 14:44:46.911 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Allocated 96.000 MiB for frame buffer
    2019-11-26 14:44:46.913 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : CUDA device 1 (GeForce RTX 2070): Allocated 96.000 MiB for frame buffer
    2019-11-26 14:44:46.965 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Allocated 1.688 GiB of work space (2048k active samples in 0.055s)
    2019-11-26 14:44:46.970 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : CUDA device 0 (GeForce RTX 2080): Used for display, optimizing for interactive usage (performance could be sacrificed)
    2019-11-26 14:44:46.981 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : CUDA device 1 (GeForce RTX 2070): Allocated 1.688 GiB of work space (2048k active samples in 0.067s)
    2019-11-26 14:44:47.012 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Allocating 1-layer frame buffer
    2019-11-26 14:44:47.059 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iterations after 0.419s.
    2019-11-26 14:44:47.103 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 0.463s.
    2019-11-26 14:44:47.141 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00003 iterations after 0.501s.
    2019-11-26 14:44:47.254 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00007 iterations after 0.614s.
    2019-11-26 14:44:47.301 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00013 iterations after 0.661s.
    2019-11-26 14:44:47.393 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00015 iterations after 0.752s.
    2019-11-26 14:44:47.482 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00022 iterations after 0.842s.
    2019-11-26 14:44:47.628 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00026 iterations after 0.988s.
    2019-11-26 14:44:47.881 Iray [VERBOSE] - IRAY:RENDER ::   1.0   IRAY   rend progr: 100.00% of image converged
    2019-11-26 14:44:47.881 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00034 iterations after 1.241s.
    2019-11-26 14:44:47.993 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Convergence threshold reached.
    2019-11-26 14:44:48.446 Saved image: C:\Users\Karsten\AppData\Roaming\DAZ 3D\Studio4 Public Build\temp\render\r.png
    2019-11-26 14:44:48.457 Finished Rendering
    2019-11-26 14:44:48.491 Total Rendering Time: 2.10 seconds

     

    Weird, but at least I'm happy it*s working again.

     

    The updated Public Beta includes an Iray update, which deals with some bug fixes.

  • takezo_3001takezo_3001 Posts: 1,974
    • Puppeteer pane
      • ...
    • Map Transfer
      • ...
    • BVH Importer/Exporter
      • ...
    • Hexagon Bridge
      • ...
    • Bryce Bridge
      • ...

    This has me more than excited to find out more as I rely heavily on puppeteer! 

  • marble:

    As I said, there are two separate fallback issues. (1) One is an immediate fallback for RTX users as soon as you activate Iray viewport (both 4.12.0.86 and 4.12.1.16) with R440 drivers.

    (2) The other one which doesn't happen in 4.12.0.86 but only in beta seems to be triggered by some materials and it happens with all drivers and cards.

    Hmmm.  Curious.  Do i remember that right that you are on Win10?

    I never get issue#1.  One explanation is my OS is Win 7(64) Pro.  Have come across people complaining about Win10 mem management issues for various software.  Am avoiding Win 10 upgrade like the plague, so didn't read anymore in depth.  Also, probably not related, but post anyway:  also purged my startup setup since fnding out my X-Ray camera on start load was causing issues.  Yet loading that same camera after something was in scene cause no such issue.

    Issue #2 is my problem.  Support seems busy so not expecting any anything really until they have anything tangible.  Though acknowledgement would be nice.  Hope to hear from them in next week or so.

    • Puppeteer pane
      • ...
    • Map Transfer
      • ...
    • BVH Importer/Exporter
      • ...
    • Hexagon Bridge
      • ...
    • Bryce Bridge
      • ...

    This has me more than excited to find out more as I rely heavily on puppeteer! 

    Hope you report back.  Puppeter is cat's meow! Hope they made the tab layout different so when you have lots of tabs that you don't have to cycle L-R a long time.

  • takezo_3001takezo_3001 Posts: 1,974
    • Puppeteer pane
      • ...
    • Map Transfer
      • ...
    • BVH Importer/Exporter
      • ...
    • Hexagon Bridge
      • ...
    • Bryce Bridge
      • ...

    This has me more than excited to find out more as I rely heavily on puppeteer! 

    Hope you report back.  Puppeter is cat's meow! Hope they made the tab layout different so when you have lots of tabs that you don't have to cycle L-R a long time.

    Will do, I'm currently doing some rendering though... I'm hoping for an official word on what was added to it.

  • marblemarble Posts: 7,500
    edited November 2019

    marble:

    As I said, there are two separate fallback issues. (1) One is an immediate fallback for RTX users as soon as you activate Iray viewport (both 4.12.0.86 and 4.12.1.16) with R440 drivers.

    (2) The other one which doesn't happen in 4.12.0.86 but only in beta seems to be triggered by some materials and it happens with all drivers and cards.

    Hmmm.  Curious.  Do i remember that right that you are on Win10?

    I never get issue#1.  One explanation is my OS is Win 7(64) Pro.  Have come across people complaining about Win10 mem management issues for various software.  Am avoiding Win 10 upgrade like the plague, so didn't read anymore in depth.  Also, probably not related, but post anyway:  also purged my startup setup since fnding out my X-Ray camera on start load was causing issues.  Yet loading that same camera after something was in scene cause no such issue.

    Issue #2 is my problem.  Support seems busy so not expecting any anything really until they have anything tangible.  Though acknowledgement would be nice.  Hope to hear from them in next week or so.

    Yes, I am on Windows 10. I don't seem to have the same VRAM problems with DAZ Studio 4.11 though but I have Optix Prime switched off for that. So what I'm doing (which confuses me no-end when it comes to remembering which version had which problem) is using 4.12 Beta as much as possible other than when it won't render a scene without falling back to CPU. Then I load it in 4.11 to render. Generally, I find 4.12 much nicer to work with in terms of Viewport operation (much smoother) and render speed (when it works).

    X-Ray Camera??? Whassat???

    Post edited by marble on
  • PDSmithPDSmith Posts: 712

    I've been haveing the same issue for months and like I mentioned in that other thread I started. I seemed to have a tentative fix going.  I'm running on close to 3 hours of solid test futzing and not one drop to CPU rendering.

    loaded up the new beta  4.12.1.40  and windows 10 behind my back updated my drivers to 432.00. so I'm not sure if its a clean install or not  but  all three graphic cards are online.  RTX 2070, and 2 GTX 960's.  I can use denoise, dforce and other features. Tested them, ran them all and so far so good.

    Just wanted to point out atleast one person got lucky so far, hope what I gave helps others.  

    -PDSmith

  • marblemarble Posts: 7,500

    Oh I give up. After reading that some of the bugs had been addressed in the new Beta, I went ahead and installed it over the previous Beta. Now I see that it has gone back to falling back to CPU on rendering an image series. It is plain to see in GPU-Z ... VRAM does not drop between frame one and frame two (it should - and it does with a working system). Instead, VRAM not only remains high but increases so that the 8GB limit is breached and, hey-presto, CPU rendering.

    I am fuming now because I can't get back to the previous beta which had fall-back problems but not with the image series.

  • Wildman oSWildman oS Posts: 121
    edited November 2019

    As I said above, I am experiancing NO problems with cpu fallback if I use Nvidia studio drivers v431.86

    even with the latest beta of daz studio v4.12.1.40

    but I notice above that somebody has reported cpu dropback with even the latest nvidia studio drivers v441.28

    You guys should stop beating your head against the wall, use nvidia studio drivers v431.86 and wait until nvidia fix the problem.

     

    I have not yet tested the latest nvidia studio drivers v441.28 myself

    FYI for comparison:

    Windows 10pro x64 v1903

    Intel i9 9900k, nvidia rtx2080ti, 32gb ram, too many hard drives

    Post edited by Wildman oS on
  • marblemarble Posts: 7,500

    As I said above, I am experiancing no problems with cpu fallback if I use Nvidia studio drivers v431.86

    You guys should stop beating your head against the wall and wait until nvidia fix the problem.

    I have not yet tested the latest beta of daz studio v4.12.1.40 nor the latest nvidia studio drivers v441.28

    It was happening for me with 431.86 which is why I updated them. I'm running 441.12 drivers now and, after the DAZ Studio Beta update, am back to square one with the CPU dropping out on image series renders.

  • Wildman oSWildman oS Posts: 121
    edited November 2019
    marble said:

    It was happening for me with 431.86 which is why I updated them. I'm running 441.12 drivers now and, after the DAZ Studio Beta update, am back to square one with the CPU dropping out on image series renders.

    I'm sorry to hear this, also sorry to sound so exhasperated, I was assuming the way I solved my own cpu fallback problems would solve it for all.

    Have you tried the latest nvidia studio v441.28 drivers yet ?

    or maybe there's a windows issue here too

    or maybe fallback to drivers prior to nvidia 431.86

    EDIT: typos as always

    Post edited by Wildman oS on
  • I've gone from everything working in 4.12.1.16 to having DAZ Studio crash to desktop as soon as it tries to render with the gpu in 4.12.1.40. I wish I could get the old beta back.

     

    For reference:

    Windows 10 Home 64-bit version 1903

    NVIDIA GeForce RTX 2080 (I have tried several drivers to no effect)

    Intel i7-8700k

    64gb RAM

     

  • nonesuch00nonesuch00 Posts: 18,120

    I have upgraded to the new public beta 4.1.12.0.40 from 4.1.12.0.16 and t there is one big fix:

    a) When I render in DAZ Studio, DAZ Studio no longer allocates and writes to my system disk repeatedly; not freeing the allocated space such that I eventually start running out of space on my system disk  until I exit DAZ Studio and reboot my laptop. So not seeing my system disk disappear every time I do a DAZ render is a big improvement. 

     

  • takezo_3001takezo_3001 Posts: 1,974
    • Puppeteer pane
      • ...
    • Map Transfer
      • ...
    • BVH Importer/Exporter
      • ...
    • Hexagon Bridge
      • ...
    • Bryce Bridge
      • ...

    This has me more than excited to find out more as I rely heavily on puppeteer! 

    Hope you report back.  Puppeter is cat's meow! Hope they made the tab layout different so when you have lots of tabs that you don't have to cycle L-R a long time.

    Puppeteer pane

    • Improved general performance
    • Fixed (significant) memory leaks in key preview, record, mouse drag, and playback operations, as well as in context menus
    • Removed dependencies on legacy support libraries

    Now what specifically does rob mean with removing dependencies on legacy support libraries?

  • Now what specifically does rob mean with removing dependencies on legacy support libraries?

    It basically boils down to having done work necessary to allow development of the named area to move forward with the application.

  • takezo_3001takezo_3001 Posts: 1,974
    Now what specifically does rob mean with removing dependencies on legacy support libraries?

    It basically boils down to having done work necessary to allow development of the named area to move forward with the application.

    Cool, thanks a ton for the speedy answer!laugh Happy thanksgiving to ya!

  • marble said:
     

    Yes, I am on Windows 10.

    smiley Had actually meant the windows 10 question for Sylvie as she has an RTX card too.  GTX and RTX cards seem to respond differently on some issues. 

    But still good to know. smiley

    marble said:

    X-Ray Camera??? Whassat???

    That was what we originally posted about on Page 28 of this thread.  My clarifying reply was 7th post from top.  X-Ray camera helpful in many ways for indoor scenes, though you need to manage the planes that come with the camera.

  • Saxa -- SDSaxa -- SD Posts: 872
    edited November 2019
    PDSmith said:

    I'm running on close to 3 hours of solid test futzing and not one drop to CPU rendering.

    loaded up the new beta  4.12.1.40  and windows 10 behind my back updated my drivers to 432.00.

    Just wanted to point out atleast one person got lucky so far, hope what I gave helps others.  

    -PDSmith

    Thanks for sharing! Have been happily using 4.12.0.86 with 441.12 driver with zero issue.  If this issue drags on without a fix, and I need to get to next stage of workflow and use the beta with improvements, then will test 432.00.  Got this issue originally on 4.12.1.16 with 430.39 and then tried 430.86 and issue persisted.

    You guys should stop beating your head against the wall, use nvidia studio drivers v431.86 and wait until nvidia fix the problem.

    LOL.  Am hardly banging my head on this issue.

    Am using 4.12.0.86 for day long sessions without issue on 441.12.

    Am posting and working on this drop to CPU issue on the side, because SOMEONE has to report these issues and try to get bug fixes in. 

    Post edited by Saxa -- SD on
  • marblemarble Posts: 7,500
    edited November 2019
    marble said:
     

    Yes, I am on Windows 10.

    smiley Had actually meant the windows 10 question for Sylvie as she has an RTX card too.  GTX and RTX cards seem to respond differently on some issues. 

    But still good to know. smiley

    marble said:

    X-Ray Camera??? Whassat???

    That was what we originally posted about on Page 28 of this thread.  My clarifying reply was 7th post from top.  X-Ray camera helpful in many ways for indoor scenes, though you need to manage the planes that come with the camera.

     

    Oh boy, I missed the bus on both blush !

    I'll scan back throught the thread, thanks.

    Post edited by marble on
Sign In or Register to comment.