Block a user
Fix: Overlay-Next: Disable background images on selection
Miguel Pozo
created branch pull-overlay-images-enabled in pragma37/blender
2024-11-20 20:27:59 +01:00
26e0f3a758
Disable background images on selection
03909f2691
Fix: Overlay-Next: Images
f339ab4325
UI: Minimum Docking Target Size
09e6bab7bc
UI: Changes to Docking Operation Descriptions
29356e2bf7
Fix: Overlay-Next: Loose edges is drawn with less intensity when selected
Fix: Overlay-Next: Images
Overlay Next: Edit mode "cage" drawing is broken with Subdivision Surface modifier
Fix: Overlay-Next: Images
It has been a bit confusing but I think I managed to mimic 100% the Legacy behavior.
"View as render" background images were rendered to the default framebuffer. Non "View as render"…
ede4b5da20
Remove unused DRW_STATE_DEPTH_GREATER
029dd62f25
Mimic legacy behavior
4e63a7ee73
Merge branch 'main' into fix-overlay-images
406e93525f
Fix #130535: Name of Object not updated in viewport when name clashes.
e49498a795
Compositor: Implement Classic Kuwahara for new CPU compositor
Overlay-Next: Image Comparisions
Material reusability and fields
It's great to have that optimization already, but we should be able to reuse the same node group with different images and other constants-- stuff that would probably make the shader-sharing…
Fix: Overlay-Next: Images
I'm not sure, maybe Legacy rendered the background on a separate texture? But without this in Next the background images are rendered on top of the main render.
Fix: Overlay-Next: Images
Nope, that would be the case if we moved the In Front detection to Instance::object_is_in_front
as I suggested in the chat.
Without this change, empties with OB_EMPTY_IMAGE_DEPTH_FRONT
…
Overlay: Add Texture Space support
024502abde
Overlay: Add Texture Space support
a54bbe0b92
Fix: Overlay: In Front support
c2695e2dcc
Vulkan: Add support for legacy platforms
8c87732454
Overlay-Next: Object Name
07e197ba8c
Fix #130453: Handle empty drawing for GPv3 in Overlay Next