Renders suddenly failing [rend error: No device specified or usable]
Paper Tiger
Posts: 108
I've tried everything i can think of. This all began after updating to the new game ready drivers. I've rolled back, rolled forward, clean installed, completely wiped all old drivers and reinstalled, rebooting a million times in between, updated Daz. Nothing seems to help. Render settings show the card selected, yet i still keep getting this error:
2024-10-31 11:04:46.214 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: No device specified or usable
2024-10-31 11:04:46.214 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 0 device(s):
2024-10-31 11:04:46.214 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2024-10-31 11:04:46.214 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: No worker to render with: aborting render
2024-10-31 11:04:46.214 [ERROR] Iray :: Internal rendering error.
I've seen issues like this all over the forums, in the end, no cause was ever found in any of the threads i read, let alone a solution. Guess I'm hoping maybe someone knows anyway?
UPDATE: Since the original post, i DDU'd, and reinstalled the last known working drivers i had. The problem still persists, on *every* scene ive ever created for my VN. But it will render a base character just fine, or even some of my character presets. This only seems to be happening on pre-existing scenes that get loaded?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Yep, so if I load Daz up, i can render a base shot like this. But as soon as i load any scenes, the error begins, and affects every render attempt following, until i shut Daz down.
I believe that if you hit that error then you will have to restart Daz to clear it - so bear that in mind if you are trying multiple scenes one after the other without restarting.
As to why it's happening with your scenes - check that you do not have any OT hairs with the Transmitted Color issue. If not then I did once have an item of clothing that would crash the render so double-chck to see if it's something like that. The PA for the item I had issues with did issue a fix so I was never able to find out what the problem was or if it was something fixable myself.
Also, I am not sure but I thought it was the studio drivers rather than the game drivers that were recommended?
So the render that works features the character above, the render that doesn't work also features her. I can render her normally if i load her from scratch, but if i load anything with her in it, (or any scene at all), then the issue begins. Once it starts, it is permanent until daz is restarted. I tried hiding/deleting props/clothing one by one myself, and - after it happens the first time - it happens all the way down to a blank scene. The character does use an OOT hair, but renders in that base render just fine. It also affects scenes that are entirely absent of OOT hairs. I've since reverted back to my last known working drivers (the ones i was rendering on for the last 2 months), and the issue persists, and Ive rebooted the PC a thousand times during all the troubleshooting :(
By "loading her from scratch" I assume you mean importing the character as a subset? Could it be possible that you applied a fix to the OOT hair in the subset but not in the scene you are loading? Could it be worth checking the hair in the scene to make sure that there is no image linked to the Transmitted Color property?
You have said that you tried hiding/showing items to trigger the crash - what was the item that caused the change? It's probably worth looking into that item further I would imagine.
Aye, I meant loading her from a preset. The same preset i loaded her from in the scenes that won't render. If i open daz, and load the preset, she renders in that blank scene, if i load a scene file, and then attemp to render *literally anything*, the error occurs. I will check the transmitted color image tho. And there hasn't been any identified item that causes the change. It happens on loading a scene, any scene, even two different scenes with an entirely *different* set of characters and props/environments. After a scene is loaded, regardless of what's in it, the error occurs. And persists until daz is shut down.
Alright, no maps in the transmitted color. it is rendering some scenes now, so i went back to the scene i need, and the issue returns. Something in that scene is causing it. It uses Sun/Sky, not an HDRI, i leave the sky transparent and put it in in post. Outside of that, it's got the model that works when she's alone, US2 terrain, a VDB muzzle flash, and a pistol prop. Gonna try saving it without each one of these things and attempt rendering them to see if that change anything.
Ok, first thing i deleted was the US2 terrain. And voila. It renders. So now i wanna see if recreating that exact US2 build will bring the issue back, or maybe if something just got corrupted in the last iteration of it.
Oh, so is it the Sun/Sky settings that are causing the crash? If you load an imported scene and delete the environment options do they all then render? If so then perhaps your scenes are all using a setting or value that is now "out of bounds" or invalid in the latest version of iray or nvidia drivers? So, a similar issue to the OOT hair thing where a setting was once allowed and then in a later version caused a crash. If that is the case then it would atleast give you a way to "fix" the scene maybe - even if it meant re-doing all the lighting.
EDIT: I didn't see the latest reply when I posted this and so I guess it's not relevant now that you have identified the terrain as the guilty party.
Yep, but i loaded a new US2 Terrain behind it, and the issue returned. Could be a combination issue. But this scene was rendering last night just fine, i deleted the original render because i made changes to the scene that were too big to spot-render over. Ugh, I'm ripping my hair out over here, but experimentation continues.
Ok, i rebuilt the scene from scratch, attempting to render as i added in each separate item. started with the terrain, that rendered fine, added the character, same, clothes, same, pistol, same ... and then i added the VDB muzzle flash, and the issue returned.
but i could render the muzzle flash if the terrain wasn't loaded (not hidden, the scene had to be loaded without any terrain present, otherwise the issue remained)
Definitely a confusing one
Ok, I loaded earlier scenes, in the exact same environment, just before i ever loaded the VDB muzzle flash into it, and the problem disappears.... I've got no idea why a volumetric prop would produce errors that seem to indicate that it can't find the GPU ... but, hell. At least my forward development isn't halted.
Ahh, so it's the VDB not playing nice with the US2 environment - that sounds out of my skill range so I probably cannot help any further :( I'm glad you found a way to work around it tho, hopefully it doesn't add too much to your workload.
Aye, ive gotten ahold of Oso3D, who makes the asset, he said he'd be willing to test some combinations to see if he can't help narrow it down. His current suspicion is that it's got to do specifically with *emissive* VDBs. We'll see. I'll do my best to post the answer, if we actually find it, incase anyone else runs across this in the future. Still, the fact that this all began the exact SECOND that driver version 566.03 was installed feels like too big of a coincidence to ignore, when these scenes were rendering fine for months prior to that, but we'll see.
Alright, so i know a bunch of guys who've now tried it. And yeah, that's as far as we've narrowed it down so far ... something about *emissive* VDBs seem to be hitching up in daz. I get the error, one of the others got it as well, the rest all crashed, so long as there was an emissive VDB in the scene
EDIT: Non-Emissive VDBs seem to function and render normally ... faster than they used to, even.