Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Well this update fixed the movement issue with the keyboard but the saving then crashing on render unless you restart your computer problem still remains
And also to note it's made it far worse with rendering a scene that I could render before this update now won't at all will cause my entire pc to simply freeze and force a restart!
Yes you need to put 2.
If you want to test it.
Clear the log, put 1, do a render and look at the memory usage of each card in the log.
Then, put 2, redo a render and compare the memory usage of the each card again.
You will notice that in the second run the geometry memory is the same everywhere but on the second run, your textures memory is inequal on each card AND a lot less because the driver tried to split it across the 2 cards...
I'm not sure if it's doing that with all turing cards but with my 2 x 2080 ti with nvlink, that's what is happening.
@TheTreeInFront mind posting excerpts of your log files showing texture memory usage from each of those two test cases with your 2080Ti's? Do so, and afaik you will be the first user on this forum to actually document memory pooling on Turing cards in DS/Iray as working.
So with Daz public beta 4.12.1.109
Nvidia drivers 445.87 Game ready
Each card show in the Nvidia panel : Dedicated video memory : 11264 MB GDDR6
Theses are 2 x GeForce RTX™ 2080 Ti WINDFORCE OC 11G
I have a scene with 1 x Victoria 8, 1 x Olympia 8 and 1 x Alexandra 8.
Alexandra is wearing the preset Legend !Full Armor from the "The Legend" product by Aeon Soul.
NVLink Peer Group Size : 1
2020-05-14 20:49:15.483 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 1353 textures, 76 lambdas (40 unique)
2020-05-14 20:49:15.541 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 0.000s
2020-05-14 20:49:15.541 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-05-14 20:49:15.557 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-05-14 20:49:15.559 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-05-14 20:49:15.559 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-05-14 20:49:15.559 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-05-14 20:49:15.561 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-05-14 20:49:15.561 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-05-14 20:49:15.612 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-05-14 20:49:15.624 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-05-14 20:49:15.626 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-05-14 20:49:15.700 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 2 device(s):
2020-05-14 20:49:15.700 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti)
2020-05-14 20:49:15.704 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti)
2020-05-14 20:49:15.704 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-05-14 20:49:15.704 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend progr: CUDA device 1 (GeForce RTX 2080 Ti): Processing scene...
2020-05-14 20:49:15.704 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend progr: CUDA device 0 (GeForce RTX 2080 Ti): Processing scene...
2020-05-14 20:49:15.828 Iray [VERBOSE] - IRAY:RENDER :: 1.8 IRAY rend stat : Geometry memory consumption: 379.364 MiB (device 1), 0.000 B (host)
2020-05-14 20:49:15.832 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Using OptiX version 7.1.0
2020-05-14 20:49:15.834 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Geometry memory consumption: 379.364 MiB (device 0), 0.000 B (host)
2020-05-14 20:49:16.123 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Initializing OptiX for CUDA device 1
2020-05-14 20:49:16.123 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Initializing OptiX for CUDA device 0
2020-05-14 20:49:32.539 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Texture memory consumption: 2.921 GiB for 146 bitmaps (device 0)
2020-05-14 20:49:32.539 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Importing lights for motion time 0
2020-05-14 20:49:32.543 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Initializing light hierarchy.
2020-05-14 20:49:32.555 Iray [VERBOSE] - IRAY:RENDER :: 1.8 IRAY rend stat : Texture memory consumption: 2.921 GiB for 146 bitmaps (device 1)
2020-05-14 20:49:32.567 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Light hierarchy initialization took 0.024s
2020-05-14 20:49:32.569 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Lights memory consumption: 948.000 B (device 0)
2020-05-14 20:49:32.573 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-05-14 20:49:32.579 Iray [VERBOSE] - IRAY:RENDER :: 1.8 IRAY rend stat : Lights memory consumption: 948.000 B (device 1)
2020-05-14 20:49:33.399 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Materials memory consumption: 732.105 KiB (GPU)
2020-05-14 20:49:33.399 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : PTX code (257.080 KiB) for SM 7.5 generated in 0.826s
2020-05-14 20:49:33.401 Iray [VERBOSE] - IRAY:RENDER :: 1.8 IRAY rend stat : PTX code (257.080 KiB) for SM 7.5 generated in 0.000s
2020-05-14 20:49:33.696 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : JIT-linking wavefront kernel in 0.053s
2020-05-14 20:49:33.710 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : JIT-linking wavefront kernel in 0.063s
2020-05-14 20:49:33.710 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : JIT-linking mega kernel in 0.014s
2020-05-14 20:49:33.710 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Scene processed in 18.006s
2020-05-14 20:49:33.712 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : JIT-linking mega kernel in 0.002s
2020-05-14 20:49:33.716 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 36.558 MiB for frame buffer
2020-05-14 20:49:33.716 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Scene processed in 18.012s
2020-05-14 20:49:33.720 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 36.558 MiB for frame buffer
2020-05-14 20:49:33.800 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.084s)
2020-05-14 20:49:33.804 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.082s)
2020-05-14 20:49:33.810 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-14 20:49:33.810 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-14 20:49:34.027 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : Allocating 1-layer frame buffer
NVLink Peer Group Size : 2
2020-05-14 20:53:15.455 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 1353 textures, 76 lambdas (40 unique)
2020-05-14 20:53:15.493 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 0.000s
2020-05-14 20:53:15.495 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-05-14 20:53:15.505 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-05-14 20:53:15.507 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-05-14 20:53:15.507 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-05-14 20:53:15.507 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-05-14 20:53:15.507 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-05-14 20:53:15.507 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-05-14 20:53:15.521 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-05-14 20:53:15.531 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-05-14 20:53:15.531 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-05-14 20:53:15.579 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 2 device(s):
2020-05-14 20:53:15.579 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti)
2020-05-14 20:53:15.583 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti)
2020-05-14 20:53:15.583 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-05-14 20:53:15.583 Iray [INFO] - IRAY:RENDER :: 1.13 IRAY rend progr: CUDA device 1 (GeForce RTX 2080 Ti): Processing scene...
2020-05-14 20:53:15.583 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend progr: CUDA device 0 (GeForce RTX 2080 Ti): Processing scene...
2020-05-14 20:53:15.783 Iray [VERBOSE] - IRAY:RENDER :: 1.2 IRAY rend stat : Geometry memory consumption: 379.364 MiB (device 0), 0.000 B (host)
2020-05-14 20:53:15.787 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : Using OptiX version 7.1.0
2020-05-14 20:53:15.789 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Geometry memory consumption: 379.364 MiB (device 1), 0.000 B (host)
2020-05-14 20:53:15.791 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : Initializing OptiX for CUDA device 0
2020-05-14 20:53:15.793 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing OptiX for CUDA device 1
2020-05-14 20:53:31.708 Iray [VERBOSE] - IRAY:RENDER :: 1.2 IRAY rend stat : Texture memory consumption: 1.471 GiB for 62 bitmaps (device 0)
2020-05-14 20:53:31.714 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Importing lights for motion time 0
2020-05-14 20:53:31.714 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Texture memory consumption: 1.450 GiB for 84 bitmaps (device 1)
2020-05-14 20:53:31.714 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing light hierarchy.
2020-05-14 20:53:31.716 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Light hierarchy initialization took 0.001s
2020-05-14 20:53:31.716 Iray [VERBOSE] - IRAY:RENDER :: 1.2 IRAY rend stat : Lights memory consumption: 948.000 B (device 0)
2020-05-14 20:53:31.722 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Lights memory consumption: 948.000 B (device 1)
2020-05-14 20:53:31.724 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-05-14 20:53:31.915 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Materials memory consumption: 732.105 KiB (GPU)
2020-05-14 20:53:31.915 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : PTX code (257.080 KiB) for SM 7.5 generated in 0.193s
2020-05-14 20:53:31.921 Iray [VERBOSE] - IRAY:RENDER :: 1.2 IRAY rend stat : PTX code (257.080 KiB) for SM 7.5 generated in 0.000s
2020-05-14 20:53:32.071 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : JIT-linking wavefront kernel in 0.033s
2020-05-14 20:53:32.073 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : JIT-linking mega kernel in 0.002s
2020-05-14 20:53:32.073 Iray [INFO] - IRAY:RENDER :: 1.13 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Scene processed in 16.490s
2020-05-14 20:53:32.089 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : JIT-linking wavefront kernel in 0.032s
2020-05-14 20:53:32.091 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : JIT-linking mega kernel in 0.002s
2020-05-14 20:53:32.091 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Scene processed in 16.507s
2020-05-14 20:53:32.093 Iray [INFO] - IRAY:RENDER :: 1.13 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 36.558 MiB for frame buffer
2020-05-14 20:53:32.099 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 36.558 MiB for frame buffer
2020-05-14 20:53:32.195 Iray [INFO] - IRAY:RENDER :: 1.13 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.095s)
2020-05-14 20:53:32.195 Iray [INFO] - IRAY:RENDER :: 1.13 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-14 20:53:32.201 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.095s)
2020-05-14 20:53:32.201 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-14 20:53:32.466 Iray [INFO] - IRAY:RENDER :: 1.13 IRAY rend info : Allocating 1-layer frame buffer
Speed result, even thou I'm not sure if it's significative of anything.
each card on their own
2020-05-14 20:49:56.723 Total Rendering Time: 56.78 seconds
nvlink group with the 2 cards
2020-05-14 20:53:53.941 Total Rendering Time: 51.92 seconds
A little context.
I would'nt want anyone to rush getting two card thinking they will have twice the memory. We probably need a lot more tests to know what is really happening.
Yes my log was positive so I did'nt push it personaly thinking that with time it would just get better. But getting the info from the previous post, I did more test and a logical good test would be to cram a lot of texture and see if I can get more than 11 Gib of textures to render.
This is where it get ugly. I tried the last Public Beta. As I started rendering with 12 figures I got Windows to simply reboot. After a lot of tests I realised that the memory limit is quite lower than it should.
Look at this log. It's the result of 5 figures with heavy clothes.
2020-05-15 03:38:49.988 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 5061 textures, 71 lambdas (40 unique)
2020-05-15 03:38:50.152 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 0.000s
2020-05-15 03:38:50.154 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-05-15 03:38:50.162 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-05-15 03:38:50.164 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-05-15 03:38:50.168 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-05-15 03:38:50.168 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-05-15 03:38:50.170 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-05-15 03:38:50.170 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-05-15 03:38:50.254 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-05-15 03:38:50.274 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-05-15 03:38:50.276 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-05-15 03:38:50.500 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 2 device(s):
2020-05-15 03:38:50.500 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti)
2020-05-15 03:38:50.500 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti)
2020-05-15 03:38:50.506 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-05-15 03:38:50.506 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend progr: CUDA device 1 (GeForce RTX 2080 Ti): Processing scene...
2020-05-15 03:38:50.506 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend progr: CUDA device 0 (GeForce RTX 2080 Ti): Processing scene...
2020-05-15 03:38:51.190 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Geometry memory consumption: 1.590 GiB (device 0), 0.000 B (host)
2020-05-15 03:38:51.194 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Geometry memory consumption: 1.590 GiB (device 1), 0.000 B (host)
2020-05-15 03:38:51.196 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : Using OptiX version 7.1.0
2020-05-15 03:38:51.526 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : Initializing OptiX for CUDA device 0
2020-05-15 03:38:51.526 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Initializing OptiX for CUDA device 1
2020-05-15 03:38:54.920 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2020-05-15 03:39:11.292 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Texture memory consumption: 1.603 GiB for 89 bitmaps (device 1)
2020-05-15 03:39:11.292 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Texture memory consumption: 1.615 GiB for 102 bitmaps (device 0)
2020-05-15 03:39:11.292 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Importing lights for motion time 0
2020-05-15 03:39:11.294 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Initializing light hierarchy.
2020-05-15 03:39:11.318 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Light hierarchy initialization took 0.018s
2020-05-15 03:39:11.318 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Lights memory consumption: 948.000 B (device 1)
2020-05-15 03:39:11.324 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-05-15 03:39:11.328 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Lights memory consumption: 948.000 B (device 0)
2020-05-15 03:39:12.032 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : PTX code (257.016 KiB) for SM 7.5 generated in 0.705s
2020-05-15 03:39:12.032 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Materials memory consumption: 2.325 MiB (GPU)
2020-05-15 03:39:12.034 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : PTX code (257.016 KiB) for SM 7.5 generated in 0.000s
2020-05-15 03:39:12.648 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : JIT-linking wavefront kernel in 0.366s
2020-05-15 03:39:13.016 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : JIT-linking mega kernel in 0.363s
2020-05-15 03:39:13.016 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Scene processed in 22.511s
2020-05-15 03:39:13.034 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : JIT-linking wavefront kernel in 0.385s
2020-05-15 03:39:13.036 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 37.889 MiB for frame buffer
2020-05-15 03:39:13.040 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : JIT-linking mega kernel in 0.002s
2020-05-15 03:39:13.042 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Scene processed in 22.536s
2020-05-15 03:39:13.092 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.051s)
2020-05-15 03:39:13.092 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 37.889 MiB for frame buffer
2020-05-15 03:39:13.102 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-15 03:39:13.148 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.052s)
2020-05-15 03:39:13.148 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-15 03:39:13.166 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: CUDA device 1 (GeForce RTX 2080 Ti): out of memory (while launching CUDA renderer in <internal>:848)
2020-05-15 03:39:13.166 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: CUDA device 1 (GeForce RTX 2080 Ti): Failed to launch renderer
2020-05-15 03:39:13.166 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.9 IRAY rend error: CUDA device 1 (GeForce RTX 2080 Ti): Device failed while rendering
2020-05-15 03:39:13.174 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.13 IRAY rend error: CUDA device 0 (GeForce RTX 2080 Ti): out of memory (while launching CUDA renderer in <internal>:848)
2020-05-15 03:39:13.174 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.13 IRAY rend error: CUDA device 0 (GeForce RTX 2080 Ti): Failed to launch renderer
2020-05-15 03:39:13.174 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.2 IRAY rend error: CUDA device 0 (GeForce RTX 2080 Ti): Device failed while rendering
2020-05-15 03:39:13.180 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER :: 1.2 IRAY rend warn : All available GPUs failed.
2020-05-15 03:39:13.180 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.2 IRAY rend error: Fallback to CPU not allowed.
2020-05-15 03:39:13.186 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.2 IRAY rend error: All workers failed: aborting render
2020-05-15 03:39:13.192 Iray Render error: Internal rendering error.
2020-05-15 03:39:13.378 Saved image: E:\DAZ\Temp_files\render\r.png
2020-05-15 03:39:13.392 Finished Rendering
2020-05-15 03:39:13.424 Total Rendering Time: 1 minutes 12.44 seconds
2020-05-15 03:39:16.763 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Device statistics:
2020-05-15 03:39:16.763 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): 0 iterations, 22.863s init, 0.027s render
2020-05-15 03:39:16.763 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): 0 iterations, 22.655s init, 0.033s render
This should have worked !
Now with one of thoses genesis 8 (and her clothes) deleted from the same scene
2020-05-15 03:41:20.197 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 3794 textures, 50 lambdas (27 unique)
2020-05-15 03:41:20.315 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 0.000s
2020-05-15 03:41:20.315 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-05-15 03:41:20.323 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-05-15 03:41:20.325 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-05-15 03:41:20.325 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-05-15 03:41:20.329 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-05-15 03:41:20.329 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-05-15 03:41:20.329 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-05-15 03:41:20.337 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-05-15 03:41:20.347 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-05-15 03:41:20.353 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-05-15 03:41:20.353 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Available GPU memory has increased since out-of-memory failure. Re-enable CUDA device 1.
2020-05-15 03:41:20.353 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Available GPU memory has increased since out-of-memory failure. Re-enable CUDA device 0.
2020-05-15 03:41:20.359 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 2 device(s):
2020-05-15 03:41:20.363 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti)
2020-05-15 03:41:20.363 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti)
2020-05-15 03:41:20.363 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-05-15 03:41:20.363 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend progr: CUDA device 0 (GeForce RTX 2080 Ti): Processing scene...
2020-05-15 03:41:20.363 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend progr: CUDA device 1 (GeForce RTX 2080 Ti): Processing scene...
2020-05-15 03:41:20.921 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Geometry memory consumption: 1.247 GiB (device 1), 0.000 B (host)
2020-05-15 03:41:20.921 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Geometry memory consumption: 1.247 GiB (device 0), 0.000 B (host)
2020-05-15 03:41:20.921 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : Initializing OptiX for CUDA device 1
2020-05-15 03:41:20.921 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Initializing OptiX for CUDA device 0
2020-05-15 03:41:36.653 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Texture memory consumption: 1.398 GiB for 74 bitmaps (device 1)
2020-05-15 03:41:36.653 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Texture memory consumption: 1.410 GiB for 87 bitmaps (device 0)
2020-05-15 03:41:36.653 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : Importing lights for motion time 0
2020-05-15 03:41:36.653 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : Initializing light hierarchy.
2020-05-15 03:41:36.661 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : Light hierarchy initialization took 0.002s
2020-05-15 03:41:36.663 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Lights memory consumption: 948.000 B (device 1)
2020-05-15 03:41:36.663 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Lights memory consumption: 948.000 B (device 0)
2020-05-15 03:41:36.669 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-05-15 03:41:36.813 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : PTX code (181.076 KiB) for SM 7.5 generated in 0.137s
2020-05-15 03:41:36.813 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Materials memory consumption: 1.766 MiB (GPU)
2020-05-15 03:41:36.815 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : PTX code (181.076 KiB) for SM 7.5 generated in 0.000s
2020-05-15 03:41:36.929 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : JIT-linking wavefront kernel in 0.053s
2020-05-15 03:41:36.947 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : JIT-linking wavefront kernel in 0.069s
2020-05-15 03:41:36.947 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : JIT-linking mega kernel in 0.013s
2020-05-15 03:41:36.947 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Scene processed in 16.579s
2020-05-15 03:41:36.949 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : JIT-linking mega kernel in 0.002s
2020-05-15 03:41:36.949 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Scene processed in 16.586s
2020-05-15 03:41:36.955 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 37.889 MiB for frame buffer
2020-05-15 03:41:36.955 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.000s)
2020-05-15 03:41:36.955 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-15 03:41:36.959 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 37.889 MiB for frame buffer
2020-05-15 03:41:36.959 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.000s)
2020-05-15 03:41:36.959 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-05-15 03:41:37.147 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Allocating 1-layer frame buffer
2020-05-15 03:41:37.245 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 16.881s.
2020-05-15 03:41:37.261 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00003 iterations after 16.898s.
2020-05-15 03:41:37.309 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00005 iterations after 16.946s.
2020-05-15 03:41:37.349 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00008 iterations after 16.985s.
2020-05-15 03:41:37.467 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00012 iterations after 17.103s.
2020-05-15 03:41:37.733 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00016 iterations after 17.369s.
2020-05-15 03:41:37.751 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00024 iterations after 17.388s.
2020-05-15 03:41:38.281 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 80.62% of image converged
2020-05-15 03:41:38.281 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00032 iterations after 17.918s.
2020-05-15 03:41:38.291 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00048 iterations after 17.927s.
2020-05-15 03:41:38.817 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 83.97% of image converged
2020-05-15 03:41:38.817 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00064 iterations after 18.453s.
2020-05-15 03:41:39.085 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00088 iterations after 18.721s.
2020-05-15 03:41:39.605 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 86.77% of image converged
2020-05-15 03:41:39.609 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00110 iterations after 19.246s.
2020-05-15 03:41:39.957 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00137 iterations after 19.592s.
2020-05-15 03:41:40.785 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 89.46% of image converged
2020-05-15 03:41:40.785 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00163 iterations after 20.421s.
2020-05-15 03:41:40.905 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00192 iterations after 20.542s.
2020-05-15 03:41:41.561 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 91.58% of image converged
2020-05-15 03:41:41.561 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00216 iterations after 21.198s.
2020-05-15 03:41:41.849 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00245 iterations after 21.485s.
2020-05-15 03:41:42.441 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 93.20% of image converged
2020-05-15 03:41:42.455 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00272 iterations after 22.091s.
2020-05-15 03:41:42.845 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 93.83% of image converged
2020-05-15 03:41:42.845 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00302 iterations after 22.482s.
2020-05-15 03:41:43.765 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00330 iterations after 23.402s.
2020-05-15 03:41:43.809 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 94.92% of image converged
2020-05-15 03:41:43.809 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00360 iterations after 23.446s.
2020-05-15 03:41:44.731 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00389 iterations after 24.368s.
2020-05-15 03:41:44.825 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 95.90% of image converged
2020-05-15 03:41:44.825 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00420 iterations after 24.460s.
2020-05-15 03:41:44.905 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Convergence threshold reached.
2020-05-15 03:41:46.159 Saved image: E:\DAZ\Temp_files\render\r.png
2020-05-15 03:41:46.171 Finished Rendering
2020-05-15 03:41:46.195 Total Rendering Time: 58.84 seconds
I can only say my opinion on what is happening. Now it's nice to have the "out of memory" error instead of just having Windows restart the computer after going from the latest Game Ready driver 445.87 to the last older Studio drivers 442.92.
At first I tried to see why Windows was rebooting. Downclocking the cards etc, but in MSI afterburner it was pretty clear that even if the log was showing a geometry and texture of 2 gig of data each, the real memory usage on one video card was going from 1 gig to 9.5 gig and 2 seconds later it stopped.
Maybe the static memory for the data is one thing but when the render itself start, all the cuda core (4352 of them) also need some video mem space as working registers to do their own calculations in parallel on each card and it's there that it goes down the drain.
I would have hoped to have a nice flat 22 gig of memory to put stuff and render a lot more textures. But it's not happening right now for me. Look like I have about 5 Gib on each card to render. My screen itself is 3440 x 1440 so that take a few bytes of video mem and the final picture will also draw a little bit, but not that much.
Maybe a setting in the Nvidia control panel, there are so many. But I'm always in SLI because with SLI off, it completely cut the NVLink and then each card simply copy the texture memory (even if the link stay physically connected).
It's the first version and even in beta, more than a year after the hardware is out so I guess we just need to wait a little more.
I recently downloaded the latest BETA 12.2.6. I'm not sure which version was my old DAZ Studio BETA 12 but it ran better.
The latest version(12.2.6) completely made DAZ useless for me to render anything. It basically slowed renders to a crawl and it shouldn't, I have a NVIDIA GeForce RTX 2080 Ti, my renders should fly like they used to. I noticed that I can't work on machine and run a render at the same time any more. The cursor stutters and slows I can't use any other programs.
Can anybody help me out here?
Do you by any chance have both CPU and the video card selected under Photoreal Mode and Interactive Mode in Render Settings - Advanced? If yes, try unselecting CPU.
Thanks @TheTreeInFront! Your info clarifies several key points of confusion people have had (pretty much from the start) about NVLink functionality and Daz Studio/Iray. Namely:
Some words on how SLI doesn't technically fit into all of this. SLI is neither the same thing as NVLink nor itself technically required for memory pooling in DS/Iray to function. SLI is the name of both a physical interconnect (found exclusively on 10xx series GPUs and earlier) and a parallel processing algorithm used to implement multi-GPU functionality on Nvidia graphics cards in supported games. NVLink is a physical interconnect that replaces the physical interconnect portion of SLI on Turing (and likely later) GPUs. And it supports many other types of data streams than just SLI since it uses a widely adopted internal Nvidia data protocol standard called GPUDirect.
GPUDirect must be enabled in order for memory pooling to function. However GPUDirect functionality is - by default - disabled in the default Nvidia Windows driver architecture (WDDM.) And GTX cards are only allowed to run Nvidia drivers using the default mode. However however - since SLI on Turing cards also requires that GPUDIrect be enabled to function (since Nvidia dropped its dedicated physical interconnect) Nvidia have made it so that enabling SLI on Turing GPUs also enables GPUDirect. And it turns out that enabling GPUDirect for one use automatically makes it availalable for all others. Hence why SLI needs to be enabled for memory pooling to function on Turing cards despite them having nothing directly to do with each other.
There are potential drawbacks to this. SLI requires that all subject cards be configured in a master-slave relationship where hardware performance between them is kept as balanced as possible. Meaning that SLI'ing a 2080Ti and a 2070 SUPER together would result in the 2080Ti being downclocked to the 2070 S's level. Meaning that your DS/Iray memory pooled rendering experience will also be affected (since you are just piggybacking off of the SLI configuration.) However, if you have two identical cards there should\n't be any noticeable difference.
Something you might find useful regarding tracking memory usage limits in your system. If you search your DS log file for "GiB available," you should find at least one line like the following for each of your Nvidia GPUs:
The "20.069 GiB available" is apparently the actual amount of video memory available to Iray during the current session. As you can see on my system (single Titan RTX also being used to drive a 4K monitor) it is almost a full 4 gigs lower than the GPU's physical maximum capacity. And this number seems to stay the same on my system regardless of what other apps are running besides Daz Studio. Presumably this is the persistent memory overhead required by Windows and the Daz Studio interface itself to function in tandem with Iray under the default driver model (switching the Nvidia driver to TCC mode - something only supported with Titan/Quadro cards - pops the available memory all the way up to card's full total.) You might wanna check and see what numbers it gives for your 2080Ti's.
Getting this error when I try to render. Daz will work for awhile, Iray preview mode still works. send this out to render and get the below. Only way to fix it is to shut down daz and restart. I have a Titan RTX, so it's definietly not a memory issue :-P I should also point out that even though I can't render out, I can still take advantage of iray preview :-P
2020-05-15 12:40:37.797 Rendering image
2020-05-15 12:40:56.987 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - API:DATABASE :: 1.0 API db warn : Transaction is released without being committed or aborted. Automatically aborting.
2020-05-15 12:44:17.053 Total Rendering Time: 3 minutes 39.33 seconds
GREAT, now the specular render settings are screwed up! I speculate that we will not see this being fixed any time soon as we still have the jumping selection bug... Here's hoping that I'm proven wrong; whelp, at least the General release is stable enough... And no, not using specular settings are not an option as I prefer a high degree of realism in my renders, ignoring the bug would defeat the purpose of even striving for a realistic renderer in the first place!
EDIT: I had the same issue with the general release version, it turned out that it was my PC's environment that screwed up the rendering engine as it righted itself upon re-starting!
Are you letting it render long enough? What are your render settings?
This is one of thoses parts because I have 3 copy for a single daz opening that all say the same thing except 1.0 IRAY instead of 1.1
2020-05-15 03:36:36.901 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : NVIDIA display driver version: 442.92
2020-05-15 03:36:36.915 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : Your NVIDIA driver supports CUDA version up to 10.2; iray requires CUDA version 10.2; all is good.
2020-05-15 03:36:36.919 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : Using iray plugin version 5.1, build 327300.3640 n, 30 Mar 2020, nt-x86-64-vc14.
2020-05-15 03:36:37.469 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): compute capability 7.5, 11.000 GiB total, 9.011 GiB available, display attached
2020-05-15 03:36:37.473 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.1 IRAY rend error: CUDA device 1 (GeForce RTX 2080 Ti): SLI is enabled, may render slowly or behave erratically (it is strongly recommended to disable SLI with iray if not using NVLINK)
2020-05-15 03:36:37.473 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : CUDA device 1 (GeForce RTX 2080 Ti): WDDM driver used, consider switching to TCC driver model if no display needed (via 'nvidia-smi -dm 1'), to increase rendering performance
2020-05-15 03:36:37.587 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): compute capability 7.5, 11.000 GiB total, 9.011 GiB available, display attached
2020-05-15 03:36:37.587 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.1 IRAY rend error: CUDA device 0 (GeForce RTX 2080 Ti): SLI is enabled, may render slowly or behave erratically (it is strongly recommended to disable SLI with iray if not using NVLINK)
2020-05-15 03:36:37.593 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): WDDM driver used, consider switching to TCC driver model if no display needed (via 'nvidia-smi -dm 1'), to increase rendering performance
I've tried to activate TCC without success and I don't have space for another regular card to offload the display anyway. For the reserved memory, it seem to be a ratio since you have twice the memory and twice the reserved amount compared to mine.
[edit]
Forgot to put the lines of the NVlink
2020-05-15 03:36:37.859 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Setting NVLINK peer group size to 2.
2020-05-15 03:36:37.871 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : NVLINK peer access enabled for 1 groups with 2 devices each
TCC is not an option for consumer cards, you need Quadros or - I think - a Titan.
Yes, as my scene setup remained unchanged with the previous version; however, that is a moot point as the general release had the same issue! I since re-started my PC and it righted itself, it may have been something with my PC environment that interfered with the render engine; possibly my GPU was glitching out or some such... I'll edit my original post!
make sure that both PCIe slots are running at the same speed.
if your motherboard/CPU only supports 16x/8x speed in a 2xGPU setup, set the 16x slot to 8x speed in the motherboard BIOS
I'm in the middle of getting a 2nd 2080TI and a 3slot NVLink bridge and will be testing the pooling too... soon™
Unfortunately, I now know that it was not my computer (Macbook Pro 2013) – but rather Daz 4.12.1+ incompatibility with Mac's Catalina OS that has caused serious problems working in the application for the past few months. As a result, one of my favorite applications will sadly get shelved going forward. And that's after 15 years (since May 2005) of working with Daz and buying tons and tons and tons of content on Daz3d.com.
How do I know it's not my computer? Just bought a new Macbook Pro to support all my 3D work in ZBrush, Maya, Blender, etc., - 64 Gigs of RAM, 2.4 Ghz 8-core Intel Core i9, and a pretty hefty graphics card. I did not transfer over Daz from my old computer. Just content. I did a 100% fresh install; but to my complete shock, after working in Daz for a little more than 3 hours tonight, I'm having identical problems I had on my 2013 machine (on Catalina), even after a completely fresh install. Both the Beta 4.12.2.6 and 4.12.1.117 exhibit the same behavior:
1-2 crashes per hour.
Extremely long lag times for loading content (e.g., one character).
Freqeunt lags in the process of merely manipualting a character.
When I save a file, two "Save" dialog boxes pop up overlapping each other (exactly what happened on my old computer) that both read "Filtered Save". I select one and save, and then about after 6 additional saves, Daz crashes.
When rendering, a dialog box pops up that says I am already rendering, which is false.
When I've been lucky enough to get past 30 minutes of working in Daz and I save an existing file, it treats it if it were a new file... "Untitled". So it's essentially "Save As" forever after that point. At times the old file I had been working on was never saved anyway.
From time to time, after rendering, Daz crashes. It also crashes after merely saving (or trying to save) the scene I'm working on.
NONE of this happened before 4.12.1.117. It's really sad because I have deadlines and Daz used be fantastic for certain parts of my workflow. I was really, really hoping this new computer would solve the problems, but it looks like I can't use Daz anymore, at least until these serious problems are solved. And that's after working with Daz for 15 years. Really, really, really disappointed.
Here's the current compatiblity matrix for Windows driver modes and all of Nvidia's current discrete GPU offerings:
Chances of Nvidia ever allowing TCC mode on GTX cards is extremely slim imo since it is pretty much the only remaining software feature left that differentiates hige-end GTX cards from their significantly more expensive lower-end Quadro counterparts.
Yeah, see above.
Did some quick tests on my machines (a Titan RTX based desktop and a GTX 1050 2GB based ultrabook) and this is what I found regarding the ratio between "total" and "available" memory (combined with your findings for the 2080Ti):
The ratios aren't identical, but I'll grant you that they are pretty close to each other. So you may be right about it being a (relatively) fixed percentage of the whole.
To my knowledge, all modern mainstream socket motherboards with 2 or more physical x16 PCI-E slots automatically biffurcate the 1st slot's lanes to it and the 2nd x16 slot any time the 2nd slot is occupied. Meaning that no BIOS changes are necessary unless you are trying to do something more complex than just adding a 2nd GPU.
Submit support tickets. These all sound like bugs that should be relatively easy to reproduce (and therefore fix) if documented properly. Something that most likely rarely happens given how few OS X Daz Studio users there seem to be these days.
I SO wish this hadn't sneaked its way into my DIM when I was downloading a load of other updates. I would never have installed it if I'd spotted it!
Load times seem to have at least doubled.
It's horribly unstable. Frequent crashes, usually just as I'm about to save my work.
It doesn't work properly with Manfridays Render Queue so I've lost countless hours of overnight render time.
I used to be able to have two, sometimes three versions open at the same time. One for rendering, and one or two for working on scenes etc. Bar the ocassional slowdown for a second or so, it was fine. Now? Forget it. The smallest tweak whilst rendering takes 5-10 seconds minimum. It's really REALLY slow, even with just one version running.
I submitted a ticket over a week ago. I have deadlines to try and meet so I'm not interested in months of bug tracing to try and fix things. I simply asked for a rollback as I was more than happy with the previous version. No reply yet.
All in all highly disappointing. I love Daz Studio, but if I can't get this sorted out very soon, I'm going to have to look into using a more stable platform.
The latest stable release of Daz Studio is exactly the same as the previous beta: 4.12.1.117. If you haven't installed it yet, go ahead and do so, and you should be able to continue as you were.
Betas, from any software provider, are never recommended for production work.
In DIM, click on the Downloads Filter button on the Downloads tab. Scroll down to Public and disable it. That way, the beta updates will not show up in DIM and you won't accidently update the version on your computer. When there is an update and you want to install it, go back to the filters and enable Public.
Also, it is a good idea to save a backup of each version. I actually change the download path and save the files to a unique archive folder when they are released and then change the download path back to my default. I can install any version at any time by pointing the download path, via the settings, to that particular archive folder. (I do that for both the betas and the releases.) If you don't like the version you just installed, it's very easy to roll back a version or two when you have the files on your computer.
Did you update both the General Release and the Public Beta? If not, you should still have the previous version installed.
Are you getting errors, such as Duplicate Formulae found?
Are you using ctrl/cmd S to save? Try using File>Save, or use the current Public Build.
The plug in may need updating in light of the regularising of multi-instancing.
I've never used a beta, or opted in for the beta program. I've always used the public version as I'm well aware that betas can be glitchy. The update simply appeared in my DIM ten days or so ago and I downloaded it without realising. It's 4.12.1.117. If they've moved me to the beta version without asking, well, I'm going to be even more annoyed.
I've never used the beta.
If it's labeled "Public Build" it's the beta. The General Release doesn't say "Public".
Then you are posting in the wrong forum thread.
No need to be "even more annoyed." I made the assumption you were referring to the beta because this is the beta thread.
My information about using DIM to download backups of each version is still relevant, however it won't help you with this issue.
I usually run the current beta along side the previous version release, so 4.12.x.x beta and 4.11.x.x release. I keep the program files for Daz Studio hidden and tick the Show Hidden option box on the Downloads Tab when I know a new version is available. I download and archive as I mentioned previously, usually without installing. Then I untick the Show Hidden option box. Sounds like that might be a good idea for you, as well.
I do hope that CS will help you get a copy of the previous release. Good luck.
This is rather confusing, if the beta and the public build are the same then what difference does it make, and what's the difference whether you have the public build or the beta build - if they are both the same then they will surely both have the same issues?
their beta increments a number of times from a given general release, then becomes the general release when they hit their deadline, or decide it's 'ready' by some internal measure. For a short period they overlap, and then the beta increments again, and the cycle repeats. During this overlap period, they are indeed the same. Some of us save both versions of the installers at these moments so we can back-install things later on when new changes impact our systems in unpleasent ways.
There was a beta->general release last week or so, so they may still be overlapping. I believe the beta has incremented already?, hasn't it? even to the 4.12.2.x (from 4.12.1.x) if cared ot look (in the topic).
Either way, many of us who break our systems with recent general releases have to follow/use the beta to get critical bug fixes, so it's really not surprising to find general release users here in the beta thread, desperate for fixes that were missed in the beta->general release decision process. You could even argue that the beta and general don't feel much different.
--ms