View topic - New YafaRay v3.2.0 released!

New YafaRay v3.2.0 released!

General questions related with the YafaRay Project, 3D computer graphics and about this site.

New YafaRay v3.2.0 released!

Post Sun Mar 26, 2017 8:52 am

Hello,

I would like to announce the release of the new version v3.2.0. I hope you like it!

You can download builds for Linux 32/64bit, Windows 32/64 bits and MacOSX 64bits (however the Mac build needs additional tests, as I only can do *very* limited tests for the Mac builds)

The list of changes between v3.1.1-beta and v3.2.0 can be seen in the download pages below.

The Blender-Exporter builds can be downloaded from:
https://github.com/YafaRay/Blender-Exporter/releases/tag/v3.2.0

The Standalone builds (to be used with other software than Blender such as Wings3D for example) can be downloaded from:
https://github.com/YafaRay/Core/releases/tag/v3.2.0

There is also a SketchUp 2017 (windows 64bit) YafaRay plugin. It works but it's in an "alpha" experimental and very early state. For now I'm having problems to generate a MacOSX build so only Windows for now...
https://github.com/YafaRay/su2yafaray/releases/tag/v3.2.0-alpha

Please if you have any issues with it, let us know in the Bug Tracker and/or Forums.



The list of changes for the Blender-Exporter between v3.1.1-beta and v3.2.0 are:

Feature changes/additions in v3.2.0:
------------------------------------
* IMPORTANT: Support for Texture Mipmaps / Ray Differentials, see: http://yafaray.org/node/695 `[Blender Exporter + Core]`
- Modifier all ImageHandlers to standardise access and make them more flexible. BIG changes to ImageHandlers.
- Added new Grayscale internal buffers (optional)
- Reorganized all Interpolation and GetColor code
- Added MipMap capability to ImageHandlers
- Added Trilinear MipMap interpolation based on Ray Differentials.
- Added EWA MipMap interpolation based on Ray Differentials
- Heavily modified IBL blur function, to use mipmaps with manually calculated mipmap level instead of the previous dedicated "IBL blur" process

* Path Tracing integrator: added new Russian Roulette parameter to speed up path tracing, see: http://www.yafaray.org/node/775 `[Blender Exporter + Core]`
The relevant parameter will be "russian_roulette_min_bounces".
- If this parameter is set to 0, russian roulette will be enabled.
- If set to the same value specified in depth (max bounces), russian roulette will be disabled
- If set to a value between 0 and max bounces, then russian roulette will only start be applied after this number of bounces, so we can get decent sampling in dark areas for example and get a good speedup with less noise.
- Lower values of this parameter will result in faster (but somewhat noisier) renders.

* yafaray-xml: better autodetection of plugins path, but in some cases "-pp" may still be needed `[Core]`

* Building system: many changes to make the building process easier and more integrated with Git `[Blender Exporter + Core]`

* Building system: standalone builds generated again `[Core]`

* Building system: added building instructions and test scenes `[Blender Exporter + Core]`

* QT4 support reintroduced and updated for YafaRay v3, but still in a basic state, many features not available yet for the Qt interface `[Blender Exporter + Core]`

* Re-added ability to generate Sketchup plugins again `[Core]`

* Texture mapping: allow MirrorX,MirrorY even when Repeat = 1 `[Blender Exporter + Core]`

Bug fixes in v3.2.0:
--------------------
* IMPORTANT: Path/Photon OneDirectLight - attempt to sample lights more uniformly, see: http://www.yafaray.org/node/803 `[Core]`
This has been a significant bug, that went unnoticed for a very long time and was causing severe artifacts in Photon Mapping and Path Tracing when lights were not uniformly lighting the scene. Now with this fix, renders should be much more correct and hopefully more realistic!

* IMPORTANT: all integrators, SPPM and path roulette: Fixing non-randomness repetitive patterns, see: http://www.yafaray.org/node/792 `[Core]`
Another important bug that went unnoticed for a very long time. A lack of randomness caused severe patterns in BiDirectional integrator and probably some artifacts (in less extent) in the others. We hope this change helps to achieve more correct and realistic results now.

* IMPORTANT: big changes to textures interpolation and colorspace processing, see: http://yafaray.org/node/787 `[Core]`
- I found out that YafaRay was doing the texture interpolation *after* decoding the texels color space. This was causing significant differences in color between standard bilinear/bicubic and when using trilinear or EWA mipmaps.

- The Core code has been modified so from v3.2.0 onwards all internal image buffers will be converted to "linear RGB" during the texture loading process. That will allow a correct color interpolation process, and probably slightly faster than before. Hopefully this should improve color fidelity respect to the original texture images used for the scene.

- Also, all textures will be "optimized" by default. I think it's clear by now that optimized textures greatly improve memory usage and apparently don't cause slowdowns (might even make it slightly faster due to reduced RAM access?). To accomodate the extra color information necessary to store "linear RGB" values in the optimized buffers, their size will be around 20-25% bigger respect to v3.1.1, therefore a RAM usage increase will happen now compared with previous versions.

- For optimal results, from now on the user will be responsible for selecting correct ColorSpaces for all textures, including bump map, normal map, etc. For example for Non-RGB / Stencil / Bump / Normal maps, etc, textures are typically already linear and the user should select "linearRGB" in the texture properties, but if the user (by mistake) keeps the default sRGB for them, YafaRay will (incorrectly) apply the sRGB->LinearRGB conversion causing the values to be incorrect. However, I've added a "fail safe" so for any "float" textures, bump maps, normal maps, etc, when getting colors after interpolatio YafaRay will to a "inverse" color conversion to the original Color Space. This way, even a mistake in user's color space selection in bump maps, normal maps, etc, will not cause any significant problems in the image as they will be converted back to their original color space. However, in this case rendering will be slower and potential artifacts can appear due to interpolation taking place in the wrong color space. For optimal results, the user must select correctly the color space for all textures.

* Bidirectional integrator changes `[Blender Exporter + Core]`
- Will be supported again, although will be considered "unstable" until the (many) issues it has are completely fixed.
- Fixed issue with excessive brightness that happened after render finished.

* Fix for SPPM sudden brightness change when reaching approx 4,300 million photons. See: http://www.yafaray.org/node/772 `[Core]`

* Fixed bug that caused many extra render passes to be generated in some cases `[Core]`

* Fixed crash when using Blender Exporter and Core with Ruby bindings support enabled `[Blender Exporter + Core]`

* Image Texture Interpolation fixes, see: http://www.yafaray.org/node/783 `[Core]`

* Angular camera: fixed wrong renders due to incorrect default clipping, see: http://yafaray.org/node/779 `[Core]`

* Fixed EXR MultiLayer image file saving `[Core]`

* Fixed uninitialized values generated by Ambient Occlusion sampling `[Core]`

* AA user interface: fixed disabled filter type and pixel width when passes=1 `[Blender Exporter]`

* Show the Physics tab in Blender, see: http://yafaray.org/node/797 `[Blender Exporter]`

* Several other fixes and improvements, especially for the building system and tools for developers.
User avatar
David Bluecame
 
Posts: 355
Joined: Mon Jan 21, 2013 12:42 pm
Location: Spain

Re: New YafaRay v3.2.0 released!

Post Sun Mar 26, 2017 9:25 am

For your information, from this release onwards, the versioning number will be as follows:

* "bleeding edge" daily builds: any more changes (bugfixes and/or new features) on top of v3.2.0 will be named v3.2.0-1, v3.2.0-2, v3.2.0-3, etc, until a new Release is released
* If there is need to release a "bugfix-only" release based on the changes mentioned, it will be v3.2.1 (containing v3.2.0-1, v3.2.0-2, etc)
* After that bugfix release, subsequent daily builds will show: v3.2.1-1, v3.2.1-2, v3.2.1-3, etc
* If there is another bugfix-only release it will be v3.2.2, containing the changes in v3.2.1-1, v3.2.1-2, etc.
* etc, etc
* If new features are introduced, the version number for the "new features release" will become v3.3.0. It will include all commits/changes done after releasing v3.2.0, including any bugfixes, etc.
* If any radical and structural changes are introduced, the version number will become v4.0.0

I hope this makes sense and allows us to standardise versioning from now on, so no need for "alpha" versions as there will always be the possibility of downloading and testing any of the "bleeding edge" daily builds that will be automatically generated every time we send a commit to the master branch, and can be downloaded from http://www.yafaray.org/daily_builds/index.html
User avatar
David Bluecame
 
Posts: 355
Joined: Mon Jan 21, 2013 12:42 pm
Location: Spain

Re: New YafaRay v3.2.0 released!

Post Mon Mar 27, 2017 7:36 am

Thanks to all of you and especially to you David for this new version !!!

Compliments ! ;)

John

http://www.accasoftware.com
John_c
 
Posts: 4
Joined: Fri Jun 20, 2014 7:39 am


Return to News & Discussion



Who is online

Users browsing this forum: No registered users and 2 guests

cron