Random Value node works wrong with Value to String node #93201
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#93201
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.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68
Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-10-31 17:52, hash:
c312c71969
and laterShort description of error
When you set a Random Value node mode to Float, and linked the output socket to float input socket of a Value to String node, the linked line colored red and the Value to String node ignores received value.
Exact steps for others to reproduce the error
P.S. Value to String node works fine with Random Float node. So has the Value to String node not supported field input yet ?
Thanks,
Added subscriber: @SatoshiYamasaki
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @JacquesLucke
Changed status from 'Confirmed' to: 'Archived'
By default the Random Value node outputs a field, because that is typically what one wants. The Value to String node expects a single value though. To make this work you have to tell the Random Value node to output a single value instead of a field by overwriting the ID input. We want to make these implicit field inputs a bit more obvious in the future. Maybe we'll also add a way to disable the implicit field input in the node directly.
The Random Float node is deprecated. It did not output a field by default.
@PratikPB2123
Thank you for confirm!
@JacquesLucke
Thank you for your hard work and the information. I know Ramdom Float node is deprecated, so I tried to use the Random Value node as an alternative because I saw such descriptions in release note. I understand we should do the work around in the meanwhile.