Light linking remove button unlinks object from actual collection #115869

Closed
opened 2023-12-07 04:56:44 +01:00 by aomay · 3 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: (newest version of Blender that worked as expected)

Short description of error
Puts the entire Collection into a light excluded state.

Then slowly start to eliminate unnecessary objects,

The object will be completely deleted.

Exact steps for others to reproduce the error
Will contain objects collection
Put in light link
Then delete the objects in the directory
The object will be deleted

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: (newest version of Blender that worked as expected) **Short description of error** Puts the entire Collection into a light excluded state. Then slowly start to eliminate unnecessary objects, The object will be completely deleted. **Exact steps for others to reproduce the error** Will contain objects collection Put in light link Then delete the objects in the directory The object will be deleted
967 KiB
aomay added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-12-07 04:56:44 +01:00
Member

Hi, thanks for the report. Can confirm. With current implementation, this looks expected as object is unlinked from the collection: https://projects.blender.org/blender/blender/src/branch/main/source/blender/blenkernel/intern/light_linking.cc#L421
@Sergey , is this intended behavior?

Hi, thanks for the report. Can confirm. With current implementation, this looks expected as object is unlinked from the collection: https://projects.blender.org/blender/blender/src/branch/main/source/blender/blenkernel/intern/light_linking.cc#L421 @Sergey , is this intended behavior?
Pratik Borhade changed title from light excluded Kill Obj to Light linking remove button unlinks object from actual collection 2023-12-07 08:11:31 +01:00

It is expected behavior indeed. The light and shadow linking collections are regular collections. They might or might not be linked to the scene.

If you want light/shadow linking collection to have different content from what it is in the scene the collection needs to be made single user.

It is expected behavior indeed. The light and shadow linking collections are regular collections. They might or might not be linked to the scene. If you want light/shadow linking collection to have different content from what it is in the scene the collection needs to be made single user.
Blender Bot added
Status
Archived
and removed
Status
Needs Info from Developers
labels 2024-01-02 14:33:14 +01:00

I just had an ah ha moment with this functionality, though I still disagree with the approach:

  • If you choose the collection you want to enable/disable light links in, and then delete an object from that collection (in light linking) then it also deletes the object in the scene.

  • But if you create a new light linking collection, deleting an object from this collection does not delete the object in the scene

This distinction is the clincher with this whole thing, and because this functionality is not intuitive the user is left to their own frustration and must learn the hard way.

Personally, an intuitive approach to software should be paramount to functional programming. Any user would assume that a light linking collection is not an actual collection, so deleting items from here should be safe. How many people are going to hit that minus button only to find out, often when it's far too late to fix, that they've actually deleted the object from their scene? It just really makes no sense.

I just had an ah ha moment with this functionality, though I still disagree with the approach: - If you choose the collection you want to enable/disable light links in, and then delete an object from that collection (in light linking) then it also deletes the object in the scene. - But if you create a new light linking collection, deleting an object from this collection does not delete the object in the scene This distinction is the clincher with this whole thing, and because this functionality is not intuitive the user is left to their own frustration and must learn the hard way. Personally, an intuitive approach to software should be paramount to functional programming. Any user would assume that a light linking collection is not an actual collection, so deleting items from here should be safe. How many people are going to hit that minus button only to find out, often when it's far too late to fix, that they've actually deleted the object from their scene? It just really makes no sense.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#115869
No description provided.