Octane not saving out all passes for first frame of render
Posted: Wed Jan 10, 2024 12:34 pm
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Windows 10
B. 2x4090
C. 128gb
D. 546.33
E. 2023.1.2
F. 2023.1.2
G. Cinema 4D 2024.1.0
H. -
Whenever I render an Image sequence it is random which of the selected multi passes Octane actually saves out for the first frame. Everything renders, and I can still see and save out passes from the Picture Viewer but Octane only saves out a random number of multi passes for the first frame.
For the rest of the frames it saves everything without fail, but the first frame rendered is usually missing a few passes saved out, sometimes all but one (a random one). This can be a big problem when I´m rendering a very big single frame with a lot of samples and need the image to have alpha and a functioning CryptoMatte since saving it out from picture viewer tends to ruin these two things. This has been going on through many Octane and Cinema versions.
A. Windows 10
B. 2x4090
C. 128gb
D. 546.33
E. 2023.1.2
F. 2023.1.2
G. Cinema 4D 2024.1.0
H. -
Whenever I render an Image sequence it is random which of the selected multi passes Octane actually saves out for the first frame. Everything renders, and I can still see and save out passes from the Picture Viewer but Octane only saves out a random number of multi passes for the first frame.
For the rest of the frames it saves everything without fail, but the first frame rendered is usually missing a few passes saved out, sometimes all but one (a random one). This can be a big problem when I´m rendering a very big single frame with a lot of samples and need the image to have alpha and a functioning CryptoMatte since saving it out from picture viewer tends to ruin these two things. This has been going on through many Octane and Cinema versions.