OctaneRender™ Standalone 2.16 Tweet

[raul_pier]

Great, Thank you All

[abstrax]

Thanks M!

erm.. maybe Render Layer Passes as a stocking stuffer?.... before xmas?...

timbot_passes.jpg

We were hoping to get it out today, but didn't make it. So next week it will be - very likely on Monday.

[haikalle]

Thank you and Merry Christmas!

[aoktar]

Reduced the brightness of the daylight environment by a factor of 0.6 for the new daylight model and 0.8 for the old model. This way there is a better match between the texture environment and the daylight environment.

I think this is a bad idea especially when "Should" is used, in a studio's perspective.

We ran into this problem back when the C4D plugin was starting to get developed where moving an old scene to the latest Octane version would require frame blending between the old frames and the new ones due to one being "Brighter" or "Darker" than the other. Sometimes the difference would be to much and the shot would need to be completely re-rendered.

I Would like to suggest that values stay at their first released state. This way if a client comes back in 6 months for a small change we can be confident that the newly rendered frames will match the original frames and not have to deal with any sort of post correction.

Edit: Even though older scenes will be updated, I do not believe the plugin side of things work as such. I have asked Aoktar to add version-ing to materials and tags for this very reason, but it never gets implemented.

there is no exact way which is found by me. Things can be much more complex than you imagine. Any copy/paste or merging operation or etc. can cause to easily break the tracking and estimating the versioning.
Best is to leave it and inform the people.

[FrankPooleFloating]

Thanks M!

erm.. maybe Render Layer Passes as a stocking stuffer?.... before xmas?...

timbot_passes.jpg

We were hoping to get it out today, but didn't make it. So next week it will be - very likely on Monday.

Sprung out of bed with a song in my heart this morning - in anticipation of finally getting to play with Render Layer Passes!.... D'oh!

[Techie]

Thanks and happy new year!

[smicha]

A small bug Guys - when subdivision level is set to 1 and the octane benchmark scene is loaded octane crashes.

Happy New Year

[shawnfrueh]

[*] Removed the pins "Fstop" and "ISO" from the camera imager node, since they only control exposure which is done already by the exposure pin. The only thing these two pins added was confusion, since some people expected the ability to control the depth of field with Fstop. You can find a Lua script graph that emulates the old behaviour here: viewtopic.php?f=73&t=43944

I think we should go back to this topic. I feel that this was a sudden decision that a larger user base still does not know about. Octane at its core is a all about being physically accurate and here we are changing values that solve "confusion" buy removing accuracy. I know you guys here this a lot and it is the best option: Go take a look at Vray.

Here is what I suggest:

You have two crowds when it comes to Cameras, those who know how a camera in the real world works and those who don't. I am one who does not and appreciate simplifying things. But some of the jobs I get require a lot of accuracy and on top of that we have some high end lighting artists that have memorized the correct workings of a camera so I think Octane should go both ways, Simplistic and Advanced. This could then be implemented as a check box that will open the "advanced settings." This will please the technical side of artists and vise versa.

I would like to hear what others have to say about this and if you agree.


-Shawn

[funk]

You have two crowds when it comes to Cameras, those who know how a camera in the real world works and those who don't. I am one who does not and appreciate simplifying things. But some of the jobs I get require a lot of accuracy and on top of that we have some high end lighting artists that have memorized the correct workings of a camera so I think Octane should go both ways, Simplistic and Advanced. This could then be implemented as a check box that will open the "advanced settings." This will please the technical side of artists and vise versa.

I would like to hear what others have to say about this and if you agree.

I think there is a big misunderstanding here. Octane's Fstop and ISO have never worked like a real camera. A "technical" user who knows how a camera works could never have used them to produce "correct" results. Removing those pins hasn't removed any "accuracy".

[abstrax]

Sprung out of bed with a song in my heart this morning - in anticipation of finally getting to play with Render Layer Passes!.... D'oh!

Yes, sorry about that. We really wanted to get it out yesterday, but we found more issues which needed to be fixed. I think we have squashed now all the (known) problems, so I'm pretty confident that we can finally release 2.20 on Monday.