GeoNodes: Getting animated/driven Curve Radius doesn't work if curve has shape key #105806

Open
opened 2023-03-15 18:52:47 +01:00 by Demeter Dzadik · 5 comments
Member

System Information
Operating system: Linux-6.2.2-gentoo-x86_64-Intel-R-_Core-TM-i9-9900K_CPU@_3.60GHz-with-glibc2.36 64 Bits
Graphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02

Blender Version
Broken: version: 3.6.0 Alpha, branch: HEAD (modified), commit date: 2023-03-15 05:24, hash: 254e3e133fda
Worked: Likely never

Short description of error
This is a pretty specific set-up on the old Curves, so I'm not sure if it's something that needs to be fixed or if this datablock is getting replaced anyways, but I thought it would at least be good to be aware of.

If a curve has a shape key, the GeoNodes "Radius" node seems to fail to return the correct radius value.

I don't know for sure if this is really a GeoNodes issue, though, because from my testing, the way the Radius value works with shape keys just seems pretty weird. It makes a fair amount of sense until the Radius value gets a driver. At that point, the shape key seems to take on whatever value the Radius had when leaving edit mode.

Exact steps for others to reproduce the error

  • File: radius_driver_not_working.blend
  • Scale the bone; The curve point's radius is hooked up to be driven by the bone's scale, and the sphere is created by GeoNodes based on that curve point's radius. So, when you scale the bone, the sphere gets bigger.
  • Add 2 shape keys to the curve
  • Scale the bone again; Sphere doesn't scale any more.

For my use case, I don't actually need shape keys on my curve, so this won't be an issue for me at all, I just ran into it because I happened to have a temporary shape key on there and I thought I would report it.

**System Information** Operating system: Linux-6.2.2-gentoo-x86_64-Intel-R-_Core-TM-_i9-9900K_CPU_@_3.60GHz-with-glibc2.36 64 Bits Graphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02 **Blender Version** Broken: version: 3.6.0 Alpha, branch: HEAD (modified), commit date: 2023-03-15 05:24, hash: `254e3e133fda` Worked: Likely never **Short description of error** This is a pretty specific set-up on the old Curves, so I'm not sure if it's something that needs to be fixed or if this datablock is getting replaced anyways, but I thought it would at least be good to be aware of. If a curve has a shape key, the GeoNodes "Radius" node seems to fail to return the correct radius value. I don't know for sure if this is really a GeoNodes issue, though, because from my testing, the way the Radius value works with shape keys just seems pretty weird. It makes a fair amount of sense until the Radius value gets a driver. At that point, the shape key seems to take on whatever value the Radius had when leaving edit mode. **Exact steps for others to reproduce the error** - File: [radius_driver_not_working.blend](/attachments/7e1b8e22-4625-4337-a4b3-5e1dfca8f014) - Scale the bone; The curve point's radius is hooked up to be driven by the bone's scale, and the sphere is created by GeoNodes based on that curve point's radius. So, when you scale the bone, the sphere gets bigger. - Add 2 shape keys to the curve - Scale the bone again; Sphere doesn't scale any more. For my use case, I don't actually need shape keys on my curve, so this won't be an issue for me at all, I just ran into it because I happened to have a temporary shape key on there and I thought I would report it.
Demeter Dzadik added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-03-15 18:52:47 +01:00

Hello. Simplify the file. It's better to start from scratch. Whatever there are unrelated scripts that ask to run when the project is opened.
If you create an object that copies the curve and converts it to a mesh using a profile, you can see that there is a radius. The presence of shape keys does not affect this. But the bone binding stops working. It seems to be just some kind of limitation not related to geometry nodes, Need check in older versions...

Hello. Simplify the file. It's better to start from scratch. Whatever there are unrelated scripts that ask to run when the project is opened. If you create an object that copies the curve and converts it to a mesh using a profile, you can see that there is a radius. The presence of shape keys does not affect this. But the bone binding stops working. It seems to be just some kind of limitation not related to geometry nodes, Need check in older versions...

Yes, this is not a regression, it was like that before (2.9). It doesn't look like a bug yet.

Yes, this is not a regression, it was like that before (2.9). It doesn't look like a bug yet.
Iliya Katushenock added the
Interest
Animation & Rigging
Interest
Modeling
labels 2023-03-15 20:15:02 +01:00

The fact this is not a regression doesn't mean this is not a bug. toggling edit mode of curve resulted in sphere changing radius, so this looks like missing update somewhere.

The fact this is not a regression doesn't mean this is not a bug. toggling edit mode of curve resulted in sphere changing radius, so this looks like missing update somewhere.
Richard Antalik added
Module
Modeling
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-03-16 05:41:16 +01:00
Author
Member

I feel like I might've ended up reporting two issues in one here.

Now that I've had a good night's sleep, I ask myself why I didn't report the shape key behaviour as a separate issue, since that's already a piece of weird behaviour worthy of a report, before I even involve any GeoNodes.

Would it be okay to edit this report to focus only on the funky behaviour of curve shape keys when the Radius value is driven? I'm hesitant, now that it's been confirmed and categorized. I'm also hesitant because I'm not sure if the current Curve datablock is slated for deprecation soon? In which case I don't want to waste anyone's time.

I feel like I might've ended up reporting two issues in one here. Now that I've had a good night's sleep, I ask myself why I didn't report the shape key behaviour as a separate issue, since that's already a piece of weird behaviour worthy of a report, before I even involve any GeoNodes. Would it be okay to edit this report to focus only on the funky behaviour of curve shape keys when the Radius value is driven? I'm hesitant, now that it's been confirmed and categorized. I'm also hesitant because I'm not sure if the current Curve datablock is slated for deprecation soon? In which case I don't want to waste anyone's time.

@Mets Sure, feel free to simplify provided files

@Mets Sure, feel free to simplify provided files
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#105806
No description provided.