Daz Studio Pro BETA - version 4.22.0.15! (UPDATED)

Daz Software · November 2022

Daz 3D is pleased to announce Daz Studio Pro BETA - version 4.22.0.15!

Highlights:

See the Highlights thread (and/or Change Log) for details.
See the NVIDIA Iray thread for additional information.

Frequently Asked Questions:

Previous Public Build (Beta) Threads:

...
- 4.22.0.15 (December 18, 2023)
- 4.22.0.14 (December 16, 2023)
- 4.22.0.12 (December 13, 2023)
- 4.22.0.10 (December 11, 2023)
- 4.22.0.9 (December 6, 2023)
- 4.22.0.7 (December 1, 2023)
- 4.22.0.1 (October 31, 2023)
- 4.21.1.108 (October 25, 2023)
- 4.21.1.104 (October 20, 2023)
- 4.21.1.80 (August 11, 2023)
- 4.21.1.48 (April 24, 2023)
- 4.21.1.45 (March 27, 2023)
- 4.21.1.41 (February 17, 2023)
- 4.21.1.29 (January 20, 2023)
- 4.21.1.26 (December 22, 2022)
- 4.21.1.13 (November 4, 2022)

4.21.0.5 (October 12, 2022)
- 4.20.1.91 (October 5, 2022)
- 4.20.1.88 (September 28, 2022)
- 4.20.1.78 (September 7, 2022)
- 4.20.1.58 (July 27, 2022)
- 4.20.1.43 (June 3, 2022)
- 4.20.1.38 (May 20, 2022)
- 4.20.1.34 (May 13, 2022)

General Release Threads:

4.22.0.1 (November 1, 2023)
4.21.0.5 (October 12, 2022)
4.20.0.17 (April 29, 2022)
- 4.20.0.2 (February 18, 2022)
4.16.0.3 (November 22, 2021)
- 4.15.0.30 (September 2, 2021)
- 4.15.0.2 (January 7, 2021)
4.14.0.10 (December 2, 2020)
- 4.14.0.8 (November 10, 2020)

Praxis · November 2022

So was 4.21.0.5 the last DS version to support Iray GPU rendering on Windows7?

i.e. This latest DS 4.21.1.13 does not:?

Seems that way from the following links, but am I missing something?

For Iray GPU rendering, DS 4.21.0.5 requires NVIDIA drivers 471.41 or later: https://www.daz3d.com/forums/discussion/comment/7755976/#Comment_7755976

Latest NVIDIA drivers version supporting Win7 is 473.81 (for e.g. RTX 20xx, 30xx): https://www.nvidia.com/Download/driverResults.aspx/191965/en-us/

For Iray GPU rendering, DS 4.21.1.13 requires NVIDIA drivers 516.93 or later: https://www.daz3d.com/forums/discussion/comment/7824761/#Comment_7824761

If this is in fact the case, then everyone using Iray on Windows 7 should get a heads-up to save a copy of their DS 4.21.0.5 DIM installer (see below) before downloading DS 4.21.1.13

DS 4.21.0.5 General Release: IM00013176-02_DAZStudio421Win64bit.zip FileSize = 509,586 KB
DS 4.21.0.5 Beta Release: IM00012000-02_DAZStudio421PublicBuildWin64bit.zip FileSize = 509,626 KB

namffuak · November 2022

It does look like the handwriting is on the wall. Probably should be spray-painted in big letters, but it's there.

I'm currently planning on upgrading my W7 free-standing 3D system to W10 pro over thanksgiving weekend - currently perfecting the geometric alignment of my waterfowl (I used to work with an Industrial Engineer who insisted on 'getting all his ducks in a row' - boy did I get tired of that phrase). I draw the line at W10; the cpu is not on the W11 approved list, the system as a whole is just short of 8 years old, and I see no point in changing anything for what I've heard of W11.

Praxis · November 2022

namffuak said:

It does look like the handwriting is on the wall. Probably should be spray-painted in big letters, but it's there.

I'm currently planning on upgrading my W7 free-standing 3D system to W10 pro over thanksgiving weekend - currently perfecting the geometric alignment of my waterfowl (I used to work with an Industrial Engineer who insisted on 'getting all his ducks in a row' - boy did I get tired of that phrase). I draw the line at W10; the cpu is not on the W11 approved list, the system as a whole is just short of 8 years old, and I see no point in changing anything for what I've heard of W11.

Thanks for the reply.

You said "free-standing system": Does W10 Pro allow stand-alone operation, i.e. never needing to be connected to the internet?

Richard Haseltine · November 2022

DIM does now have an option to back up installers, if desired http://docs.daz3d.com/doku.php/public/software/install_manager/change_log_1_4_0_94#1_4_0_86

VividImaginator · November 2022

I found critical render problems with this last beta (Daz Studio Pro BETA - version 4.21.1.13.)

I loaded a Genesis 3 female scene subset that I use to test new Beta releases; the subset has nothing special; it is just a custom G3 female with a skin builder skin wearing a modified mischief outfit.

The G3 subset renders like it is supposed to render, but the moment I add an OOT hairstyle the rendering goes crazy.

Here is the log:

"2022-11-05 14:15:34.457 [INFO] :: Finished asset load (merge): 0m 0.38s - /People/Genesis 8 Female/Hair/OOT Linda Ponytail Hair/MATS/Iray/Linda Ponytail Hair Base Color 09.duf
2022-11-05 14:15:34.663 [INFO] :: Unlocking viewport redraw...
2022-11-05 14:15:34.663 [INFO] :: Viewport redraw unlocked.
2022-11-05 14:15:36.884 [INFO] :: Rendering image

...

2022-11-05 14:15:37.209 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "Documents\DAZ 3D\Studio\My Library\SkinbuilderCreations\SaraBase01--Genesis3FemaleFull--Arms_1004.jpg", no selector, pixel type "Rgb", 4096x4096x1 pixels, 1 miplevel.
...

2022-11-05 14:15:37.542 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "Documents\Custom Daz\Runtime\Textures\outoftouch\!hair\OOTHairblending2\Linda\09OOTLindaHair.jpg", no selector, pixel type "Rgb", 4000x4000x1 pixels, 1 miplevel.

...
2022-11-05 14:15:37.959 Iray (Scene Update) : Updating LPE labels
2022-11-05 14:15:37.959 Iray (Scene Update) : Updating geometry
2022-11-05 14:15:37.959 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.
2022-11-05 14:15:37.959 Iray (Scene Update) : Retrieving geometry
2022-11-05 14:15:37.959 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.
2022-11-05 14:15:38.039 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Auto instancing compression ratio 1.00 (Full instancing compression ratio 1.00)
2022-11-05 14:15:38.041 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0
2022-11-05 14:15:38.114 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (1 triangle object with 2 M triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 2 M triangles, 0 fiber instances yielding 0 segments) took 0.073 s
2022-11-05 14:15:38.114 Iray (Scene Update) : Updating motion transform data
2022-11-05 14:15:38.114 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating motion transforms.
2022-11-05 14:15:38.116 Iray (Scene Update) : Updating section objects
2022-11-05 14:15:38.116 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating section objects.
2022-11-05 14:15:38.116 Iray (Scene Update) : Updating materials
2022-11-05 14:15:38.116 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.
2022-11-05 14:15:38.287 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : Material instance 'DS_Linda Ponytail Hair Genesis 8 Female__Front2_23e6_1694' uses MDL JIT compilation.
2022-11-05 14:15:38.290 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 143 textures, 1 lambdas (1 unique)
2022-11-05 14:15:38.293 Iray (Scene Update) : Updating volumes
2022-11-05 14:15:38.293 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating compiled code.
2022-11-05 14:15:38.293 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.
2022-11-05 14:15:38.293 Iray (Scene Update) : Updating environment
2022-11-05 14:15:38.293 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating lens data
2022-11-05 14:15:38.303 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating lights
2022-11-05 14:15:38.303 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating instance topology
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating flags
2022-11-05 14:15:38.303 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
2022-11-05 14:15:38.305 Iray (Scene Update) : Updating backplate
2022-11-05 14:15:38.305 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
2022-11-05 14:15:38.307 Iray (Scene Update) : Updating portals
2022-11-05 14:15:38.307 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
2022-11-05 14:15:38.307 Iray (Scene Update) : Updating decals
2022-11-05 14:15:38.307 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
2022-11-05 14:15:38.311 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
2022-11-05 14:15:38.313 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
2022-11-05 14:15:38.318 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
2022-11-05 14:15:38.318 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
2022-11-05 14:15:38.319 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
2022-11-05 14:15:38.321 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
2022-11-05 14:15:38.322 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
2022-11-05 14:15:38.322 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
2022-11-05 14:15:38.322 [ERROR] Iray :: Internal rendering error."

After that, it doesn't recognize my RTX 3090 GPU any more; it says no cuda device found or usable... I mean, the RTX 3090 is still listed in Daz but it says 0 cuda devices found or usable when trying to render.

I'm using NVIDIA 517.40 studio drivers.

Rolling back to the previous beta.

Praxis · November 2022

Richard Haseltine said:

DIM does now have an option to back up installers, if desired http://docs.daz3d.com/doku.php/public/software/install_manager/change_log_1_4_0_94#1_4_0_86

Thank you Richard.

I've been manually backing-up DS installers since 4.0.2.55, so it's second nature for me now - but I'm concerned for those who don't know how to do that, or how to find and edit the .INI file to activate the auto-backup option. I think that until auto-backup is the default behaviour, each Release thread such as this should include prominent step-by-step instructions for how to set up the .INI and/or manually back-up, and why it is important to do so.

namffuak · November 2022

Praxis said:

namffuak said:

It does look like the handwriting is on the wall. Probably should be spray-painted in big letters, but it's there.

I'm currently planning on upgrading my W7 free-standing 3D system to W10 pro over thanksgiving weekend - currently perfecting the geometric alignment of my waterfowl (I used to work with an Industrial Engineer who insisted on 'getting all his ducks in a row' - boy did I get tired of that phrase). I draw the line at W10; the cpu is not on the W11 approved list, the system as a whole is just short of 8 years old, and I see no point in changing anything for what I've heard of W11.

Thanks for the reply.

You said "free-standing system": Does W10 Pro allow stand-alone operation, i.e. never needing to be connected to the internet?

IIRC it really would like you to set up an MSN account, but it can be bypassed; I've an MSI laptop running W10 pro - it shipped with W10 home - and I did not connect to the internet until aafter I had 10 home configured and running. Then I tied into my wifi and did the upgrade to 10 pro. And then I shut off the auto update process and pointed Edge to a non-existent proxy server.

I have the free upgrade to W10 on a usb thumb drive and hope to do the upgrade from 7 pro without problems - but I'm running backups, including a system image and system recovery backup before I start.

Praxis · November 2022

namffuak said:

...
I have the free upgrade to W10 on a usb thumb drive and hope to do the upgrade from 7 pro without problems - but I'm running backups, including a system image and system recovery backup before I start.

Thanks for the info, and good luck with the upgrade.

I'm very interested in how it goes...

Imago · November 2022

The menus and Custom Actions doesn't save changes and additions, I have to use version 4.12 in order to add or save new menus and Custom Actions.

IceCrMn · November 2022

I'm getting a random CTD with this in the log just prior to the crash.

2022-11-06 06:05:17.538 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.17 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Kernel [4] (ShadowEvalFS      ) failed after 0.200s
2022-11-06 06:05:17.538 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.17 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)
2022-11-06 06:05:17.538 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.17 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Failed to launch renderer
2022-11-06 06:05:17.539 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Device failed while rendering
2022-11-06 06:05:17.539 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.16 IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3060) is no longer available for rendering.
2022-11-06 06:05:17.539 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): [Guidance sync] Failed slave device (remaining 1, done 0).
2022-11-06 06:05:17.539 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.16 IRAY   rend warn : Re-rendering iteration because of device failure
2022-11-06 06:05:17.539 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.539 Iray [INFO] - IRAY:RENDER ::   1.17 IRAY   rend info : CPU: Allocated 32.983 MiB for frame buffer
2022-11-06 06:05:17.539 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.539 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.540 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.540 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.540 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.540 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.540 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 06:05:17.540 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.16 IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)

So far I've not seen a pattern. So can't reproduce it reliably.

I'm running Studio Driver 517.40.

IceCrMn · November 2022

Ok, I think I've tracked it down.

It looks to be the OOT Zola hair.

https://www.daz3d.com/zola-hair-for-genesis-3-and-8-females

Just loading this hair in an empty scene then starting either the preview render or a normal render it causes the CTD every time.

---

Attached full log.

You should see a

* Studio start up

* load Zola hair

* enable Iray preview render

* CTD

This happens twice in this log.

---

I'll change the shaders and see if it's related to the special hair shader used in this product. I assume it is.

IceCrMn · November 2022

Changing the shader to Iray Uber Base fixed it for me.

Does anyone else have this hair to test it to make sure it's not just me or something on my system causing this?

---

attached log of shader swap and successful preview render to 500 iterations.

edit: Just tested with the release version (4.21.0.5) and it renders just fine no CTD. The special hair shader seems to not work with the new version of iray in the current beta.

mikmod · November 2022

I can report, that with this DS 4.21.1.13 beta, the crash linked to Kennedy's Sneakers asset seems to be gone, like in stable DS 4.20.0.17 - thanks! It affected some other assets as well, so I'm at testing now. :)
Using 522.30 Studio driver on RTX 3090 and Windows 10 21H2.

The one thing that doesn't work, is dForce, on this driver. Nvidia decided to use OpenCL 3.0 as default now, right? Is there a environment variable to set the driver to work in "old" OpenCL mode?

PDSmith · November 2022

Since grabbing the most recent Beta update (last night), I'm seeing the same error.

2022-11-06 07:22:49.350 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR]
 - IRAY:RENDER ::   1.8   IRAY   rend error: CUDA device 1 (NVIDIA GeForce RTX 2070): an illegal memory access was
 encountered (while launching CUDA renderer in <internal>:150)

2022-11-06 07:22:49.516 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.5 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)

I've swapped out the latest Nvidia studio driver as of this morning from the NVIDIA website, same repeated errors, then swapped out to the latest Game Driver, No change, same errors every time.

Studio/Iray has hit a wall in my opinion with this Beta, (I've even tried disableing my 2070 then the 3060 to see if I was having problems with one of my cards, due to a lightning storm last night since my PC was doing over night renders). No change, all is well for the cards... so I'll let the powers that be hash this out.

2022-11-06 07:22:49.521 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 07:22:49.521 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 1 (NVIDIA GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)

Richard Haseltine · November 2022

mikmod said:

I can report, that with this DS 4.21.1.13 beta, the crash linked to Kennedy's Sneakers asset seems to be gone, like in stable DS 4.20.0.17 - thanks! It affected some other assets as well, so I'm at testing now. :)

Perhaps related to the fix for #DS-2450 listed here http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_21_1_12

Using 522.30 Studio driver on RTX 3090 and Windows 10 21H2.

The one thing that doesn't work, is dForce, on this driver. Nvidia decided to use OpenCL 3.0 as default now, right? Is there a environment variable to set the driver to work in "old" OpenCL mode?

The latest drivers have so far had an issue with OpenCL that causes problems for dForce. unless this is meant to be fixed in the driver you are using (check its chnage log) you would need to roll back to the 517 build, if possible (this will not support 4090 cards, and may not support games or other software that you want to run)

Richard Haseltine · November 2022

PDSmith said:

Since grabbing the most recent Beta update (last night), I'm seeing the same error.
2022-11-06 07:22:49.350 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR]
 - IRAY:RENDER ::   1.8   IRAY   rend error: CUDA device 1 (NVIDIA GeForce RTX 2070): an illegal memory access was
 encountered (while launching CUDA renderer in <internal>:150)
2022-11-06 07:22:49.516 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.5 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)

I've swapped out the latest Nvidia studio driver as of this morning from the NVIDIA website, same repeated errors, then swapped out to the latest Game Driver, No change, same errors every time.

Studio/Iray has hit a wall in my opinion with this Beta, (I've even tried disableing my 2070 then the 3060 to see if I was having problems with one of my cards, due to a lightning storm last night since my PC was doing over night renders). No change, all is well for the cards... so I'll let the powers that be hash this out.

2022-11-06 07:22:49.521 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 07:22:49.521 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 1 (NVIDIA GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)

As above, as far as I know you need to be using 517.x or earlier for dForce to work - I am not sure if this also affects Iray to any degree, but we have seen issue reports that suggest it may.

Richard Haseltine · November 2022

VividImaginator said:

I found critical render problems with this last beta (Daz Studio Pro BETA - version 4.21.1.13.)

I loaded a Genesis 3 female scene subset that I use to test new Beta releases; the subset has nothing special; it is just a custom G3 female with a skin builder skin wearing a modified mischief outfit.

The G3 subset renders like it is supposed to render, but the moment I add an OOT hairstyle the rendering goes crazy.

There is a known issue with some OOT hairs, which is being investigated.

Here is the log:

"2022-11-05 14:15:34.457 [INFO] :: Finished asset load (merge): 0m 0.38s - /People/Genesis 8 Female/Hair/OOT Linda Ponytail Hair/MATS/Iray/Linda Ponytail Hair Base Color 09.duf
2022-11-05 14:15:34.663 [INFO] :: Unlocking viewport redraw...
2022-11-05 14:15:34.663 [INFO] :: Viewport redraw unlocked.
2022-11-05 14:15:36.884 [INFO] :: Rendering image

...

2022-11-05 14:15:37.209 Iray [INFO] - IMAGE:IO ::   1.0   IMAGE io   info : Loading image "Documents\DAZ 3D\Studio\My Library\SkinbuilderCreations\SaraBase01--Genesis3FemaleFull--Arms_1004.jpg", no selector, pixel type "Rgb", 4096x4096x1 pixels, 1 miplevel.
...

2022-11-05 14:15:37.542 Iray [INFO] - IMAGE:IO ::   1.0   IMAGE io   info : Loading image "Documents\Custom Daz\Runtime\Textures\outoftouch\!hair\OOTHairblending2\Linda\09OOTLindaHair.jpg", no selector, pixel type "Rgb", 4000x4000x1 pixels, 1 miplevel.

...
2022-11-05 14:15:37.959 Iray (Scene Update) : Updating LPE labels
2022-11-05 14:15:37.959 Iray (Scene Update) : Updating geometry
2022-11-05 14:15:37.959 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.
2022-11-05 14:15:37.959 Iray (Scene Update) : Retrieving geometry
2022-11-05 14:15:37.959 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.
2022-11-05 14:15:38.039 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Auto instancing compression ratio 1.00 (Full instancing compression ratio 1.00)
2022-11-05 14:15:38.041 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0
2022-11-05 14:15:38.114 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (1 triangle object with 2 M triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 2 M triangles, 0 fiber instances yielding 0 segments) took 0.073 s
2022-11-05 14:15:38.114 Iray (Scene Update) : Updating motion transform data
2022-11-05 14:15:38.114 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating motion transforms.
2022-11-05 14:15:38.116 Iray (Scene Update) : Updating section objects
2022-11-05 14:15:38.116 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating section objects.
2022-11-05 14:15:38.116 Iray (Scene Update) : Updating materials
2022-11-05 14:15:38.116 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.
2022-11-05 14:15:38.287 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : Material instance 'DS_Linda Ponytail Hair Genesis 8 Female__Front2_23e6_1694' uses MDL JIT compilation.
2022-11-05 14:15:38.290 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 143 textures, 1 lambdas (1 unique)
2022-11-05 14:15:38.293 Iray (Scene Update) : Updating volumes
2022-11-05 14:15:38.293 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating compiled code.
2022-11-05 14:15:38.293 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.
2022-11-05 14:15:38.293 Iray (Scene Update) : Updating environment
2022-11-05 14:15:38.293 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating lens data
2022-11-05 14:15:38.303 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating lights
2022-11-05 14:15:38.303 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating instance topology
2022-11-05 14:15:38.303 Iray (Scene Update) : Updating flags
2022-11-05 14:15:38.303 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
2022-11-05 14:15:38.305 Iray (Scene Update) : Updating backplate
2022-11-05 14:15:38.305 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
2022-11-05 14:15:38.307 Iray (Scene Update) : Updating portals
2022-11-05 14:15:38.307 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
2022-11-05 14:15:38.307 Iray (Scene Update) : Updating decals
2022-11-05 14:15:38.307 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
2022-11-05 14:15:38.311 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
2022-11-05 14:15:38.313 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
2022-11-05 14:15:38.318 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
2022-11-05 14:15:38.318 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
2022-11-05 14:15:38.319 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
2022-11-05 14:15:38.321 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
2022-11-05 14:15:38.322 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
2022-11-05 14:15:38.322 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
2022-11-05 14:15:38.322 [ERROR] Iray :: Internal rendering error."

After that, it doesn't recognize my RTX 3090 GPU any more; it says no cuda device found or usable... I mean, the RTX 3090 is still listed in Daz but it says 0 cuda devices found or usable when trying to render.

I'm using NVIDIA 517.40 studio drivers.

Did you try a clean install of the drivers? Sometimes bits get left over which can cause issues.

Rolling back to the previous beta.

Richard Haseltine · November 2022

IceCrMn said:

Ok, I think I've tracked it down.

It looks to be the OOT Zola hair.

https://www.daz3d.com/zola-hair-for-genesis-3-and-8-females

Just loading this hair in an empty scene then starting either the preview render or a normal render it causes the CTD every time.

---

Attached full log.

You should see a

* Studio start up

* load Zola hair

* enable Iray preview render

* CTD

This happens twice in this log.

---

I'll change the shaders and see if it's related to the special hair shader used in this product. I assume it is.

This is apaprently an issue that is being investigated.

PDSmith · November 2022

Richard Haseltine said:
PDSmith said:

Since grabbing the most recent Beta update (last night), I'm seeing the same error.
2022-11-06 07:22:49.350 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR]
 - IRAY:RENDER ::   1.8   IRAY   rend error: CUDA device 1 (NVIDIA GeForce RTX 2070): an illegal memory access was
 encountered (while launching CUDA renderer in <internal>:150)
2022-11-06 07:22:49.516 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.5 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)

I've swapped out the latest Nvidia studio driver as of this morning from the NVIDIA website, same repeated errors, then swapped out to the latest Game Driver, No change, same errors every time.

Studio/Iray has hit a wall in my opinion with this Beta, (I've even tried disableing my 2070 then the 3060 to see if I was having problems with one of my cards, due to a lightning storm last night since my PC was doing over night renders). No change, all is well for the cards... so I'll let the powers that be hash this out.

2022-11-06 07:22:49.521 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)
2022-11-06 07:22:49.521 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 1 (NVIDIA GeForce RTX 2070): an illegal memory access was encountered (while de-allocating memory)
As above, as far as I know you need to be using 517.x or earlier for dForce to work - I am not sure if this also affects Iray to any degree, but we have seen issue reports that suggest it may.

I'm not using deforce in the scene that I'm aware of, I'm one of those people who still actively uses G2 and V4/M4 due to they footprint on memory, load times, render times and clearing of memory. In this case I loaded a premade scene that the previous Beta had no propblems with, did some changes to poses, clicked render and it errored out big time.

So with all this, are you saying I should roll back my drivers because Iray / dForce / Studio are in conflict?

late add on- Thank god nvidia is one of those companies that allows it's customers to download older versions of their product.

Richard Haseltine · November 2022

Imago said:

The menus and Custom Actions doesn't save changes and additions, I have to use version 4.12 in order to add or save new menus and Custom Actions.

In general saving changes seems to be working. Are you allowing DS to close or force-quitting? It may also be worth checking that some kind of system or security tool isn't blocking the files from updating.

marble · November 2022

I have 4.21.0.5 with NVidia Studio Driver 517.40. If I install this latest beta (4.21.1.13) will I need to update my NVidia drivers and will that break dForce?

I am interested to know what has changed with L.I.E. but I haven't found a full description. I've seen comments that it is faster (I have always avoided using it because of how slow it is) but is it faster? And what else has changed? Do I need 4.21.1.13 to see these changes?

PDSmith · November 2022

marble said:

I have 4.21.0.5 with NVidia Studio Driver 517.40. If I install this latest beta (4.21.1.13) will I need to update my NVidia drivers and will that break dForce?

I am interested to know what has changed with L.I.E. but I haven't found a full description. I've seen comments that it is faster (I have always avoided using it because of how slow it is) but is it faster? And what else has changed? Do I need 4.21.1.13 to see these changes?

I rolled back my Nvidia Studio driver to 517.40 and attempted to use 4.21.1.13 Beta. It's a no marriage for me, guess I'll wait for the next round of Beta to come out and see what's new then.

Richard Haseltine · November 2022

marble said:

I have 4.21.0.5 with NVidia Studio Driver 517.40. If I install this latest beta (4.21.1.13) will I need to update my NVidia drivers and will that break dForce?

I am interested to know what has changed with L.I.E. but I haven't found a full description. I've seen comments that it is faster (I have always avoided using it because of how slow it is) but is it faster? And what else has changed? Do I need 4.21.1.13 to see these changes?

The driver you have will be fine.

LIE can be faster if you adjust its settings so that it doesn't compress the final composite textures as much - by default it is just the same as before. It has also gained a lot of new blend modes, allowing for more effects from layering (e.g. using a map to create tan lines by lightening the texture, through screen mode (though it isn't called that) rather than just by darkening the rest of the skin using multiply) and the UI has also been tweaked to make it more convenient.

VividImaginator · November 2022

Richard Haseltine said:

There is a known issue with some OOT hairs, which is being investigated.

Did you try a clean install of the drivers? Sometimes bits get left over which can cause issues.

I did a clean install just to test if that was the problem and no; the problem persists after doing a clean GPU driver install.

The "OOT Linda Ponytail Hair" bug was introduced with the last beta; I know for a fact because I use that hairstyle very often. Linda Ponytail is a hairstyle I use for one of my main characters and I used it almost every day during October.

If there was issues with OOT hairstyles before this beta then OOT Linda Ponytail it is a new one for the list.

So I will be using the beta 4.21.0.5 for a while.

marble · November 2022

Richard Haseltine said:

marble said:

I have 4.21.0.5 with NVidia Studio Driver 517.40. If I install this latest beta (4.21.1.13) will I need to update my NVidia drivers and will that break dForce?

I am interested to know what has changed with L.I.E. but I haven't found a full description. I've seen comments that it is faster (I have always avoided using it because of how slow it is) but is it faster? And what else has changed? Do I need 4.21.1.13 to see these changes?

The driver you have will be fine.

LIE can be faster if you adjust its settings so that it doesn't compress the final composite textures as much - by default it is just the same as before. It has also gained a lot of new blend modes, allowing for more effects from layering (e.g. using a map to create tan lines by lightening the texture, through screen mode (though it isn't called that) rather than just by darkening the rest of the skin using multiply) and the UI has also been tweaked to make it more convenient.

Thanks Richard. Are the new features documented anywhere? A mini tutorial would be nice. As I said, I have tended to avoid LIE because it was not only slow to work with but the results were also slow to load.

RobotHeadArt · November 2022

So I see in Shader Mixer an Emission Intensity channel for making emissive volumes on the Uber Add Inhomogeneous Volume brick in the Simple OpenVDB MDL Volume shader. What do I plug in to this to enable emissive volumes? It looks like it wants a color but that doesn't make sense. Is the brick for converting a VDB file to the blackbody emission not yet implemented? Edit: Just tried to set the Emissive Intensity to red and crash to desktop in Iray Interactive mode.

Imago · November 2022

Richard Haseltine said:

In general saving changes seems to be working. Are you allowing DS to close or force-quitting? It may also be worth checking that some kind of system or security tool isn't blocking the files from updating.

No, normal quitting and waiting for the session to fully close. Nothing is blocking it at all. As I said, DAZ Studio 4.12.0.86 saves everything correctly.

JB007 · November 2022

Is the 4090 fully supported in this beta with a new Iray / Cuda?

Richard Haseltine · November 2022

marble said:

Richard Haseltine said:

marble said:

I have 4.21.0.5 with NVidia Studio Driver 517.40. If I install this latest beta (4.21.1.13) will I need to update my NVidia drivers and will that break dForce?

I am interested to know what has changed with L.I.E. but I haven't found a full description. I've seen comments that it is faster (I have always avoided using it because of how slow it is) but is it faster? And what else has changed? Do I need 4.21.1.13 to see these changes?

The driver you have will be fine.

LIE can be faster if you adjust its settings so that it doesn't compress the final composite textures as much - by default it is just the same as before. It has also gained a lot of new blend modes, allowing for more effects from layering (e.g. using a map to create tan lines by lightening the texture, through screen mode (though it isn't called that) rather than just by darkening the rest of the skin using multiply) and the UI has also been tweaked to make it more convenient.

Thanks Richard. Are the new features documented anywhere? A mini tutorial would be nice. As I said, I have tended to avoid LIE because it was not only slow to work with but the results were also slow to load.

This covers the blend modes https://doc.qt.io/archives/qt-4.8/qpainter.html#CompositionMode-enum

bobrodobrobobrodobro · November 2022

Why mty librarry looks like this?

Notifications

Daz Studio Pro BETA - version 4.22.0.15! (UPDATED)

Daz 3D is pleased to announce Daz Studio Pro BETA - version 4.22.0.15!

Highlights:

Frequently Asked Questions:

Previous Public Build (Beta) Threads:

General Release Threads:

Comments

Adding to Cart…

Notifications

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

Daz 3D is pleased to announce Daz Studio Pro BETA - version 4.22.0.15!

Highlights:

Frequently Asked Questions:

Previous Public Build (Beta) Threads:

General Release Threads:

Comments

Adding to Cart…

Daz Studio Pro BETA - version 4.22.0.15! (UPDATED)