Block a user
Fix: Cycles build error with OptiX after recent changes
@blender-bot package windows linux @blender-bot build macos-arm64
Fix: Cycles build error with OptiX after recent changes
5a381079d1
Fix: Cycles build error with OptiX after recent changes
066619e1a8
Fix: GPU: GLStorageBuf::async_flush_to_host non named path
02e6985c62
Fix #94323: Cycles blocky artifacts in overlapping volumes due to scale difference
9b61673b46
Fix: EEVEE: Add missing view bind
fccdfa2b06
Fix (unreported) missing IDTypes init in lib_remapper tests.
a92fada735
Fix: Cycles build error with OptiX after recent changes
b50de2c06f
Build: Update macOS libraries for Blender 4.2
368d6edc3c
Cycles: Update ocloc to 101.5518 on Windows
2950098012
Fix: Issue in openimagedenoise cmake config harvest
3b4d03968b
Build: Fix various issue for 4.2 macOS library update
The SLIM UV unwrap algorithm implementation for Blender 4.x
Sure, those names are fine. You can also add a few separators (uiItemS) to better group properties.
Fix #94323: Cycles blocky artifacts due to scale difference of overlapping volumes
@blender-bot build +gpu linux
Fix #94323: Cycles blocky artifacts due to scale difference of overlapping volumes
I think the same is needed in svm_node_closure_emission
.
Fix #94323: Cycles blocky artifacts due to scale difference of overlapping volumes
We could add a SD_IS_VOLUME_SHADER_EVAL
that is set in sd->flag
in volume_shader_eval
.
This would be in the runtime flags part of ShaderDataFlag
, similar to SD_BACKFACING
.
Fix #94323: Cycles blocky artifacts due to scale difference of overlapping volumes
I don't think this is the right place, because it also runs for every mix and add shader node. So it will get multiplied multiple times.
The SLIM UV unwrap algorithm implementation for Blender 4.x
One way to get around it would be to add a boolean:
[x] Importance Weights
Attribute [ uv_importance ]
Factor [ 1.0 ]
Maybe by…
Cycles: Add more procedural noise types