Page 1 of 2

[27.17] Octane Output Bug

PostPosted: Fri Aug 11, 2023 1:25 pm
by AlexeyAdamitsky
I can't make Octane work reliably for saving images now. AOVs are ignoring some settings and Octane is pretty much ignoring settings in the Octane Output.

Image

It creates bizzar file names.

Image

Re: [27.17] Octane Output Bug

PostPosted: Sat Aug 19, 2023 8:26 am
by linograndiotoy
Which version?

Re: [27.17] Octane Output Bug

PostPosted: Sat Aug 19, 2023 8:59 am
by AlexeyAdamitsky
linograndiotoy wrote:Which version?


27.17 Blender Octane Build

Re: [27.17] Octane Output Bug

PostPosted: Thu Aug 24, 2023 8:27 am
by linograndiotoy
Be sure to specify the needed strings, by the way (normally those are there by default).

Capture.JPG

Re: [27.17] Octane Output Bug

PostPosted: Thu Feb 15, 2024 2:05 am
by dmerziii
This is still a bug.

I'm using the string as suggested, but the frame #s are not saving, and each frame is overwriting the previous frame when rendering more than 1 frame.

Re: [27.17] Octane Output Bug

PostPosted: Thu Feb 15, 2024 2:11 am
by dmerziii
I did a little test with 4 Frames, I turned off the checkbox that says overwrite.

And now I do get 4 outputs, but the frame # is still missing, instead it keeps adding a zero for each new frame, and if I had a simple 150 frame animation that would get ridiculous (not to mention, useless).

Re: [27.17] Octane Output Bug

PostPosted: Thu Feb 22, 2024 7:53 am
by linograndiotoy
Which version?

Re: [27.17] Octane Output Bug

PostPosted: Tue Feb 27, 2024 1:03 am
by dmerziii
The title is 27.17 - I'm talking about that same version 27.17 :D
It's the latest available for Octane 2022 - I'm not even going to try updating to 2023 - as that just seemed to introduce new bugs.

I've since reverted back to 27.16 because this output bug is detremental to any real production workflow.

Re: [27.17] Octane Output Bug

PostPosted: Tue Feb 27, 2024 10:58 am
by linograndiotoy
2023 is definitely very good indeed, especially the build we'll release tomorrow (which corrects Hue and Saturation valuies when a 2021 or 2022 scene is loaded).

Re: [27.17] Octane Output Bug

PostPosted: Thu Feb 29, 2024 4:04 pm
by dmerziii
Lino, I 100% appreciate the sentitment, and I do appreciate your responding to me, but you've got to understand though, as a production artist, working on critical work with deadlines that I cannot be a beta tester with my project files while new versions are fixing bugs for new features.
I am sticking with 2022 for now on this project because it's got all the features I need (and am familiar with on a long-run project) and it works for me 99% - with the exception of this output bug, which is unfortunately, quite a big bug.

Chasing new versions, and hoping the new fix coming 'tomorrow' doesn't create new problems is not going to cut it for serious client work, not to mention when I have to consider the other factors such as other artists I am collaborating with, I'm not working inside of a bubble.

That's why I love the idea of Blender's LTR versions, studios and production-level work know that even if the feature set is a few months/years behind, the bugs will still be fixed so we're not stuck with a broken version and can get work done consistently.

Once I am done with this large project, and can navigate new features, I will be updating to 2023.