Personal observation: this version is significantly better on the vram usage and release of used memory than the previous (at least so far)
as for the environment and tone map settings, you can add them without switching to iray preview or starting a render by going create> new environment settings node etc
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
Further question: if my existing video card will still work for dForce simulations, do I need any particular driver version for it to continue to work? (I keep the driver moderately up-to-date but usually avoid the absolute latest until I've heard about any problems, through the forums)
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
Further question: if my existing video card will still work for dForce simulations, do I need any particular driver version for it to continue to work? (I keep the driver moderately up-to-date but usually avoid the absolute latest until I've heard about any problems, through the forums)
The latest Nvidia drivers no longer support Kepler GPUs. The GTX7x0 cards using Maxwell architecture are the oldest cards still supported by current drivers. I would hold off on updating DS if you want to continue using your card for dForce.
On the bright side, now seems to be a pretty good time to find second-hand graphics card bargains.
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
Correct, as the minimum driver requirement doesn't support Kepler.
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
dForce isn't reliant on the NVIDIA driver as such, but utilizes OpenCL 1.2 to perform simulations. See the 2nd section in this post.
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
dForce uses openCL, not CUDA, so I don't see why it would stop working for dForce even if Iray can't use it anymore.
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
Correct, as the minimum driver requirement doesn't support Kepler.
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
dForce isn't reliant on the NVIDIA driver as such, but utilizes OpenCL 1.2 to perform simulations. See the 2nd section in this post.
Thank you - I'll save my currrent version installers and give the new one a try - in the worst case I should be able to reinstall my older Beta.
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
Further question: if my existing video card will still work for dForce simulations, do I need any particular driver version for it to continue to work? (I keep the driver moderately up-to-date but usually avoid the absolute latest until I've heard about any problems, through the forums)
The latest Nvidia drivers no longer support Kepler GPUs. The GTX7x0 cards using Maxwell architecture are the oldest cards still supported by current drivers. I would hold off on updating DS if you want to continue using your card for dForce.
On the bright side, now seems to be a pretty good time to find second-hand graphics card bargains.
Thanks - I'd love a better card but I'm so techno-ignorant I don't know whether my existing PC will take one. I'll have to investigate what will fit (or more importantly what won't) and maybe try the local PC-fix-shop to see what they can do.
Where on earth did Tone Mapping and Environment settings go? They're gone from the Render Settings Tab.
Either start a render or use the Iray Viewport Drawstyle for a sec, Tone Mapping and Environments will appear as as well as nodes in the Scene pane.
Is there any particular reason for this change? Sounds a bit weird to me. Could it be to avoid the confusion I've seen some people having with figuring out how to use the Preferences>Scene>Render Settings tickboxes?
Where on earth did Tone Mapping and Environment settings go? They're gone from the Render Settings Tab.
Either start a render or use the Iray Viewport Drawstyle for a sec, Tone Mapping and Environments will appear as as well as nodes in the Scene pane.
Is there any particular reason for this change? Sounds a bit weird to me. Could it be to avoid the confusion I've seen some people having with figuring out how to use the Preferences>Scene>Render Settings tickboxes?
One can also use the Create option on the Menu bar to create the Environment\Tonemapper nodes.
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
Correct, as the minimum driver requirement doesn't support Kepler.
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
dForce isn't reliant on the NVIDIA driver as such, but utilizes OpenCL 1.2 to perform simulations. See the 2nd section in this post.
Thank you - I'll save my currrent version installers and give the new one a try - in the worst case I should be able to reinstall my older Beta.
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
Further question: if my existing video card will still work for dForce simulations, do I need any particular driver version for it to continue to work? (I keep the driver moderately up-to-date but usually avoid the absolute latest until I've heard about any problems, through the forums)
The latest Nvidia drivers no longer support Kepler GPUs. The GTX7x0 cards using Maxwell architecture are the oldest cards still supported by current drivers. I would hold off on updating DS if you want to continue using your card for dForce.
On the bright side, now seems to be a pretty good time to find second-hand graphics card bargains.
Thanks - I'd love a better card but I'm so techno-ignorant I don't know whether my existing PC will take one. I'll have to investigate what will fit (or more importantly what won't) and maybe try the local PC-fix-shop to see what they can do.
That local shop would be a good place to look for a used video card. Sometimes they resell cards they replace when their customers upgrade.
2020-10-14 15:39:16.225 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 528 textures, 89 lambdas (63 unique)2020-10-14 15:39:16.253 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Computing 1 flux compensation factor took 0.001s2020-10-14 15:39:16.253 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 0.001s2020-10-14 15:39:16.253 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.2020-10-14 15:39:16.269 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.2020-10-14 15:39:16.271 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.2020-10-14 15:39:16.271 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.2020-10-14 15:39:16.271 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.2020-10-14 15:39:16.272 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.2020-10-14 15:39:16.272 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.2020-10-14 15:39:16.289 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using iray core convergence estimate.2020-10-14 15:39:16.290 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer2020-10-14 15:39:16.303 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled2020-10-14 15:39:16.303 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.2020-10-14 15:39:16.306 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using OptiX version 7.1.02020-10-14 15:39:16.317 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing OptiX for CUDA device 02020-10-14 15:39:16.647 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):2020-10-14 15:39:16.647 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2070)2020-10-14 15:39:16.647 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...2020-10-14 15:39:16.647 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend progr: CUDA device 0 (GeForce RTX 2070): Processing scene...2020-10-14 15:39:16.788 Iray [VERBOSE] - IRAY:RENDER :: 1.3 IRAY rend stat : Geometry memory consumption: 350.914 MiB (device 0), 0.000 B (host)2020-10-14 15:39:47.288 Iray [VERBOSE] - IRAY:RENDER :: 1.3 IRAY rend stat : Texture memory consumption: 2.215 GiB for 140 bitmaps (device 0)2020-10-14 15:39:47.289 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Importing lights for motion time 02020-10-14 15:39:47.289 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Initializing light hierarchy.2020-10-14 15:39:47.298 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Light hierarchy initialization took 0.002s2020-10-14 15:39:47.299 Iray [VERBOSE] - IRAY:RENDER :: 1.3 IRAY rend stat : Lights memory consumption: 948.000 B (device 0)2020-10-14 15:39:47.305 Iray [VERBOSE] - IRAY:RENDER :: 1.3 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)2020-10-14 15:39:48.053 Iray [VERBOSE] - IRAY:RENDER :: 1.3 IRAY rend stat : PTX code (435.524 KiB) for SM 7.5 generated in 0.748s2020-10-14 15:39:48.059 Iray [VERBOSE] - IRAY:RENDER :: 1.3 IRAY rend stat : Materials memory consumption: 465.090 KiB (GPU)2020-10-14 15:39:48.206 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : JIT-linking wavefront kernel in 0.040s2020-10-14 15:39:48.208 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : CUDA device 0 (GeForce RTX 2070): Scene processed in 31.553s2020-10-14 15:39:48.222 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : CUDA device 0 (GeForce RTX 2070): Allocated 47.461 MiB for frame buffer2020-10-14 15:39:48.278 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : CUDA device 0 (GeForce RTX 2070): Allocated 1.688 GiB of work space (2048k active samples in 0.050s)2020-10-14 15:39:48.841 Iray [INFO] - IRAY:RENDER :: 1.4 IRAY rend info : Allocating 1-layer frame buffer2020-10-14 15:39:48.907 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 32.259s.2020-10-14 15:39:49.454 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00002 iterations after 32.807s.2020-10-14 15:39:49.972 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00003 iterations after 33.325s.2020-10-14 15:39:50.508 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00004 iterations after 33.861s.2020-10-14 15:39:50.928 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.12 IRAY rend error: CUDA device 0 (GeForce RTX 2070): Tail kernel failed after 0.007s2020-10-14 15:39:50.928 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.12 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while launching CUDA renderer in <internal>:705)2020-10-14 15:39:50.935 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.12 IRAY rend error: CUDA device 0 (GeForce RTX 2070): Failed to launch renderer2020-10-14 15:39:50.935 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): Device failed while rendering2020-10-14 15:39:50.935 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER :: 1.4 IRAY rend warn : All available GPUs failed.2020-10-14 15:39:50.941 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: Fallback to CPU not allowed.2020-10-14 15:39:50.941 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while initializing memory buffer)2020-10-14 15:39:50.941 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: All workers failed: aborting render2020-10-14 15:39:50.947 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.947 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.953 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.953 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.959 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.959 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.964 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.965 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.970 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.970 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:50.976 Iray Render error: Internal rendering error.2020-10-14 15:39:51.323 Saved image: C:\Users\ZZZ\AppData\Roaming\DAZ 3D\Studio4 Public Build\temp\render\r.png2020-10-14 15:39:51.331 Finished Rendering2020-10-14 15:39:51.380 Total Rendering Time: 1 minutes 5.84 seconds2020-10-14 15:39:55.806 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Device statistics:2020-10-14 15:39:55.806 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2070): 4 iterations, 31.981s init, 2.688s render2020-10-14 15:39:55.813 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:55.813 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:55.819 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:55.819 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:55.825 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)2020-10-14 15:39:56.071 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.077 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.077 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.077 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.083 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.083 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.083 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.089 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.089 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.089 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.095 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.095 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.096 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.101 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.101 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.101 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.107 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.107 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.107 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.112 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.113 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.113 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.118 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.118 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.118 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.124 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.124 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.124 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.129 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.130 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.130 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.135 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.135 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-10-14 15:39:56.135 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.141 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-10-14 15:39:56.141 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
Yes, I have the same, tried Nvidia new drivers 456.71. and older ones 456.55. Seems new beta has some issues with Iray render.
If it can help you and thanks to other users, I could fix the problem and it was not drivers but was skin material related on my side.
I precise I could render just fine as long as the scene didn't have any Iray section plane (that's what make it weird lol). And I have zero problem with others Daz builds and that skin material.
If it's the same problem, try to test with the g8f dev model and an Iray section plane, and see if Iray crash again.
Ok so I just installed this 4.12.2.51 Beta and am a little confused about the Render settings debate. I gathered (or likely mis-gathered) from the discussions above that the Tone Mapping and Environment Panes had been removed in favour of the new nodes within the scene but, from what I can see, I have both. I rendered a scene from pre-update and I can still see the two panes in my Render Settings tab and I can also see the two nodes with associated parameters in the Parameters tab. Is this what would be expected?
Next question is regarding Filament. I can see how to use Filament in the viewport but not how to use it as a render engine. If I go to the Render Settings tab and click on "Engine" I am offered the same old choices with no Filament option.
Also with regard to filament, the lighting does not equate to the IRay lighting. If I use the settings that look ok in the IRay render, the Filament scene is too bright and washed out by excess light.
Next question is regarding Filament. I can see how to use Filament in the viewport but not how to use it as a render engine. If I go to the Render Settings tab and click on "Engine" I am offered the same old choices with no Filament option.
Also with regard to filament, the lighting does not equate to the IRay lighting. If I use the settings that look ok in the IRay render, the Filament scene is too bright and washed out by excess light.
If you're using scene lights, you can go to the Filament draw settings (found in the Create menu) and change scene light scale.
Incidentally, if you look in the Filament thread in the Commons, I posted a couple renders showing the opposite problem: a Filament screenshot where the character was in darkness, lit only by a dim spotlight, where the Iray render was drowning in light.
Comments
Personal observation: this version is significantly better on the vram usage and release of used memory than the previous (at least so far)
as for the environment and tone map settings, you can add them without switching to iray preview or starting a render by going create> new environment settings node etc
There were changes to SSIM, so you'll probably need to redo those settings.
Can someone confirm ?
Any use of Iray section plane node now crash Iray
Could you please provide more detail, e.g. when does the crash occur, etc?
Not sure if there much to add to be honest
1. load any scene/model
2. put an iray section plane
3. Hit Iray preview or render with Iray
4. Crash Iray after few iterations
It works just fine for me, whether it is Iray Preview or Iray render. Are your drivers up to date?
Yeah lastest 456.71.
You are on the new public build too 4.12.2.51?
Well from your initial post it wasn't clear if the crash happened when adding the plane or when rendering, for example.
Yep. Just tried it too. No problems or crashes with either preview or final render. That's with RTX2080ti and GTX 1080ti using driver 452.06
TD
Same build and driver versions.
Thanks.
I guess that's from me then.
Very weird tho
.
See the chnage log for 4.12.2.41 http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_12_2_41 for more information
SSIM was not, until now, a stop condition - it gave feedback but the render had to be stopped manually. The settings have chnaged, and may need adjsutment - see http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_12_2_50
Can you please help this "techno-know-very-little" with a basic question:
I have a very old video card (GTX 660) which I believe is Kepler architecture - am I correct in my understanding that I cannot use the latest DS 4.12.2.51 Beta for Iray rendering with that video card?
I currently do all my Iray renders with CPU (because my GPU is too "small" for almost any scene) but rely on that card to do dForce simulations. Can I still do this with DS 4.12.2.51, or is it in some way incompatible for all purposes?
Yes, I have the same, tried Nvidia new drivers 456.71. and older ones 456.55. Seems new beta has some issues with Iray render.
Further question: if my existing video card will still work for dForce simulations, do I need any particular driver version for it to continue to work? (I keep the driver moderately up-to-date but usually avoid the absolute latest until I've heard about any problems, through the forums)
Can also confirm that 456.38 and 456.71 breaks iray for me, but 451.48 works fine. Anything lower and DAZ will complain.
The latest Nvidia drivers no longer support Kepler GPUs. The GTX7x0 cards using Maxwell architecture are the oldest cards still supported by current drivers. I would hold off on updating DS if you want to continue using your card for dForce.
On the bright side, now seems to be a pretty good time to find second-hand graphics card bargains.
Correct, as the minimum driver requirement doesn't support Kepler.
dForce isn't reliant on the NVIDIA driver as such, but utilizes OpenCL 1.2 to perform simulations. See the 2nd section in this post.
dForce uses openCL, not CUDA, so I don't see why it would stop working for dForce even if Iray can't use it anymore.
RTX 3090 owner here, Studio driver 456.38. Iray works for me just fine.
Thank you - I'll save my currrent version installers and give the new one a try - in the worst case I should be able to reinstall my older Beta.
Thanks - I'd love a better card but I'm so techno-ignorant I don't know whether my existing PC will take one. I'll have to investigate what will fit (or more importantly what won't) and maybe try the local PC-fix-shop to see what they can do.
Is there any particular reason for this change? Sounds a bit weird to me. Could it be to avoid the confusion I've seen some people having with figuring out how to use the Preferences>Scene>Render Settings tickboxes?
You can also generate those scene nodes from the Create menu now.
One can also use the Create option on the Menu bar to create the Environment\Tonemapper nodes.
That local shop would be a good place to look for a used video card. Sometimes they resell cards they replace when their customers upgrade.
If it can help you and thanks to other users, I could fix the problem and it was not drivers but was skin material related on my side.
I precise I could render just fine as long as the scene didn't have any Iray section plane (that's what make it weird lol). And I have zero problem with others Daz builds and that skin material.
If it's the same problem, try to test with the g8f dev model and an Iray section plane, and see if Iray crash again.
Ok so I just installed this 4.12.2.51 Beta and am a little confused about the Render settings debate. I gathered (or likely mis-gathered) from the discussions above that the Tone Mapping and Environment Panes had been removed in favour of the new nodes within the scene but, from what I can see, I have both. I rendered a scene from pre-update and I can still see the two panes in my Render Settings tab and I can also see the two nodes with associated parameters in the Parameters tab. Is this what would be expected?
Next question is regarding Filament. I can see how to use Filament in the viewport but not how to use it as a render engine. If I go to the Render Settings tab and click on "Engine" I am offered the same old choices with no Filament option.
Also with regard to filament, the lighting does not equate to the IRay lighting. If I use the settings that look ok in the IRay render, the Filament scene is too bright and washed out by excess light.
If you're using scene lights, you can go to the Filament draw settings (found in the Create menu) and change scene light scale.
Incidentally, if you look in the Filament thread in the Commons, I posted a couple renders showing the opposite problem: a Filament screenshot where the character was in darkness, lit only by a dim spotlight, where the Iray render was drowning in light.