IRay fail to render 95% of time now (Solved)
windli3356
Posts: 230
EDIT: this is the Iray blackscreen issue that never had an offical solution since 2016, I found many related threads date back to 2016, and there's yet a solution to this problem.
So all of sudden, Iray is nearly unusable in recent build. most of time my PC fail to start iteration and rendering will be done in 3 secs with a black screen. Tried both game ready driver and studio driver, still encounter the same problem, so I doubt it's the driver issue.
Please see log in attached
My spec i7 - 5820k 16G ram, RTX2060
irayFail.png
400 x 521 - 23K
Post edited by windli3356 on
Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
What does the log say?
Start rendering -> finished rendering nothing in between, sometimes you got little more info.
These day Daz is quickly became a dumpster where I spend 99% trouble shooting and less than 1% time doing the work. Always 1 issue after another.
This is not the log. This is the render dialog, which contains little information.
To get the log, go to Help>Troubleshooting>View Log File...
k, my bad, here it is.
really never encountered so many issue with rendering engine with any other 3D tools I used.
2020-07-25 09:40:43.082 GL_NV_viewport_array2 : NOT INITIALIZED
2020-07-25 09:40:43.082 GL_NV_viewport_swizzle : NOT INITIALIZED
2020-07-25 09:40:43.082 GL_NVX_conditional_render : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NVX_linked_gpu_multicast : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NV_gpu_multicast : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NVX_gpu_multicast2 : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NVX_progress_fence : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NVX_gpu_memory_info
2020-07-25 09:40:43.083 GL_NVX_multigpu_info : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NVX_nvenc_interop : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NV_shader_thread_group : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_NV_shader_thread_shuffle : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_KHR_blend_equation_advanced : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_KHR_blend_equation_advanced_coherent : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_OVR_multiview : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_OVR_multiview2 : NOT INITIALIZED
2020-07-25 09:40:43.083 GL_SGIS_generate_mipmap
2020-07-25 09:40:43.083 GL_SGIS_texture_lod
2020-07-25 09:40:43.083 GL_SGIX_depth_texture
2020-07-25 09:40:43.083 GL_SGIX_shadow
2020-07-25 09:40:43.083 GL_SUN_slice_accum
2020-07-25 09:40:43.083 GL_WIN_swap_hint
2020-07-25 09:40:43.083 WGL_EXT_swap_control : NOT INITIALIZED
2020-07-25 09:40:43.083
2020-07-25 09:40:43.083 WGL_ARB_buffer_region
2020-07-25 09:40:43.083 WGL_ARB_create_context
2020-07-25 09:40:43.083 WGL_ARB_create_context_no_error
2020-07-25 09:40:43.083 WGL_ARB_create_context_profile
2020-07-25 09:40:43.083 WGL_ARB_create_context_robustness
2020-07-25 09:40:43.083 WGL_ARB_context_flush_control
2020-07-25 09:40:43.083 WGL_ARB_extensions_string
2020-07-25 09:40:43.083 WGL_ARB_make_current_read
2020-07-25 09:40:43.084 WGL_ARB_multisample
2020-07-25 09:40:43.084 WGL_ARB_pbuffer
2020-07-25 09:40:43.084 WGL_ARB_pixel_format
2020-07-25 09:40:43.084 WGL_ARB_pixel_format_float
2020-07-25 09:40:43.084 WGL_ARB_render_texture
2020-07-25 09:40:43.084 WGL_ATI_pixel_format_float
2020-07-25 09:40:43.084 WGL_EXT_colorspace
2020-07-25 09:40:43.084 WGL_EXT_create_context_es_profile
2020-07-25 09:40:43.084 WGL_EXT_create_context_es2_profile
2020-07-25 09:40:43.084 WGL_EXT_extensions_string
2020-07-25 09:40:43.084 WGL_EXT_framebuffer_sRGB
2020-07-25 09:40:43.084 WGL_EXT_pixel_format_packed_float
2020-07-25 09:40:43.084 WGL_EXT_swap_control
2020-07-25 09:40:43.084 WGL_EXT_swap_control_tear
2020-07-25 09:40:43.084 WGL_NVX_DX_interop
2020-07-25 09:40:43.084 WGL_NV_DX_interop
2020-07-25 09:40:43.084 WGL_NV_DX_interop2
2020-07-25 09:40:43.084 WGL_NV_copy_image
2020-07-25 09:40:43.084 WGL_NV_delay_before_swap
2020-07-25 09:40:43.084 WGL_NV_float_buffer
2020-07-25 09:40:43.084 WGL_NV_multisample_coverage
2020-07-25 09:40:43.084 WGL_NV_multigpu_context
2020-07-25 09:40:43.084 WGL_NV_render_depth_texture
2020-07-25 09:40:43.084 WGL_NV_render_texture_rectangle
2020-07-25 09:40:43.084 : NOT INITIALIZED
2020-07-25 09:40:43.084 OpenGL features for current hardware:
2020-07-25 09:40:43.084 OpenGL provider: NVIDIA Corporation
2020-07-25 09:40:43.085 OpenGL renderer: GeForce RTX 2060/PCIe/SSE2
2020-07-25 09:40:43.085 OpenGL version: 4.6.0
Update driver. User error.
Started seeing this issue with latest game ready Driver 451.67, fail to work, then update to studio driver 451.77, same error. then rolled back to current 451.48, same error still. Very unlikely driver issue.
I didn't say the only user error was that the driver was out of date just that it was most likely.
If you want to engage and be useful I'll help but if all you want tod is sling accusations, user error because that is clearly where the problem lies.
Sorry, I don't know where you got the impression I was slinging accusation, I was simply providing all avilable information on hand trying to get a solution from the community. I didn't even elmilate the user error's possiblity, if someone can indicate where it is and help me resolve this, I'd be appreciated.
note: I saw this infamous blackscreen/blankscreen iray failure reported by many other users since 2016, but there's yet an offical words on the fix.
Dunno first post maybe
"
EDIT: this is the Iray blackscreen issue that never had an offical solution since 2016, I found many related threads date back to 2016, and there's yet a solution to this problem.
So all of sudden, Iray is nearly unusable in recent build. most of time my PC fail to start iteration and rendering will be done in 3 secs with a black screen. Tried both game ready driver and studio driver, still encounter the same problem, so I doubt it's the driver issue.
Please see log in attached
My spec i7 - 5820k 16G ram, RTX2060 "
I've never seen or heard of this so called infamous bug and I help fellow users here pretty much every day. I've never had it happen to me and never seen such a report. It seems to be another in a long line of reports by people who have some problem they don't want to actually have help fixing, because the problem is certainly local to their system, but want to complaim that Daz and Nvidia are HORRIBLE!!!!!!!. I'm deathly tired of it.
Now I'll try to walk you through fixing the problem that is, as I've said several times now almost certainly on your system.
I need the full spec of the system. Motherboard model, BIOS version. RAM amount, Windows major and minor versions, DS major and minor versions.
Completely shut down the computer, wait a full 30 seconds. Start it up. Sign in to windows. Open nothing but DS.
Create a scene with a single primtive, add a shader to it. light it in some way that works for you. Add a camera. set the render to be 1080p.
Render. Did it work?
If not post the log.
If not do a full shut down again and go through the whole process and try rendering a scene that gave you an issue previously.
Does it render? If not post the log, and all of the scenes render settings and detail what is in the scene.
other than reseting the BIOS version I actually tried nearly all these steps before I created this post, even tried to render in interactive mode, same result, I don't think reseting the BIOS was the case, but tried again anyway, not working,
Ram 16G, Windows Version win 10 2004 DS version 4.12.1.118
I believe I found the problem by analysing the latest error log, DAZ suddenly refuse to recongize my GPU, or can not access to its resource, but funny enough, the trouble shooting "about your video card" was able to detect my GPU and able to list all the stats.
2020-07-25 15:09:38.554 Iray [INFO] - IRT:RENDER :: 1.0 IRT rend info : Creating irt render context (cache id: 0x0000000100000001).
2020-07-25 15:09:41.578 Iray [INFO] - IRT:RENDER :: 1.0 IRT rend info : Scene graph manager init took 2.932s
2020-07-25 15:09:41.578 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRT:RENDER :: 1.0 IRT rend error: No devices activated. Cannot render.
2020-07-25 15:09:41.578 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRT:RENDER :: 1.0 IRT rend error: Cannot render. No devices activated.
2020-07-25 15:09:41.579 Iray Render error: No sufficiently capable GPUs or selected device combination not supported.
I using the exact same system rig, GPU driver and windows version to render my scene in Blender, Poser 11, Unity and UE4 multiply times a day, for years, none of them had this problem, so it's safe to say it's not my local hardware causing this issue, on GPU driver & Windows version, Nvidia & Win 10 stayed the same for 2 month, the only change came from Daz center's update couple days ago when they introduced bridges script to other 3D tool. The exact day when this issue surfaced. So it's also clear it's unlikely the problem from Windows & Nvidia either
I did find a way to render however, is that if I let Daz soley using CPU resource to render the scene, which isn't a real solution in anyone's eye. So by all logical reason stated above, the ball is on Daz's court.
Here's little of my prespective, a 3D tool that only works on a selective group of systems or a selective of scenes is not considered "working ", that's why industry standard tools such as Maya & 3DS max require a fee to sustain because they gurantee to elimate problem like this so content creators can fully focusing on creating. Free & open source 3D tool like Blender are considered more tolorable, but it's actually surprisingly well polished, but in the case of Daz, it's easier but a progressive paid tool like Maya & 3DS, when you touch the surface of this tool, everything looks well and promsing, but when you keep exploring it, it breaks from left to right and there don't seem any fixes on sight.
People who had same issue as mine never had a solution on this
https://www.daz3d.com/forums/discussion/332301/intermittent-iray-failure
https://forums.developer.nvidia.com/t/attn-david-hart-all-drivers-after-430-86-are-breaking-iray-for-daz-studio-4-12/107912
https://forum.reallusion.com/404002/RE-Preview-Rendering-takes-forever?PageIndex=2#bm404124
Nope.
I already told the error is in your system based on what you had already posted. DS is detecting your 2060.
From your first log
Now if you will follow directions...
So curiously, why do you think it's my RTX2060 while it just tested working in blender and other 3D tools 10 out 10 times in 4k with more complex scene? that also worked on the same scene 2 days ago before the mini update?
So I just went through all your steps, created a single primitive, added a shader, render successed in 1080P mode 5 out of 5 times, 1 out of 5 times in 4k (4k worked perfectly fine 5 out of 5 times 2 days ago)
Edit: in my not so complex daz scene with 3 characters, failed 10 out 10 times in both 1080P & 4k mode.
Error log during rednering a single preimitive in 4k ->
2020-07-25 19:01:21.497 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (4 light sources with 898 triangles, 1 instance) took 0.000s
2020-07-25 19:01:21.497 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-07-25 19:01:23.141 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-07-25 19:01:23.142 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-07-25 19:01:23.142 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-07-25 19:01:23.142 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-07-25 19:01:23.142 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-07-25 19:01:23.143 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-07-25 19:01:23.210 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-07-25 19:01:23.273 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-07-25 19:01:23.274 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-07-25 19:01:23.276 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-07-25 19:01:23.294 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2020-07-25 19:01:23.294 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2060)
2020-07-25 19:01:23.295 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-07-25 19:01:23.295 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend progr: CUDA device 0 (GeForce RTX 2060): Processing scene...
2020-07-25 19:01:23.359 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Geometry memory consumption: 192.855 MiB (device 0), 0.000 B (host)
2020-07-25 19:01:23.359 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Initializing OptiX for CUDA device 0
2020-07-25 19:02:15.392 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Texture memory consumption: 3.665 GiB for 270 bitmaps (device 0)
2020-07-25 19:02:15.401 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Importing lights for motion time 0
2020-07-25 19:02:15.407 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Initializing light hierarchy.
2020-07-25 19:02:15.435 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Light hierarchy initialization took 0.026s
2020-07-25 19:02:15.442 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Lights memory consumption: 156.285 KiB (device 0)
2020-07-25 19:02:15.538 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-07-25 19:02:15.915 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : PTX code (76.160 KiB) for SM 7.5 generated in 0.375s
2020-07-25 19:02:15.915 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Materials memory consumption: 1000.469 KiB (GPU)
2020-07-25 19:02:16.889 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: Unable to allocate 134217728 bytes from 88804556 bytes of available device memory
2020-07-25 19:02:16.982 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce RTX 2060): Scene setup failed
2020-07-25 19:02:16.986 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce RTX 2060): Device failed while rendering
2020-07-25 19:02:16.988 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER :: 1.3 IRAY rend warn : All available GPUs failed.
2020-07-25 19:02:16.990 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: Fallback to CPU not allowed.
2020-07-25 19:02:16.991 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: All workers failed: aborting render
2020-07-25 19:02:16.995 Iray Render error: Internal rendering error.
Failed to follow instructions. User error. I'm out.
It would have been useful to see the log from when you rendered the primative successfully, but since you hay that it rendered successfully 5 out of 5 times then that tells us that your gfx card is working with iray. What is likely happening is that your scenes are too large to fit in the memory of the graphics card, so iray is trying to drop back to CPU, but the latest versions of Daz studio have a setting to stop rendering if iray tried to fall back to cpu.
Your "not so complex" scene with 3 characters is likely to be too large to fit in the 6GB of VRAM on your card - you will have the geometry of 3 figures, plus likey 4k maps for each one, then any scenery and/or HDMI lighting, which all adds up. I used to use a 980ti with 6GB VRAM and although that much VRAM is useable in iray, you often have to be mindful of resources when you set up a scene - either resize some of the textures, or render in sections and composite in photoshop or similar.
It might be worth looking at this product, which will resize textures in a scene and often allow it to fit into a smaller amount of VRAM: https://www.daz3d.com/scene-optimizer
I would also recommend using something like GPU-Z to monitor the card's VRAM usage - and bear in mind that Windows 10 takes a chunk of the available VRAM.
I think that the reason that your scenes are rendering on GPU in programs like Blender is because they do not need to store the entire scene in the VRAM. For iray this is different, and since nvidia makie both iray and the cards to run it on, they have no incentive to add out of core rendering, such as Octane uses.
Perfect advice.
All you need is a scene containing one or two characters with hair, props, clothing, and each item having large textures (like using hair products from OOT). That alone would be enough to cause iRay to bail out and attempt to fallback to CPU rendering.
Sometimes it takes a few tweaks to get a scene to render especially if your graphics card has less than 8Gb of VRAM.
You are exactly right, thanks for the advise. I found it's the case yesterday, 4k render usually fail if I choose it as starting render res, strangly, as long as I start to render form 720P(then quit in about 100 iteration) which usually ended up sucessful and then 1080P then 4k, it would make most scene work. But it's a such hositle, and it's quite disappointing that there's not Vram memory limit warnning from Daz's side.
I descrbied 3 character + buliding scene as "not so complex" because compare to the stuff I put in Blender and other tools, they are really small and never had issues on the same rig.
So, the issue is partial solved, but really hope Daz would step up with their tools, especially when they sell these assets in their store, one would expect them to at least test proof them or add a debugging tool.
Yes, I believe this is exactly the case, completely unaware of this as I'm still a noob to Daz, this is my 20th days of using it, if you came from another 3D tool, then you probably understand that a scene of this scale is not very big. Still, kind disappointed that there isn't a more handy debugging tool, will be more cautious with my scenes from now
I have the same problem and i didnt get this probleme befor but i will fallow some steps that posted here.
Thanks for shaearing
Same problem with light scene with 1 people, 1000*1000 scene.
windows10 64bit, rtx 2080 super.
Updated Nvidia driver to 451.77
Daz version is 4.12.1
So when I disable CPU and just try to use GPU for rendering, it stops without any image rendered
Log is below, do you have any idea how I can use GPU?
seems daz is not detecting GPU? but on the "about your video card" the GPU name and driver version is displayed
Hi, re-installed through Daz central, after upgrading driver it worked!