OctaneRender™ Standalone 3.04

[doca]

Hi doca,
please, try with "Tonemap the render passes" option active when saving info passes.
ciao beppe

Hi beppe, abstrax,
Render passes works fine except "Lighting passes". Here is an example , and I have to mention that light ID setup is properly done and it works in Octane 3.03.04, (screen grabs of the same screen portion):
BEAUTY:

Capture2.JPG

Ambient color looks ok:

Capture3.JPG

But, Light ID1, ID2, ID3.... Are not working:

Capture4.JPG

Capture5.JPG

Object Color ID is ok, too:

Capture6.JPG

[abstrax]

Hi doca,
please, try with "Tonemap the render passes" option active when saving info passes.
ciao beppe

Hi beppe, abstrax,
Render passes works fine except "Lighting passes". Here is an example , and I have to mention that light ID setup is properly done and it works in Octane 3.03.04, (screen grabs of the same screen portion):
BEAUTY:

Capture2.JPG

Ambient color looks ok:

Capture3.JPG

But, Light ID1, ID2, ID3.... Are not working:

Capture4.JPG

Capture5.JPG

Object Color ID is ok, too:

Capture6.JPG

I can't reproduce the issue. For example in this little test scene, it works correctly as far as I can see:

light_pass_test.orbx

-> If you could send me a scene that lets us reproduce the issue we are happy to fix it as soon as possible.

[nuno1980]

@abstrax:
NOTICE: Please should reply me - my message

[doca]

-> If you could send me a scene that lets us reproduce the issue we are happy to fix it as soon as possible.

Hey absrax, your scene renders correctly. No luck with my scene.
I've attached simplified scene that renders lightID passes wrong way. Can't figure what is the problem. In 3.03.04 everything works fine.
Best,
Doca

[abstrax]

-> If you could send me a scene that lets us reproduce the issue we are happy to fix it as soon as possible.

Hey absrax, your scene renders correctly. No luck with my scene.
I've attached simplified scene that renders lightID passes wrong way. Can't figure what is the problem. In 3.03.04 everything works fine.
Best,
Doca

Thanks for your scene. I found and fixed the issue. Since there were a couple of other annoying issues, we plan to get a new build as soon as possible. Probably at the end of the week.

[doca]

-> If you could send me a scene that lets us reproduce the issue we are happy to fix it as soon as possible.

Hey absrax, your scene renders correctly. No luck with my scene.
I've attached simplified scene that renders lightID passes wrong way. Can't figure what is the problem. In 3.03.04 everything works fine.
Best,
Doca

Thanks for your scene. I found and fixed the issue. Since there were a couple of other annoying issues, we plan to get a new build as soon as possible. Probably at the end of the week.

Great to hear that!!!
And, if i can suggest for that release:

awesome!

love the batch render node. One improvement that would be great; add the file path selection to the main node rather than asking when running the render. This way, the node can be saved to your localdb and reused with the same settings every time.

[abstrax]

Great to hear that!!!
And, if i can suggest for that release:

awesome!

love the batch render node. One improvement that would be great; add the file path selection to the main node rather than asking when running the render. This way, the node can be saved to your localdb and reused with the same settings every time.

I don't fully understand. Why would you always want to render into the same directory? Or do you mean something else?

[calus]

love the batch render node. One improvement that would be great; add the file path selection to the main node rather than asking when running the render. This way, the node can be saved to your localdb and reused with the same settings every time.

I don't fully understand. Why would you always want to render into the same directory? Or do you mean something else?

Gah's argument about saving batch render job to localdb is confusing and has nothing to do with the Output Folder problem.

The point is : why would you want to have to set the Output Folder everytime you run the batch render job ?
Output Folder shouldn't be an interactive step, but should be one of the the imput of the batch render job.



Also considere to change the default filename template from %n_%f_%p.%e to %n_%p_%f.%e,
because most of the applications need frame number to be at the end of the filename to recognize an image sequence.

[Elvissuperstar007]

slice cap
add to in the road map

[doca]

I don't fully understand. Why would you always want to render into the same directory? Or do you mean something else?

Ok, it is not well explained.
The point is to have already predefined frame range and output path for each Render target (different paths, different frameranges). Lets say, I do have project with multiple cameras, or multiple shots, and I want to render them all over night. Now, I can set output and frame range only for one, right?
And I have to change output path and frame range every time I hit batch render if I do have multiple Render targets. Right again?
There is my suggestion in the attachment. And suggestion is to have option to define frame range and output path for each Render target. That way I can have multiple Render targets rendered overnight without having to wake up and setup new path and frame range for each sequence/Render target.
I hope, that I explained well.
Best,
Doca