Support curve component in attribute proximity and attribute transfer nodes #88630

Open
opened 2021-05-27 16:52:46 +02:00 by Hans Goudey · 16 comments
Member

This will involve creating a BVH from the curve data, so the two nodes are related.

This will involve creating a BVH from the curve data, so the two nodes are related.
Author
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly

Added subscriber: @victorlouis

Added subscriber: @victorlouis

Do you plan on finding the exact closest point when a Curve is the Target (or are you planning to convert to mesh)? I assume the exact approach will involve finding the root(s) of a polynomial.

When a Curve is the source Geometry, on which domain is the output attribute going to be stored? The control points? I'm not fully familiar yet with the domains for curves. It's control points and segments right?

Do you plan on finding the exact closest point when a `Curve` is the `Target` (or are you planning to convert to mesh)? I assume the exact approach will involve finding the root(s) of a polynomial. When a `Curve` is the source `Geometry`, on which domain is the output attribute going to be stored? The control points? I'm not fully familiar yet with the domains for curves. It's control points and segments right?
Author
Member

Hi @victorlouis, sorry I missed your message! I'm not sure how that happened.

In #88630#1167621, @victorlouis wrote:
Do you plan on finding the exact closest point when a Curve is the Target (or are you planning to convert to mesh)? I assume the exact approach will involve finding the root(s) of a polynomial.

The curve code is generally based on using a set of "evaluated points", so all of the math is still quite discrete. So distance would just be either the distance from each evaluated position (in points mode) or the distance from the "edges" between those positions (in edge mode).

When a Curve is the source Geometry, on which domain is the output attribute going to be stored? The control points? I'm not fully familiar yet with the domains for curves. It's control points and segments right?

There are just two domains, spline and control points (the same "point" domain as meshes and point clouds), so the result would be stored on the point domain.

Hi @victorlouis, sorry I missed your message! I'm not sure how that happened. > In #88630#1167621, @victorlouis wrote: > Do you plan on finding the exact closest point when a `Curve` is the `Target` (or are you planning to convert to mesh)? I assume the exact approach will involve finding the root(s) of a polynomial. The curve code is generally based on using a set of "evaluated points", so all of the math is still quite discrete. So distance would just be either the distance from each evaluated position (in points mode) or the distance from the "edges" between those positions (in edge mode). > When a `Curve` is the source `Geometry`, on which domain is the output attribute going to be stored? The control points? I'm not fully familiar yet with the domains for curves. It's control points and segments right? There are just two domains, spline and control points (the same "point" domain as meshes and point clouds), so the result would be stored on the point domain.

Added subscriber: @ab_stanton

Added subscriber: @ab_stanton

So the functionality of this when using a curve as target should accomplish the exact same as curve -> curve to mesh -> attribute proximity right? But be more efficient as it would skip the mesh conversion step?

So the functionality of this when using a curve as target should accomplish the exact same as curve -> curve to mesh -> attribute proximity right? But be more efficient as it would skip the mesh conversion step?
Author
Member

Right, exactly. And for attribute transfer it should support any curve attribute.

Right, exactly. And for attribute transfer it should support any curve attribute.

Added subscriber: @dusan.paulovic

Added subscriber: @dusan.paulovic
Dušan Paulovič self-assigned this 2022-01-21 01:25:28 +01:00

Please assign to me, I have the Proximity part implemented.

Please assign to me, I have the Proximity part implemented.

Added subscriber: @sozap

Added subscriber: @sozap

Added subscriber: @Bradley_G

Added subscriber: @Bradley_G

Added subscriber: @Quijx

Added subscriber: @Quijx

Added subscriber: @mod_moder

Added subscriber: @mod_moder
Dušan Paulovič was unassigned by Iliya Katushenock 2022-10-18 22:24:38 +02:00

As far as I understand, this task is now free.

As far as I understand, this task is now free.

Added subscriber: @hadrien

Added subscriber: @hadrien
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:44:49 +01:00
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
9 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#88630
No description provided.