France
Joined: Nov 7, 2005
Post Count: 9432
Status:
Offline
Re: YafaRay rendering plug-in
To fix the bug described in my previous message, David Bluecame recommended to try setting adv_auto_min_raydist_enabled or adv_auto_shadow_bias_enabled parameters to true and play with the values of adv_min_raydist_value and adv_shadow_bias_value. Changing adv_min_raydist_value didn't have some effect but adv_shadow_bias_value did, the reason why I published the version 1.4.3 (there was only little feedback about it and I'm not sure it's the perfect solution). Try to set adv_shadow_bias_value with a float or double value, not a boolean value. The fastest way to try some YafaRay parameters and get their type is to look at a XML YafaRay example like this one: bval is for boolean values, fval for float or double values, ival for integer values, sval for strings.
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
----------------------------------------
[Edit 1 times,
last edit by Puybaret at Jan 25, 2021, 9:38:39 AM]
Joined: May 28, 2015
Post Count: 607
Status:
Offline
Re: YafaRay rendering plug-in
By following this method I got the same results as you and I found that the shadow_bias parameter takes precedence over min_raydist. There may be another parameter that comes into account because for the same values, the rendering is different when the auto mode is enabled for shadow_bias.
----------------------------------------
EnkoNyito
Joined: Jul 20, 2020
Post Count: 12
Status:
Offline
Re: YafaRay rendering plug-in
I've been using Yafaray since last summer, and overall I've had a good experience. However, I have three lingering issues, and I wondered if I'm just clueless on using the software properly (quite possible), or if they are the result of bugs.
Note: I typically use Yafaray at Level 4, with Photon, Lanczos and Shinydiffusemat, but I have seen the same issues with every setting I've tried.
1) First, I use some mantle clock furniture objects, and somehow whenever I render them with Yafaray, the clock face is missing, like this:
For reference, with SunFlow, they render properly, like this:
2) Secondly, the lamps (from SH3D default furniture set) are lighting incorrectly; the light "shines through," even when the lighting is set at a low percentage intensity. Like in the following example (lamp set at 7%):
3) Finaly, when using the Multiple photo rendering (v.2.1) plug-in, there seems to be some kind of memory management issue. The memory used by SH3D keeps getting larger with each render, usually leading to a crash when it goes above 200 GB or so, which is about 4-5 renders on a .sh3d file of about 1.75 GB. I can live with restarting the app every 4 renders, it's not a big deal, but I thought maybe it could be useful to report the problem here.
Joined: May 28, 2015
Post Count: 607
Status:
Offline
Re: YafaRay rendering plug-in
@GhyslainB
I've been using Yafaray since last summer, and overall I've had a good experience. However, I have three lingering issues, and I wondered if I'm just clueless on using the software properly (quite possible), or if they are the result of bugs.
Note: I typically use Yafaray at Level 4, with Photon, Lanczos and Shinydiffusemat, but I have seen the same issues with every setting I've tried.
1) First, I use some mantle clock furniture objects, and somehow whenever I render them with Yafaray, the clock face is missing,
Could you provide the link where to download this clock?
2) Secondly, the lamps (from SH3D default furniture set) are lighting incorrectly; the light "shines through," even when the lighting is set at a low percentage intensity.
This usually happens during indirect rendering (path tracing, photon mapping or sppm) with the YafaRay engine. It seems that the light source diffuses through the object making the faces of the mesh visible.
3) Finaly, when using the Multiple photo rendering (v.2.1) plug-in, there seems to be some kind of memory management issue. The memory used by SH3D keeps getting larger with each render, usually leading to a crash when it goes above 200 GB or so, which is about 4-5 renders on a .sh3d file of about 1.75 GB. I can live with restarting the app every 4 renders, it's not a big deal, but I thought maybe it could be useful to report the problem here.
If your memory problem when rendering is similar to this one, you can create a bugs or feature requests ticket.
----------------------------------------
EnkoNyito
Joined: May 28, 2015
Post Count: 607
Status:
Offline
Re: YafaRay rendering plug-in
Emmanuel,
GhyslainB's Mantle Clock is made up of 51 materials (2 colors and 49 textures). Even by making the ForegroundColor and FrontColorNoCulling materials invisible, the problem persists.
Here is a comparative rendering without changing the source code.
France
Joined: Nov 7, 2005
Post Count: 9432
Status:
Offline
Re: YafaRay rendering plug-in
There must be a problem with double sides or with normals in the Mantle Clock. When you remove normals from OBJ files (remove the last /vindex in the triplets of the lines starting by f), or when you import / reexport the model in Blender, the parts of the clock which are rendered in black aren't black anymore. Which software was used to design it?
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
Joined: May 28, 2015
Post Count: 607
Status:
Offline
Re: YafaRay rendering plug-in
There must be a problem with double sides or with normals in the Mantle Clock. When you remove normals from OBJ files (remove the last /vindex in the triplets of the lines starting by f), or when you import / reexport the model in Blender, the parts of the clock which are rendered in black aren't black anymore. Which software was used to design it?
GhyslainB could tell you where he found this object and possibly what software was used to design it.
By replacing the textures with colors for the problematic materials (material0, material6, material9), I get this result.
----------------------------------------
EnkoNyito
