Animated Values in Node Trees and Geometry Nodes Modifier are not distinguishable #91917
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
12 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#91917
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: all
Graphics card: all
Blender Version
Broken: blender-3.0.0-alpha+master.12e8c783535c and below
Short description of error
Hello dear Blender devs,
Hello dear Geometry Nodes developers and maintainers,
I did wait some time before reporting this as a "bug" as from some perspective this might sound like a feature request. But as there are some, to users unidentifiable names used, I guess this is may very well count as a bug.
When working in Geometry nodes it is important to be able to keyframe some values and properties to achieve more controlled and art directable Animation of the Asset. While the setting of keyframes works really well, it gets really complicated to tell the different animation channels apart as they neither show the nodes name nor the nodes Label.
Exact steps for others to reproduce the error
Open attached file, try to figure out which graph in the editor belongs to which Node.
geonodes_01.blend
For simplification I added three screenshots each showing one of the three cases I could Isolate where this bug appears:
1.) Animating Node Values in the Geometry Nodes Tree
2.) Animating Exposed Custom Properties of the Geometry Nodes Modifier
3.) Animating Node Values inside the Shader Graph.
Thank you in advance for your evaluation of this bug report
Alex / zuggamasta
Added subscriber: @zuggamasta
#95255 was marked as duplicate of this issue
#93985 was marked as duplicate of this issue
#92973 was marked as duplicate of this issue
Added subscriber: @Erindale
Maybe a better solution would be to use use
Node Name (Node Label)
so likeValue.001 (Height)
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Confirmed'
Not sure if this would be classified as bug, but will confirm as this would be good to fix. Other nodes like shader, compositor do display property names.
Added subscriber: @JacquesLucke
This is a known issue unfortunately. Would still be good to look into more of course, but it doesn't strictly classify as a bug.
Also, there are really two separate issues here: The one that applies to all node systems, and the one that applies applies to the geometry nodes modifier specifically.
This issue was referenced by
8b516d8712
Added subscriber: @lichtwerk
Node name (unfortunately label was not possible) is now included, see
8b516d8712
and discussion in D13085.Will check on modifier next.
Added subscriber: @3di
Added subscriber: @CosmoMidias
Will have to concentrate on triaging for a while (and step down).
Added subscriber: @alonabrany
Changed status from 'Confirmed' to: 'Needs Developer To Reproduce'
And first of all:
THANK YOU FOR EVERYONE WORKING ON THIS IN THE PAST <3 <3 <3
Your time and work on this is greatly appreciated.
Hello everybody,
while the original bug is now fixed the current solution still is less than practical to use.
Blender 3.2.0 Alpha
As seen in this screenshot animated properties will show up only with their socket ID in the animation editors.
They also seem start counting via creation, not via order that is visible to the user. In the example case, where is number 1? From the modifier interface I assume property 1, 3,4 and 5 to be animated but the graph and dope editor show 2,4,5 and 6.
I understand that actual channel layout is sorted from top (oldest) to bottom and can be manually corrected. But right now it's really to manually order these as I cant tell wich channel is assigned to which value.
(Geometrynodes) Modifier inputs can have customized names. Will it be possible to also access these from the animation editors?
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
I am not sure if this is considered as resolved or whether there was some development that is not completely finished, I would advise to not change status of this task.
Added subscriber: @intracube
Added subscriber: @lateasusual
I saw this issue mentioned and had a short look at fixing the modifier input naming, by just attempting to lookup the node-group socket label from the identifier:
It may not be the most correct or best way to do it, but it does work so just thought i'd share anyway :)
show_socket_names_fcurve.diff
Added subscriber: @costa
@lateasusual : please submit a Diff https://wiki.blender.org/wiki/Process/Contributing_Code, chances are better this gets attention then
@lichtwerk Will do, I didn't have time to submit one earlier and forgot about it :)
Added subscriber: @otherivan
Yes, right, fix it please. I animated group inputs of geo nodes tree and I could see only titles input_13, input_14. Group inputs have names, I think it's not too difficult to display these. They are correct for built-in modifiers
Added subscriber: @BClark
I was asking about this and just hit this issue trying to script driver setups since I couldn't get the names, only values.. so adding to the requests.
Met the same issue. Won't solve the problem entirely but the temporary solution is animate custom properties with readable names and attach geo nodes properties to them with drivers.