Persistent Data Causes Render Errors for Motion Blur #96822

New Issue

Ethan-Hall · 2022-03-28T00:23:53+02:00

Ethan-Hall commented

2022-03-28 00:23:53 +02:00

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79

Blender Version
Broken: version: 3.1.1 Release Candidate, branch: master, commit date: 2022-03-24 13:38, hash: fb2cb0324a
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e
Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: dc2d180181
Broken: version: 2.93.8, branch: master, commit date: 2022-02-01 21:14, hash: 09da7f489a
Worked: 2.92
Worked: version: 2.83.18, branch: master, commit date: 2021-09-28 14:02, hash: 00b0253c46

Caused by cedd8b8c56

Short description of error
When using persistent data and motion blur, objects render black on the frame where they accelerate from rest,
It occurs when rendering Cycles on CPU as well as GPU.

Frame	Render Result
1	{F12952892 size=full}
2	{F12952894 size=full}
3	{F12952896 size=full}

First reported here #96818 and here #92208.

Exact steps for others to reproduce the error
Render frame 1, then 2, then 3. Turn off persistent data and try again. Observe the difference.
#96822.blend

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79 **Blender Version** Broken: version: 3.1.1 Release Candidate, branch: master, commit date: 2022-03-24 13:38, hash: `fb2cb0324a` Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `c77597cd0e` Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: `dc2d180181` Broken: version: 2.93.8, branch: master, commit date: 2022-02-01 21:14, hash: `09da7f489a` Worked: 2.92 Worked: version: 2.83.18, branch: master, commit date: 2021-09-28 14:02, hash: `00b0253c46` Caused by cedd8b8c56 **Short description of error** When using persistent data and motion blur, objects render black on the frame where they accelerate from rest, It occurs when rendering Cycles on CPU as well as GPU. |Frame|Render Result| | -- | -- | |1|{[F12952892](https://archive.blender.org/developer/F12952892/0001.png) size=full}| |2|{[F12952894](https://archive.blender.org/developer/F12952894/0002.png) size=full}| |3|{[F12952896](https://archive.blender.org/developer/F12952896/0003.png) size=full}| First reported here #96818 and here #92208. **Exact steps for others to reproduce the error** Render frame 1, then 2, then 3. Turn off persistent data and try again. Observe the difference. [#96822.blend](https://archive.blender.org/developer/F12952899/T96822.blend)

Ethan-Hall commented

2022-03-28 00:23:53 +02:00

Added subscriber: @Ethan-Hall

blender-admin commented

2022-03-28 00:23:53 +02:00

#97166 was marked as duplicate of this issue

blender-admin commented

2022-03-28 00:23:53 +02:00

#91487 was marked as duplicate of this issue

blender-admin commented

2022-03-28 00:23:53 +02:00

#92208 was marked as duplicate of this issue

Alaska commented

2022-03-28 02:31:37 +02:00

Added subscriber: @Alaska

Alaska commented

2022-03-28 02:31:37 +02:00

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

Alaska commented

2022-03-28 02:31:37 +02:00

I can confirm the issue with OptiX in latest master

System Information
Operating system: Linux-5.16.0-5-amd64-x86_64-with-glibc2.33 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54
Blender version: 3.2.0 Alpha, branch: master, commit date: 2022-03-27 11:25, hash: e2e4c1daaa

I can confirm the issue with OptiX in latest master **System Information** Operating system: Linux-5.16.0-5-amd64-x86_64-with-glibc2.33 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54 Blender version: 3.2.0 Alpha, branch: master, commit date: 2022-03-27 11:25, hash: `e2e4c1daaa`

Kersten Hergert commented

2022-03-28 12:35:20 +02:00

Added subscriber: @EAGLE-LENS

Raimund Klink commented

2022-03-28 17:44:33 +02:00

Added subscriber: @Raimund58

Lt Knb commented

2022-03-28 19:05:36 +02:00

Added subscriber: @Lt-Knb

Lt Knb commented

2022-03-28 19:22:53 +02:00

Is #92208 the same issue? Also #91487 looks related as well

Ethan-Hall commented

2022-03-29 01:00:12 +02:00

@Lt-Knb I think you are right, it does look like the same issue as #92208.

The issue looks like it only occurs on the first frame when a motion blurred object accelerates from stationary.

@Lt-Knb I think you are right, it does look like the same issue as #92208. The issue looks like it only occurs on the first frame when a motion blurred object accelerates from stationary.

Ethan-Hall changed title from ~~Persistent Data Causes Render Errors~~ to Persistent Data Causes Render Errors for Motion Blur

2022-03-29 01:19:48 +02:00

Ethan-Hall commented

2022-03-29 01:22:45 +02:00

@Lt-Knb Thanks to your comment, I was able to identify the issue and create a minimal example. 🙂

Ethan-Hall commented

2022-03-29 01:25:43 +02:00

Added subscriber: @mltx

Ethan-Hall commented

2022-03-29 01:25:43 +02:00

I went back to read the comments on #92208, and it looks like @mltx also reached the same conclusion.

Ethan-Hall commented

2022-03-29 01:28:32 +02:00

Added subscriber: @iss

Ethan-Hall commented

2022-03-29 01:28:32 +02:00

@iss I am poking you since you were looking into #92208.

Lt Knb commented

2022-03-29 02:14:43 +02:00

@Ethan-Hall Glad I could help :)

Richard Antalik commented

2022-03-29 02:40:57 +02:00

Seems to be same issue as #92208, but this report seems to contain better repro case, so will merge other report here.

Richard Antalik commented

2022-03-29 02:42:33 +02:00

Added subscriber: @otherivan

poq poq commented

2022-03-31 03:27:14 +02:00

Added subscriber: @poqpoq

Philipp Oeser commented

2022-04-06 15:23:50 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-04-06 15:23:50 +02:00

#95404 (Persistent Data causes the Image Editor to not update during rendering + pixel glitches in topper pixel lines) and #91487 (Persistent Data & Motion Blur cause some frames to look weird when rendering animation in Cycles) seem related

Philipp Oeser commented

2022-04-06 16:58:34 +02:00

Added subscriber: @brecht

Philipp Oeser commented

2022-04-06 16:58:34 +02:00

I actually think there might be more duplicates out there.

I bisected this and this is caused by cedd8b8c56.
And we now have a very simple repro case (other reports had large files and it was never really clear which frame failed, the file from this report is super clear).
And even though the bug is a bit older now I will dare setting this to High priority (since it can be a pain if you run into it with no clear way to work around).

@brecht: mind checking?

I actually think there might be more duplicates out there. I bisected this and this is caused by cedd8b8c56. And we now have a very simple repro case (other reports had large files and it was never really clear which frame failed, the file from this report is super clear). And even though the bug is a bit older now I will dare setting this to High priority (since it can be a pain if you run into it with no clear way to work around). @brecht: mind checking?

Philipp Oeser commented

2022-04-06 17:13:23 +02:00

Added subscriber: @Gyoo18