Hello, I encounter one problem with Karma (first on XPU, but appears that it also affects CPU).
When I work in Stage, and in viewport, it renders as it should, but when try to render frame Range, I hit render to disk (or Render to disk in background) it exports just the first frame and exit render with this error message:
Failed to complete render: exit code -1073741819 Use a Log Viewer with External Render Processes enabled for more information.
I tried to include renderlog, but there is no error in there even if I set the verbose level to 9.
Just to pile on this, I found this thread because I have this exact (very odd) error code issue, on two Karma render nodes in my setup.
Can anyone from sideFX explain what this error code means, or how to debug it further (what does "Use a Log Viewer with External Render Processes enabled for more information" mean?)
Another follow-up: I asked about this on the Redshift forums, and got the following response:
Yes, sorry. This problem can be related to a crash on exit that we have due to the new CPU renderer. The workaround is to delete the CPU renderer .dll/.so/dylib from the Redshitf/bin directory to disable this feature. We are working on a fix for this issue.
Kev Ryan I've just started getting the exact same error as well, I'm trying to render fur on a character. What's the workaround?
EDIT: Just did a sweep on my curves, it's still pretty fast in my case but it definitely needs addressing.
sweep? what do you mean. Are you creating geo in sops instead of curves? I mean polywire was also workaround for me, but I had only couple of hundreds, with real fur/hair its not an option.
Edited by sniegockiszymon - Nov. 21, 2023 15:49:08
Command Exit Code: -1073741819 Failed to complete render: exit code -1073741819 Use a Log Viewer with External Render Processes enabled for more information.
No Redshift, 20.0.506, only objects in my stage are feathers with a vellum sim routed through Primitive and Houdini Feather Procedural nodes. Shaft of the feather is swept geo but the barbs are curves, XPU will run for a bit and then just stop when trying to render the frame range.
I have the same issue with rendering fur, I submitted a ticket today. Seems like they are aware of it and they will let me know when it's fixed. I will send an update on this thread whenever I hear something!
tbattistetti I will send an update on this thread whenever I hear something!
Please tell me, is there any news on this topic?
Hey! SideFX wrote back, telling me the bug is not fixed yet. However they asked me what would happen if I were to use another kind of curve type (eg. Bezier or NURBS) to see if the issue was still there. I added a convert SOP after my cache and I set it to Bezier Curve. In my case, this completely fixed the render issue, however it's just a workaround and might not work in every case. Let us know if that worked for you too! Cheers
Alt_stage Hey! SideFX wrote back, telling me the bug is not fixed yet. However they asked me what would happen if I were to use another kind of curve type (eg. Bezier or NURBS) to see if the issue was still there. I added a convert SOP after my cache and I set it to Bezier Curve. In my case, this completely fixed the render issue, however it's just a workaround and might not work in every case. Let us know if that worked for you too!
As an alternative solution, you can render the entire sequence with a single process. The USD Render ROP node has a corresponding parameter.
Hi guys Its looking like this is an NVidia driver issue (windows only). The good news is that it seems fixed in their very latest driver. Could you please test with 546.33 (available in both studio and game-ready) and let us know if it fixes this crashing issue? thanks very much!
brians Hi guys Its looking like this is an NVidia driver issue (windows only). The good news is that it seems fixed in their very latest driver. Could you please test with 546.33 (available in both studio and game-ready) and let us know if it fixes this crashing issue? thanks very much!
Hey Everyone,
I got stuck on this error while rendering strands with Karma and ended up on this thread. I managed to render my scene using a polywire SOP but render time went up by 30%. I tried the convert SOP to bezier curve without luck. I just upgraded to the latest NVIDIA Drivers (546.33) and so far so good. FYI, I tried redshift and unreal route for rendering, Karma gives the best and quickest result. Rendering a simple plexus effect with lots of DOF, but in 8K. Karma doesn't seem to mind.I'll probably drop Redshift at the next iteration of Karma!
brians Hi guys Its looking like this is an NVidia driver issue (windows only). The good news is that it seems fixed in their very latest driver. Could you please test with 546.33 (available in both studio and game-ready) and let us know if it fixes this crashing issue? thanks very much!
Hi All,
I can confirm the latest nvidia drivers fixes the issue. Rendered 900 frames without a glitch. Nice !
brians Hi guys Its looking like this is an NVidia driver issue (windows only). The good news is that it seems fixed in their very latest driver. Could you please test with 546.33 (available in both studio and game-ready) and let us know if it fixes this crashing issue? thanks very much!
!