Render issues when two VBD overlap if rendered with motion blur #105549

Open
opened 2023-03-07 20:39:29 +01:00 by Robert Rioux · 6 comments

Blender Version
Broken: 3.2, 3.6
Worked: 3.1

Short description of error
Render issues when two VBD overlap if rendered with motion blur

Exact steps for others to reproduce the error
Render the attached file with and without motion blur. If you render them separatly they both render OK. Only when together it doesn't work.

**Blender Version** Broken: 3.2, 3.6 Worked: 3.1 **Short description of error** Render issues when two VBD overlap if rendered with motion blur **Exact steps for others to reproduce the error** Render the attached file with and without motion blur. If you render them separatly they both render OK. Only when together it doesn't work.
Robert Rioux added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-03-07 20:39:29 +01:00
Author

Looks like my file didn't upload

Looks like my file didn't upload
Author

Here's a link for the file. I guess it was too big

https://www.dropbox.com/s/um6au2fze9wvd7b/013_BC_0220_.zip?dl=0

Here's a link for the file. I guess it was too big https://www.dropbox.com/s/um6au2fze9wvd7b/013_BC_0220_.zip?dl=0
Author

Never mind. It was a clipping plane issue. But it doesn't make much sens that it does that only when MB is on.

Never mind. It was a clipping plane issue. But it doesn't make much sens that it does that only when MB is on.
Iliya Katushenock added the
Interest
Render & Cycles
label 2023-03-07 21:37:24 +01:00
Member

Hi, thanks for the report. I can confirm the behavior.
From quick testing, this looks like a regression (Raising the priority, feel free to lower the priority since it's not a "very recent" change)

3.1 3.6/3.2
image image

**System Information**
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```
Hi, thanks for the report. I can confirm the behavior. From quick testing, this looks like a regression (Raising the priority, feel free to lower the priority since it's not a "very recent" change) | 3.1 | 3.6/3.2 | -------- | -------- | | ![image](/attachments/b07a9dba-ea45-4b7d-9564-acc21315aaa1) | ![image](/attachments/da74a7a7-029f-4785-bfb3-ba2667e0437d) | - - - ``` **System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```
1.2 MiB
1.3 MiB

Volume motion blur was introduced in 3.2, this is not a regression.

Volume motion blur was introduced in 3.2, this is not a regression.
Brecht Van Lommel added
Priority
Normal
Type
Bug
and removed
Priority
High
Type
Report
labels 2023-03-10 15:14:38 +01:00

I’ve just updated my original bug report on a similar topic to this one. I’m writing here to invite you to look at it as it probably demonstrates the cause of the problem or a part of it.

I ran an extensive and very detailed test. Originally, I had written about overlapping volumes creating artifacts. In my new test, I discovered that non-overlapping volumes also have artifacts, but are only visible in particular cases.

I believe it is related to this report and developers should look at it in connection with this report here as it provides a new perspective and elements to understand the strange artifacts in volumes.

My new post is on October 1, 2023.
#107418 (comment)

I’ve just updated my original bug report on a similar topic to this one. I’m writing here to invite you to look at it as it probably demonstrates the cause of the problem or a part of it. I ran an extensive and very detailed test. Originally, I had written about overlapping volumes creating artifacts. In my new test, I discovered that non-overlapping volumes also have artifacts, but are only visible in particular cases. I believe it is related to this report and developers should look at it in connection with this report here as it provides a new perspective and elements to understand the strange artifacts in volumes. My new post is on October 1, 2023. https://projects.blender.org/blender/blender/issues/107418#issuecomment-1035101
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
4 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#105549
No description provided.