LineArt wrong intersection detection on scene collections containing intersecting object #104562
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#104562
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: macOS-13.1-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Max Apple 4.1 Metal - 83
Blender Version
Broken: version: 3.3.3, branch: master, commit date: 2023-01-17 08:40, hash:
rB8d94aeb604faWorked: N.A.
Short description of error
LineArt always create intersection lines if in the scene there is a collection that includes intersecting objects.
Exact steps for others to reproduce the error
open the attached lineart_intersection.blend. The file containss 2 collections:
A LineArt is created from lineart collection, even if the other collection is not involed, its intersections are incorrectly drawn on in the LineArt.
LineArt wrong intersection detection on collections with intersecting objectto LineArt wrong intersection detection on scene collections containing intersecting object@ChengduLittleA
update: As a temporary workaround issue can be fixed by using Collection Masks with Exact Match option. Still not ideal since this is limited to 8 masking layers, but at least makes the LineArt workable in such situations.
It is indeed strange.
Those intersections in the other objects don't seem to have any relation to the objects within the set collection.
Is it the interface that is a bit misleading?
It indeed looks like a bug to me (but I could be wrong).
It's currently expected for LineArt to behave this way. Initially LineArt is designed to only handle triangle and its flags so when it gets into computing, individual triangles doesn't have "which collection(s) does it belong to", otherwise it will cost a lot of memory. hence there's a separate intersection flag thingy for you to specify custom filtering.
I think we can keep this issue open because it's a concern since the beginning of LineArt, we need to think of a way to make it more convenient.
A benefit of current setup is that it's easy to choose collection flags and combine them in one line art selection without having to regroup the objects into one collection, and a lot of times your scene doesn't allow that.
@ChengduLittleA
this behaviour is totally unexpected from an user point if view.
adding a lineart is generally made by specifying a collection / object / scene to be used as source.
the current setup is consistent only whit the scene as source for lineart.
in the other two cases evaluating intersections from object outside the source you asked the user to specify for generating the lineart is not a good design choice imo.
in animation you most often (i would say always) want to separate linearts between character(s) and background.
the current design choice is not clear to the user and will generate by default overlapping intersections coming from any lineart in the file. this is trivial and difficult to troubleshoot. most users won't even get what's happening and why small segments and dots are drawn (apparently whitout a reason) in their frames.
i beleive that at least there should be a clear flag for that. like "use scene intersections (faster)" enabled by default.
while this is discussed i'd encourage you to at least update the manual to:
• reflect this actual limitation clearly
• better detail the supposed workflow for collection masks, since there is no actual description on how to use them other than the simple link to their existance. And since you are stating that at current time the users should use mask and filtering by default, i believe they should find at least a detailed information about how those wors.
also, if masking and filtering has to be intensively used for restricting intersections, raising collection layers to more than just 8 would be a good idea.
The problem with LineArt is that it's not capable of doing intersection by collections. So I think the best way here is to show a warning label below the intersection checkbox and tell the user to use intersection masks.
I'll write up a better description for the manual. (
Hopefully directly on the new gitea thingy? I heard it's much easier this way...Looks like the GIT version of the doc hasn't been migrated here yet ehh)Maybe I'll raise it to 16 bits. Even this will use more memory because this mask is recorded for each triangle/edge/edge-segment in the scene and this do accumulate... Another way is to directly record collection reference in the triangle, but then every edge segment needs to record a list of collections for later filtering and it's gonna be much more complex both during the computation and filtering. So if memory wise being acceptable, I can increase the flag bits to 16.
Does this work #104767
Oh apparently this works