Attribute Math: Greater Than for the trees and flowers #83057
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#83057
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?
The return for this mode is a boolean.
This will be used to do texture based elimination of points.
Depends on #83225 (Revise whether "attribute math" comparison modes should be their own node, for flowers and trees).
Added subscriber: @dfelinto
Initial code for this node is here: e902379764
{F9475588 size=full}
Proof of the documentation so I can move this to "Ready for Testing":
I would like to challenge the engineering team to not expose the Epsilon in the UI for artists.
Added subscriber: @KenzieMac130
It could be useful in cases such as really small geometry or to quickly implement some sort of fuzzy logic or quick rounding for clustering. But probably needs a better name like "Threshold".
@astrand130 another name that came up was "rounding". It seems however that Blender already uses "Epsilon" in other places. Though I would love if we could make this more user friendly.
Added subscribers: @pablovazquez, @HooglyBoogly
@pablovazquez I think the pending thing in this task is to decide whether the mode should be expressions as they are now (!=, >=, ...) as we have in the Float Compare node, or literal names (Greater Than, ...) as we have in the math node. I leave that decision to you.
Added subscriber: @DimitriBastos
I vote for names instead of expressions. Based on the symbols only, I'm sure most users won't know what they mean.
Changed status from 'Needs Triage' to: 'Confirmed'
Current state:
attribute_compare_proper.mp4
See 62953c2bf3
This is looking good. I have one suggestion:
Based on this node tree, we can already see two nodes with a "mask" attribute. Imagine more nodes sharing this same attribute.
Can we have an attribute input node, similar to the value input node, which can be used to feed multiple attributes with a name so we just need to type the attribute one time?
Advantages:
The only problem I can see on a user based perspective is the node tree becoming more busy, but we can deal with it with some organization I think.
@DimitriBastos The light blue sockets used for attributes are really just string inputs for the name of the attribute, so it would actually be a
String Input
node. But yeah, I think that's a good idea. In the meantime exposing those sockets to the modifier is a quick way to use them in multiple places and change the name.This issue was referenced by
48ddb94a26
Changed status from 'Confirmed' to: 'Resolved'