New Color Pipeline, new Volumetric Raytracing, and several other changes
Pre-releaseYafaray-E v1.0.0 (2015-10-13) for Blender 2.76:
Note: from v1.0.0 I will no longer use the suffix "beta", as all YafaRay-Experimental versions are inherently betas ;-). I will use for version scheme: "Major.Minor.Bugfix". Major will be very important and structural changes with possible API breakage, Minor will be new and modified functionality without API breakage, Bugfix will be small changes and bugfixes.
- IMPORTANT CHANGES to Color Management and Color Pipeline Linear Workflow: http://www.yafaray.org/node/670
Initial prototype to try to fix the (apparently broken) YafaRay color pipeline workflow and to replace the simple gamma input/output correction with a proper sRGB decoding/coding in non-HDR files.
More information here: http://www.yafaray.org/node/670
So, I've prepared a YafaRay prototype that fixes the next issues:
- Improved Blender Color Space integration.
- The "simple" gamma correction has been replaced by Color Spaces:
- LinearRGB Linear values, no gamma correction
- sRGB sRGB encoding/decoding
- XYZ XYZ (very experimental) support
- Raw_Manual_Gamma Raw linear values that allow to set a simple gamma output correction manually
- Fixed: Double application of input gamma to the Blender Color picker. So now scenes will look brighter in general, but they should also look more realistic with less tweaking.
- Gamma input correction no longer used. The color picker floating point color values will be considered already linear and no conversion applied to them.
- For textures, added specific per-texture Color Space and gamma parameters.
- The color values exported to the XML file will be encoded acording to Blender Output Device Color Space setting.
- In yafaray-xml, new commandline option added: "-ics" or "--input-color-space" that allows to select how to interpret the XML color values. By default, for backwards compatibility, color values will be read as "LinearRGB", but using "-ics sRGB", the color values will be interpreted as sRGB. This setting does not affect the textures, as they have already per-texture specific color space/gamma parameters.
- Fixed: when exporting to file there was an error in Blender while reopening it to be shown in the Blender image view.
Several bug tracker entries are supposed to be fixed with this change:
- Color pipeline bug: http://www.yafaray.org/node/670
- Linear output forced on every scene: http://www.yafaray.org/node/603
- Gamma 1.80 input on linux: http://www.yafaray.org/node/604
- Forward compatibility with Blender Color Management: http://www.yafaray.org/node/547
- Gamma correction performed on EXR files: http://www.yafaray.org/node/549
- IMPORTANT CHANGES to Volumetrics for proper raytracing of volumes:
Problems with volumes and transparent objects have been reported in the bug tracker several times:
http://yafaray.org/node/289
http://yafaray.org/node/666
The problem was that Volumes were not really included in the raytracing process, so they were not reflected nor refracted. Now Volumes have been included in the raytracing process, so they can be refracted and reflected as any other objects. This is a significant change that could cause new issues, so please let us know about any problems in YafaRay bug tracker.
Now, if there are no parameters set in the XML for transparent background or transparent refracted background, their default values will be "false" and not "true" as until now. This will avoid confusion due to the new way "transparent refracted background" works, not rendering the background at all so volumes rendered against a transparent background do not carry "remains" of the background with them.
- Fix for attenuation when using 2 or more volumetric objects: http://www.yafaray.org/node/332
- Fix for error message "Index out of bounds in pdf1D_t" when spotlights with falloff > 0.70 and photons were used: http://www.yafaray.org/node/681
- Fix for Alpha Premultiply broken in Blender exporter: http://www.yafaray.org/node/682 Now the "Premultiply Alpha" option is back in the Exporter, but only when Export to file or to xml is selected. Premultiply will now be forced to true when exporting into Blender.
- Fix for some YafaRay camera panels incorrectly appearing in LuxRender! http://www.luxrender.net/forum/viewtopic.php?f=16&t=12405&sid=14e5a712bb33cbdee95c65fb1920ad38&start=20
DavidBluecame/Blender-Exporter@70138b7