LineArt: "Force intersection" doesn't work like expected #101887

Open
opened 2022-10-18 08:48:31 +02:00 by Christoph Werner · 9 comments

System Information
Version: 3.3.2 Release Candidate, branch: master, commit date: 2022-10-17 14:20, hash: c98268d3f5, type: release
Build date: 2022-10-18, 00:42:54
Platform: 'Windows-10-10.0.22621-SP0'

Renderer: 'NVIDIA GeForce RTX 3090/PCIe/SSE2'
Vendor: 'NVIDIA Corporation'
Version: '4.5.0 NVIDIA 516.59'

Short description of error
Line Art usage mode "Force Intersection" doesn't work like expected. See my screenshot and attached file for tests.

Objects or collections that are set to "Force Intersection" should always produce intersections, even if other rules defines something else.
Line Art usage set to "Force Intersection" should work like a global line art override.

Exact steps for others to reproduce the error

  1. Try to set the Line Art usage of object "Cube1" to Force Intersection mode.
  2. Try to set the Line Art usage settings to "Force Intersection" to the Collection called "Forced Intersections".
  • Both settings produce no results, means: Cube1 intersections with other objects aren't visible.

Screenshot:
image.png

File:
IntersectionBug.blend

**System Information** Version: 3.3.2 Release Candidate, branch: master, commit date: 2022-10-17 14:20, hash: c98268d3f56d, type: release Build date: 2022-10-18, 00:42:54 Platform: 'Windows-10-10.0.22621-SP0' Renderer: 'NVIDIA GeForce RTX 3090/PCIe/SSE2' Vendor: 'NVIDIA Corporation' Version: '4.5.0 NVIDIA 516.59' **Short description of error** Line Art usage mode "Force Intersection" doesn't work like expected. See my screenshot and attached file for tests. Objects or collections that are set to "Force Intersection" should always produce intersections, even if other rules defines something else. Line Art usage set to "Force Intersection" should work like a global line art override. **Exact steps for others to reproduce the error** 1. Try to set the Line Art usage of object "Cube1" to Force Intersection mode. 2. Try to set the Line Art usage settings to "Force Intersection" to the Collection called "Forced Intersections". - >Both settings produce no results, means: Cube1 intersections with other objects aren't visible. **Screenshot:** ![image.png](https://archive.blender.org/developer/F13702349/image.png) **File:** [IntersectionBug.blend](https://archive.blender.org/developer/F13702386/IntersectionBug.blend)

Added subscriber: @ChristophWerner

Added subscriber: @ChristophWerner

Added subscriber: @ChengduLittleA

Added subscriber: @ChengduLittleA
Member

Looks like an issue... Let me check

Looks like an issue... Let me check
Member

After some discussion we found out that it's not quite aligned with how line art works, because object/collection intersection option can't actually override modifier option (because the modifier only filters the result). We might be able to leave it for a while and see if we can come up with a simpler logic pattern for this kind of use cases.

After some discussion we found out that it's not quite aligned with how line art works, because object/collection intersection option can't actually override modifier option (because the modifier only filters the result). We might be able to leave it for a while and see if we can come up with a simpler logic pattern for this kind of use cases.

@ChengduLittleA: Exactly.

You can set this to archived. Thank you.

@ChengduLittleA: Exactly. You can set this to archived. Thank you.
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

because object/collection intersection option can't actually override modifier option (because the modifier only filters the result)

@ChengduLittleA , since the current behavior is expected , do you want to keep this report open as a DESIGN or a TODO? or you prefer to archive it?

> because object/collection intersection option can't actually override modifier option (because the modifier only filters the result) @ChengduLittleA , since the current behavior is expected , do you want to keep this report open as a `DESIGN` or a `TODO`? or you prefer to archive it?
Member

Hi! Sorry for the delay! I think this can be left as a DESIGN. :D

Hi! Sorry for the delay! I think this can be left as a `DESIGN`. :D
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
3 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#101887
No description provided.