Inconsistent Behavior of Value Clamping in Modifier Panel and Group Input. #97596
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#97596
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: Windows-10-10.0.17134-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11
Blender Version
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-04-23 13:09, hash:
c486da0238Also in 3.1.2
Short description of error
[Value Clamp].mp4
Limit.blend
Added subscriber: @Bradley_G
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @PratikPB2123
Added subscriber: @HooglyBoogly
Hmm, I guess this is an inconsistent use of hard limits vs. soft limits. In the node editor buttons are meant to use soft limits by design, but for the modifier panel I couldn't tell you why it is the way it is.
I'll add this to the agenda for discussion this week in the geometry nodes channel.
Just to mention that any other modifier seems to use soft limits.
For example "Subdivision Surface" modifier, by default it's clamped to 6, but you can type 7,8,9 without problem.
this is equally true to Simple Deform (360 degree), Cast modifier (factor 10), etc.
I think only GN is exhibiting this specific problem of hard limits.
Okay, we agreed that soft limits do make sense here, since it's consistent with the node editor.
Added subscriber: @BlenderBruno
This issue was referenced by
cb92ff7b2dAdded subscribers: @Dan-Chepkwony, @mod_moder
Hello @dan.chepkwony. Hans committed ~fix for this (just no clouse this at this moment) in this week. As i see, you no upload some fix for report, so i remove you as assignee early for make sure that you no take more time for that.
Changed status from 'Confirmed' to: 'Resolved'