Change Details

**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: `rBfb2cb0324a39` Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `rBc77597cd0e15` Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: `rBdc2d18018171` Broken: version: 2.93.8, branch: master, commit date: 2022-02-01 21:14, hash: `rB09da7f489ad9` Worked: version: 2.83.18, branch: master, commit date: 2021-09-28 14:02, hash: `rB00b0253c46cb` **Short description of error** The provided Blend file shows some strange behavior when rendering consecutive frames. For one frame, some objects render black. It occurs when rendering Cycles on CPU as well as GPU. I cannot reproduce the issue if I disable `persistent data` or `motion blur`. |Frame|Render Result| |19|{F12951023}| |20|{F12951026}| |21|{F12951029}| First reported here: T96818 **Exact steps for others to reproduce the error** Render frame 19, then 20, then 21. Turn off persistent data and try again. Observe the difference. {F12950926}

**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: `rBfb2cb0324a39` Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `rBc77597cd0e15` Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: `rBdc2d18018171` Broken: version: 2.93.8, branch: master, commit date: 2022-02-01 21:14, hash: `rB09da7f489ad9` Worked: version: 2.83.18, branch: master, commit date: 2021-09-28 14:02, hash: `rB00b0253c46cb` **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 T96818 and here T92208. **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. {F12952899}

**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: `rBfb2cb0324a39` Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `rBc77597cd0e15` Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: `rBdc2d18018171` Broken: version: 2.93.8, branch: master, commit date: 2022-02-01 21:14, hash: `rB09da7f489ad9` Worked: version: 2.83.18, branch: master, commit date: 2021-09-28 14:02, hash: `rB00b0253c46cb` **Short description of error** The provided Blend file shows some strange behavior when rendering consecutive frames. For one frameWhen using persistent data and motion blur, some objects render black. on the frame where they accelerate from rest, It occurs when rendering Cycles on CPU as well as GPU. I cannot reproduce the issue if I disable `persistent data` or `motion blur`. |Frame|Render Result| |19|1|{F12951023}|2892 size=full}| |20|2|{F12951026}|2894 size=full}| |21|3|{F12951029}|2896 size=full}| First reported here: T968188 and here T92208. **Exact steps for others to reproduce the error** Render frame 19, then 20, then 213. Turn off persistent data and try again. Observe the difference. {F12950926}2899}