Block a user
Fix #114189: Workbench: VR Session crashes on exit
9c540d13bc
Ensure there's a valid GPU context when freeing a wm_surface
b98bc26173
Fix #114714: Rotating the View can drastically change the view's position when Auto Depth or Orbit Arround Select is set
ff82b25c55
I18N: Updated UI translations from git/weblate repo (548bcaeb28eba).
5b094ee770
Fix #114623: Node group asset added with wrong position from header
e10ac17fdb
Fix #114737: Curves: Random selection crash in curve select mode
EEVEE Next broken normals with "High Quality Normals" / MB & "Smooth by Angle" node
In case someone else tries to take a look at this one:
The issue comes from eevee_velocity
assuming pos_nor
is sizeof(float4)
, but that's not the case for HQ normals.
EEVEE Next: Volume render cuts off front or backside of the object
Same as #114131, this is a regression from ba89723abc and #113731. @fclem
EEVEE Next: VDB volume does not render in orthographic view
This seems to be a regression from ba89723abc and #113731. @fclem
EEVEE Next: Linked / instanced objects dont update properly
#114135 might be related
It's actually the same issue.
A proper fix will require #114112.
EEVEE Next: render region enforced in camera view, even when disabled
EEVEE next: issue with lighting
EEVEE next: issue with lighting
This is just a limitation of screen space ray tracing. That's why we have Light Probes as well.
The same issue can be seen in the old EEVEE as well if you increase the AO radius enough.
Fix #114302: EEVEE Next: Curves material compilation errors
Miguel Pozo
created branch pull-fix-curves-attributes in pragma37/blender
2023-11-07 19:54:56 +01:00
33244ab525
Fix curves attributes
d64e9759ef
Fix #114377: Workbench: Support None and Channel Packed alpha modes
b4316445a8
EEVEE-Next: Add Max Displacement option
b2bdfe946e
Fix: broken regression test fcurve_test.cc
73b15f341e
Fix: Enable Vulkan Workarounds
EEVEE Next: Wrong normal map node result (tangent space)
Fix #114524: EEVEE-Next: Wrong normal map node result
SSS broken in EEVEE Next
AFAIK, this issue was fixed a while ago. @Archeovision @Xorrito @Lteng could you confirm it?