It creates bizzar file names.
[27.17] Octane Output Bug
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
-
AlexeyAdamitsky
- Posts: 103
- Joined: Fri Oct 18, 2019 4:43 pm
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.
It creates bizzar file names.
It creates bizzar file names.
-
AlexeyAdamitsky
- Posts: 103
- Joined: Fri Oct 18, 2019 4:43 pm
27.17 Blender Octane Buildlinograndiotoy wrote:Which version?
-
linograndiotoy
- Posts: 1353
- Joined: Thu Feb 01, 2018 7:10 pm
Be sure to specify the needed strings, by the way (normally those are there by default).
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).
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).
- Attachments
-
The title is 27.17 - I'm talking about that same version 27.17 
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.
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.
-
linograndiotoy
- Posts: 1353
- Joined: Thu Feb 01, 2018 7:10 pm
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).
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.
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.