Cycles: Use 0.01m as default point cloud radius

Currently Cycles uses zero as a default radius when no "radius"
attribute exists. This is more confusing than helpful. Instead,
use the same default radius as EEVEE and Workbench.
This commit is contained in:
Hans Goudey 2022-10-12 12:23:23 -05:00
parent 605f87256e
commit a6db2c22b1
Notes: blender-bot 2024-04-11 14:26:06 +02:00
Referenced by commit e3de5af135, Fix wrong Cycles default radius for motion blurred point clouds
1 changed files with 1 additions and 1 deletions

View File

@ -194,7 +194,7 @@ static void export_pointcloud(Scene *scene,
/* Export points. */
for (int i = 0; i < num_points; i++) {
const float3 co = get_float3(b_attr_position.data[i].vector());
const float radius = b_attr_radius ? b_attr_radius->data[i].value() : 0.0f;
const float radius = b_attr_radius ? b_attr_radius->data[i].value() : 0.01f;
pointcloud->add_point(co, radius);
/* Random number per point. */