Block a user
EEVEE Next broken normals with "High Quality Normals" / MB & "Smooth by Angle" node
EEVEE Next: Motion blur artifact when deform modifier and GPU subdivision are used
EEVEE Next Temporal Reprojection + GPU Subdivision shading bug
Miguel Pozo
deleted branch pull-eevee-fix-velocity_geo_buf from pragma37/blender
2023-11-23 19:50:09 +01:00
Fix: EEVEE-Next: Motion Vectors for non float4 position buffers
Miguel Pozo
pushed to pull-eevee-fix-velocity_geo_buf at pragma37/blender
2023-11-23 19:40:13 +01:00
1adc427020
Cleanup
Miguel Pozo
pushed to pull-eevee-fix-velocity_geo_buf at pragma37/blender
2023-11-23 19:40:01 +01:00
dbf4a5996f
Support non float4 position vertex buffers
f97580f665
GPU: Assert no UINT push constants are used
f06fd85d97
Anim: Restrict range of fcurve_to_keylist
9d8283d113
GPv3: Hide Others operator
ae1e2951c7
Fix #115144: isect_data_setup compiler error
A Shader Compile Error Occurs with Two AOV Outputs in a Specific Shader Node Configuration
Note that the relevant part of the error is this one:
EEVEE: AOVs without anti aliasing has miss colored pixels at mesh intersections
This issue is not present in EEVEE Next. Given that EEVEE Legacy is planned to be removed in 4.1, is it worth looking into it?
Fix: EEVEE-Next: Motion Vectors for non float4 position buffers
Miguel Pozo
pushed to pull-eevee-fix-velocity_geo_buf at pragma37/blender
2023-11-23 17:19:42 +01:00
0f1310d935
Support non float4 position vertex buffers
Miguel Pozo
deleted branch pull-fix-isect_data-overloads from pragma37/blender
2023-11-23 16:02:23 +01:00
Blender 4.01 crash "EXCEPTION_ACCESS_VIOLATION"
Fix #115144: isect_data_setup compiler error
Eevee Next: World shader texture coordinate node outputs wrong or missing