karma deep pass issue
1272 3 1- Piledriver
- Member
- 98 posts
- Joined: Nov. 2018
- Offline
- Heileif
- Member
- 125 posts
- Joined: Jan. 2015
- Offline
- jarjarshaq
- Member
- 29 posts
- Joined: Feb. 2016
- Offline
The behavior I'm seeing is the image render will quickly reach 100% and I can even open the snapshot file and check the render. In this case, it's a pyro explosion. The render will complete in maybe 20 minutes. Then the log will be at 100% for 2+ hours before actually completing and writing out the deep file. Is this expected?
In case it matters, I'm using xpu, only writing out the beauty aov to deep, compression of 5 and z bias of .002, and full color.
I'm sending tests with snapshot disabled, monochrome and less compression.
In case it matters, I'm using xpu, only writing out the beauty aov to deep, compression of 5 and z bias of .002, and full color.
I'm sending tests with snapshot disabled, monochrome and less compression.
Edited by jarjarshaq - April 2, 2024 12:36:50
- jarjarshaq
- Member
- 29 posts
- Joined: Feb. 2016
- Offline
As a follow up, removing any render vars from the "dcmvars" helps reduce this render time. Not remove it completely, but greatly reduces.
With beauty dcmvars:
first time stamp at 100%: 100.0%
saved deep out: Saved deep image
Total: 00:07:03
Without any dcmvars (essentially deep shadow map):
first time stamp at 100%: 100.0%
saved deep out: Saved deep image
Total: 00:03:31
That's a significant savings. Would like to see time shortened even further, because at the moment, some passes sit at 100% for 2-4 hours.
With beauty dcmvars:
first time stamp at 100%: 100.0%
saved deep out: Saved deep image
Total: 00:07:03
Without any dcmvars (essentially deep shadow map):
first time stamp at 100%: 100.0%
saved deep out: Saved deep image
Total: 00:03:31
That's a significant savings. Would like to see time shortened even further, because at the moment, some passes sit at 100% for 2-4 hours.
-
- Quick Links