Hi Juan,
I've noticed that F-Stop and ISO have been removed from the Camera Imager - why was this done, and is it a permanent change?
Build 2.6.4 (2.06) vs. 2.16 exposure issue.
I have a scene rendered in plugin build 2.6.4 which has an exposure of 1.9833 (F-stop 0.5 and ISO 100) and when the same scene is opened in 2.16 the exposure jumps to 36.7098 and then scene is over-exposed. What is happening here and how do I correct accurately and predictably going forward?
Regards
Carlo
F-Stop and ISO + other questions.
Moderator: juanjgon
Yes, this parameters have been removed from the Octane API in the 2.15 release. They are not physical correct, and only related to the exposure control.
There was two changes in the exposure parameters along the 2.x cycle. One in the version 2.05 and other in the version 2.15. In theory the plugin should update the exposure value for the old scenes, but perhaps there is a problem with this update code.
Do you have this problem with all your scenes?
-Juanjo
There was two changes in the exposure parameters along the 2.x cycle. One in the version 2.05 and other in the version 2.15. In theory the plugin should update the exposure value for the old scenes, but perhaps there is a problem with this update code.
Do you have this problem with all your scenes?
-Juanjo
Perhaps there is something in this scene that also affects the final exposure (I remember also a change in the skylight brightness in the 2.16 release, but this parameter also should be updated by the plugin). If you have this problem with more scenes, let me know.
-Juanjo
-Juanjo
Yes, no problem: [email protected]