Block a user
EEVEE-Next: Horizon Scan: Use Spherical harmonics
Just a quick test for now, but at least on this scene performs and looks better (at max resolution). Quite promising, congrats!
Miguel Pozo
pushed to pull-eevee-shadow-resolution-scale at pragma37/blender
2024-03-12 18:04:55 +01:00
df066cec52
Tag a light shading update on scene simplify update
Miguel Pozo
pushed to pull-eevee-shadow-resolution-scale at pragma37/blender
2024-03-12 17:43:16 +01:00
215e9c36f9
Take lod_bias into account for pcf scale
76410e1f66
Store lod_bias in the Light data
Miguel Pozo
created branch pull-eevee-shadow-resolution-scale in pragma37/blender
2024-03-12 17:00:53 +01:00
Miguel Pozo
pushed to pull-eevee-shadow-resolution-scale at pragma37/blender
2024-03-12 17:00:53 +01:00
05fd5bf639
Add shadow_resolution_scale
daa1739953
Merge branch 'blender-v4.1-release'
91466f71f1
Fix #91256, #112646: IDProperty UI data lost when changing type
3d5e3b60be
Fix: GPv3: Add missing call to
selection.finish()
aa3ffca8dc
Fix #119247: Curves: Extra point in evaluated spline of Curves geometry
498591c6df
Update eevee_shadow_tag_usage_lib.glsl
9f93d9a4ec
shadow debug texel
e32f7c0454
Shadows mouse pixel
a53e8d6d24
Merge branch 'blender-v4.1-release'
23fd84ffbe
Fix #118764: Freezing on Viewport Render Image during shader compilation
EEVEE Next: Subsurface causes crash/freeze
a53e8d6d24
Merge branch 'blender-v4.1-release'
23fd84ffbe
Fix #118764: Freezing on Viewport Render Image during shader compilation
60e8b56bcd
Fix: CUDA module memory leak since using primary context
Freezing if
Viewport Render Image
during EEVEE shaders compilation.
Fix #118764: Freezing on Viewport Render Image during shader compilation
Miguel Pozo
deleted branch pull-eevee-next-pcf-nvidia-bug-workaround from pragma37/blender
2024-03-11 12:23:21 +01:00
Fix: EEVEE-Next: Workaround for Nvidia shader compiler
EEVEE Legacy: volumes look different after changing the shader with 1 sample
I understand your concerns, but this always has worked like this and I'm not sure there's a good way to improve it other than disabling it.
Will this behavior be the same in EEVEE-Next?
Nop…