LWs native output and LWSN issue. Not saving frames.

Forums: LWs native output and LWSN issue. Not saving frames.
Sub forum for bug reports

Moderator: juanjgon

LWs native output and LWSN issue. Not saving frames.

Postby pixelsmack » Thu Jun 17, 2021 3:20 pm

pixelsmack Thu Jun 17, 2021 3:20 pm
The only way I am able to get frames saved when using LWSN is to use Octane's Render Passes system. I have tried both LWSN -2 and LWSN-3. Normally this would just be a minor annoyance, but due to another issue with Octane's regular motion blur, I am having to use Octane's Multi-Pass Motion Blur. This requires LW's native frame output to save the frame.

Here is the LWSN log. As you can see, there's no line for "saving...but also look at the render times. Seems odd."

TDOUT: [Octane] Rendering: 1 of 50 samples, 0 sec, 0.00 Ms/sec, slaves: net disabled
2021-06-17 11:16:15: 0: STDOUT: [Octane] Rendering: 2 of 50 samples, 0 sec, 96.38 Ms/sec, slaves: net disabled
2021-06-17 11:16:15: 0: STDOUT: [Octane] Rendering: 32 of 50 samples, 0 sec, 299.52 Ms/sec, slaves: net disabled
2021-06-17 11:16:15: 0: STDOUT: [Octane] Rendering: 50 of 50 samples, 0 sec, 0.00 Ms/sec, slaves: net disabled
2021-06-17 11:16:15: 0: STDOUT: [Octane] Rendering done in 0 seconds
2021-06-17 11:16:15: 0: STDOUT: [Octane] <> FRAME 3 done, render time 0 seconds
2021-06-17 11:16:15: 0: STDOUT: [Octane] <> Mem Used/Free/Total/OOC/NVLink: 2728 / 20578 / 24576 / 0 / 0
2021-06-17 11:16:15: 0: STDOUT: [Octane] <> Triangles/DisplaceTris/Hairs/Objects/Voxels rendered: 1844706 / 0 / 0 / 75 / 0
2021-06-17 11:16:15: 0: STDOUT: [Octane] <> Textures RGB32/RGB64/GREY8/GREY16 used: 12 / 0 / 0 / 0
2021-06-17 11:16:15: 0: STDOUT: [Octane]
2021-06-17 11:16:15: 0: STDOUT: [Octane] Scene closed
2021-06-17 11:16:15: 0: STDOUT: Sequence complete
pixelsmack
Licensed Customer
Licensed Customer
 
Posts: 112
Joined: Wed Jun 11, 2014 6:31 pm

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 1 guest

Fri Apr 19, 2024 11:25 pm [ UTC ]