Math node clamp scrolls value between 0 (soft min) and 1 (soft max) instead scrolling between values, that set as min/max #94546
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#94546
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-8.1-6.3.9600-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41
Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-12-29 00:25, hash:
c34ea3323a
Worked: (newest version of Blender that worked as expected)
Short description of error
Title says it clearly.
Expected to have soft minimum = min and soft maximum = max
2022-01-01_15-19-41.mp4
Added subscriber: @Vyach
Added subscriber: @ThomasDinges
Thanks for the report, not sure we consider this a bug, but I'll leave it open for further investigation.
Yep, I am also not sure, if it is a bug, but for me it hard to imagine, that it was intended. More like accidental.
Added subscriber: @BartekMoniewski
Soft min/max doesn't make sense in this value field. It should behave like other mathematical nodes and accept arbitrary numerical input. Use case for it would be Value set by the user and Min and/or Max values driven by an input, eg a texture.
Added subscribers: @JacquesLucke, @HooglyBoogly
I also think removing the soft min and max is the best approach. It's not currently possible to make them dynamic, and the whole point of the node is that the value input has a larger range than the min and max inputs anyway.
@JacquesLucke, are you okay with removing the soft range?
I agree, that it is better to remove soft limits than to leave it as is, if there is no time to implement smarter behavior.
But, soft limits according disconnected input will be sane too, if we speak about case, that @BartekMoniewski shown.
I mean no limit for min, because we don`t know what is there and soft limit to max, because there is no point to set higher value manually.
Maybe we can make the soft limit more dynamic in the future (mainly needs a socket->node pointer I think). For now I'm fine with removing the soft limit.
This issue was referenced by
070948b5f1
Changed status from 'Needs Triage' to: 'Resolved'
fine too, thanks :)