Power math node precision issue #101114

Closed
opened 2022-09-16 10:22:22 +02:00 by Serge Lyatin · 7 comments

System Information
Operating system: win10
Graphics card: 1050ti

Blender Version
Broken: 3.3.1 RC
Worked: 2.79b

Short description of error
math_precision.jpg
Difference between 100 and 10^2 produced by Power node is not a zero. But it's correct in 2.79b version.

Exact steps for others to reproduce the error
In provided file unmute/mute Round math node to see a problem
math_precision_issue.blend

**System Information** Operating system: win10 Graphics card: 1050ti **Blender Version** Broken: 3.3.1 RC Worked: 2.79b **Short description of error** ![math_precision.jpg](https://archive.blender.org/developer/F13498629/math_precision.jpg) Difference between 100 and 10^2 produced by *Power* node is not a zero. But it's correct in 2.79b version. **Exact steps for others to reproduce the error** In provided file unmute/mute *Round* math node to see a problem [math_precision_issue.blend](https://archive.blender.org/developer/F13498647/math_precision_issue.blend)
Author

Added subscriber: @SergeL

Added subscriber: @SergeL
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Member

I can confirm the issue. But Blender doesn't do anything special here besides calling the pow function, which may suffer from precision issues as you saw.
As for why it worked in 2.7, likely because it was constant folded by the compiler, which can't happen now because the values are passed as uniforms.
In any case, we don't handle such precision issues as bugs. Users should use expressions like x * x as an alternative.

I can confirm the issue. But Blender doesn't do anything special here besides calling the `pow` function, which may suffer from precision issues as you saw. As for why it worked in 2.7, likely because it was constant folded by the compiler, which can't happen now because the values are passed as uniforms. In any case, we don't handle such precision issues as bugs. Users should use expressions like `x * x` as an alternative.
Author

But why it has no problems with Geometry Nodes Power node? Same setup here works without artificial rounding.

But why it has no problems with Geometry Nodes Power node? Same setup here works without artificial rounding.
Member

Geometry Node executes on the CPU, while shaders execute on the GPU. Both have a different implementation of the power function, and it seems the GPU implementation is less accurate.
Note that the implementation is done by the GPU driver and manufacturer, not by Blender, so we have no control over it.

Geometry Node executes on the CPU, while shaders execute on the GPU. Both have a different implementation of the power function, and it seems the GPU implementation is less accurate. Note that the implementation is done by the GPU driver and manufacturer, not by Blender, so we have no control over it.
Author

Thanks for clarification!

Thanks for clarification!
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
2 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#101114
No description provided.