DAZ 4.22 [ERROR] Iray :: Internal rendering error.

strenif

I've got a RTX 4090 that has been working great for awhile.

Sometime after upgrading to 4.22, Iray stopped working.

Rendering a scene or starting IRay Preview just shows a blank screen.

I've opened a new scene, loaded a blank Gen8F character with a single spotlight to make sure it wasn't anything with my scene.

I've updated my drivers, rebooted, reinstalled DAZ, but have not had any luck getting IRay to work again.

I've gone over my settings in DAZ to make sure my video care is selected and CPU fallback is off.

My video card seems fine as I can play games like RDR2 without issues.

Any help on this would be appreciated.

 

 

2023-11-11 15:48:30.360 [WARNING] :: D:\DAZDevel\Hudson\HUDSON_HOME\jobs\NB_Studio_Trunk\workspace\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable

2023-11-11 15:48:30.360 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
2023-11-11 15:48:30.360 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
2023-11-11 15:48:30.360 [WARNING] :: D:\DAZDevel\Hudson\HUDSON_HOME\jobs\NB_Studio_Trunk\workspace\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
2023-11-11 15:48:30.360 [ERROR] Iray :: Internal rendering error.
2023-11-11 15:48:30.473 [INFO] :: Saved image: C:\Users\tibbi\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
2023-11-11 15:48:30.479 [INFO] :: Finished Rendering

 

Richard Haseltine

What is the version number of the driver you are using? Right-click on desktop, select nVidia Control Panel, the version number will be with the GPU name on the home page.

Richard Haseltine

Please don't make the same comment in multiple places - I have e,oved your other thread and the other posts, and will move this one to Daz Studio Discussion since that was where you first posted (and was most appropriate).

strenif

Sorry about that. Wasn't sure which forum it was suppose to go in.
version 4.6.0 NVIDIA 546.01

Richard Haseltine

That driver should be well within the new enough range. As a final test, can you render a simple primitive in an empty scene - Edit>Create New Primitive? How about if you add an environment Settings Node from the Create menu, then set Environment Mode to Sun/Sky or Scene Only (in case it's a corrupt Ruins.hdr environment map)?

strenif

No luck.

Richard Haseltine

What happens if you try to render that?

strenif

Ended up finding the issue.

If I load one of my characters that uses OOT hair it would break DAZ even if I started a new scene with just that plane in it. I'd have to close and restart DAZ to get it working again so long as I don't load any character with OOT hair.

Apparently this is an issue with OOT hair transmitted color and 4.22

Here's the work around till DAZ fixes the bug

https://www.youtube.com/watch?v=wHvY1BdD4yQ

 

Envixer

There are a few more hairs affected. Bloody annoying.

hellmasters

Funny. OOT updated most of hairs at the beginning of this year 2023 to fix the issue caused by OOT default shader. And I have no issue for most of my OOT hairs under 4.22. You sure you updated through DIM? Or else?

Richard Haseltine

hellmasters said:

Funny. OOT updated most of hairs at the beginning of this year 2023 to fix the issue caused by OOT default shader. And I have no issue for most of my OOT hairs under 4.22. You sure you updated through DIM? Or else?

Installation order matters, another content driectory might have an older copy of the file,  with Daz Connect (installing through daz Studio) it depends which copy of the file is grabbed.