Fernando Alcala Fernando-Alcala
  • Joined on 2020-07-08
Fernando Alcala commented on issue blender/blender#110308 2023-07-21 08:50:10 +02:00
Viewport and final render differs in lighting/materials

Nyquist sampling or something. A small viewport can not sample the fine detail enough.

Fernando Alcala commented on issue blender/blender#85840 2023-06-29 10:18:35 +02:00
Cycles: transparent object has black line where it intersect with other objects

looks a little better

My dude, it is barely visible at maximum contrast. 2.png ![3.png](/attachments/32f87ada-0258-4261-8963-36cec96aff5…

Fernando Alcala commented on issue blender/blender#107578 2023-05-03 21:46:19 +02:00
Cycles: Caustics don't work when volume boundary between casting and receiving surfaces

In this case, it is not about being limited to refractive bounces. You can add a glass cube in the scene and still get caustics. image

Volum…

Fernando Alcala commented on issue blender/blender#107482 2023-05-02 01:59:44 +02:00
Cycles motion blur does not interpolate correctly

That's because you increased the sub-stepping for Eevee but not Cycles.

Fernando Alcala commented on issue blender/blender#97259 2023-04-10 22:20:44 +02:00
Wireframe visible when going relatively far from the 0,0,0 (20 meters)

The issue was flipped. From 3.0 to 3.2, the wireframe appeared in light. shadowframe 3.2.png

The "fix" in 3.3 removed the wireframe…

Fernando Alcala commented on issue blender/blender#95305 2023-03-29 22:55:22 +02:00
Hair with dynamics and motion blur flickers on Cycles GPU render

Realease 3.5, Windows 10, 1080Ti, Optix and CUDA Problem seems to have been fixed.

Fernando Alcala commented on issue blender/blender#105637 2023-03-11 06:18:57 +01:00
Incorrect excessive darkening of volumetrically scattered light when combined with see-through shaders

Turning Path Guiding on and turning Filter Glossy off will get the light back in glass materials.

Fernando Alcala commented on issue blender/blender#104780 2023-03-04 23:23:07 +01:00
Unable to output pictures correctly when rendering version 3.2 demo with 65536*65536 resolution

Rendering at 65536 requires 360GB of ram (in total, which is mostly just displaying the render, the scene's ram requirement is negligible at this point). Rendering at 65536 is fine itself, but…