Motion Blur artefacts in Viewport #127107
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#127107
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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
Graphics card: 3080 RTX
Blender Version
Broken: 4.3.0-alpha+main.e26e62597da5
Worked: (newest version of Blender that worked as expected)
Short description of error
The Motion Blur in the Viewport has some artefacts on fast stuff.
using Temporal Reprojection makes it even worse
I'm not shure if this is excpected, but since the render looks quite different...
(In the my References, the camera rotates with 22.5° per frame and no Temporal Reprojection)
Exact steps for others to reproduce the error
Set the Motion Blur to 1, so it's more visible
move anything fast
I have similar issues. The motion blur works fine at first, then when I hide / unhide any object in the viewport there is heavy flickering in the viewport (Note: renders seem ok)
It only occurs with temporal reprojection turned on, disappears after reloading or switching to a different vp shading mode but occurs in both material preview and render mode.
(latest alpha, Win 10, GTX 1060 6MB)
I can confirm the flicker after hiding-showing an object in @heini 's file, so that's definitely a bug, but that's with temporal reprojection turned on, while @Marc-Schwindt doesn't have it on. So we have TWO bugs in this one 🤔
I have set up a file where the square rotates ridiculously fast, this is what it looks like without temporal reprojection. Looks like it might just be using speed vector and interpolate linearly so the blur actually extend beyond the rotation area and have some missing blocks visually. Not sure if this is a known limitation @fclem