Camera motion blur bug #72889

New Issue

Andrey · 2020-01-03T23:41:23+01:00

Andrey commented

2020-01-03 23:41:23 +01:00

System Information
Operating system: Windows 10
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

Blender Version
Blender 2.81a

Short description of error
When you change the number of motion blur steps more than 1 for camera, it starts to work incorrectly

Cycles 1 steps

Cycles 3 steps

Cycles 8 steps

Luxcore renderer 50 steps (in luxcore number of steps does not multiply, therefore such a large number)

.blend Camera motion blur bug.blend

Luxcore result looks much more accurate to me.
I also found some strange problem when I made camera object parent of 3D text, but I will talk about it later if necessary.

**System Information** Operating system: Windows 10 Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66 **Blender Version** Blender 2.81a **Short description of error** When you change the number of motion blur steps more than 1 for camera, it starts to work incorrectly Cycles 1 steps ![1 steps.jpg](https://archive.blender.org/developer/F8258874/1_steps.jpg) Cycles 3 steps ![3 steps.jpg](https://archive.blender.org/developer/F8258876/3_steps.jpg) Cycles 8 steps ![8 steps.jpg](https://archive.blender.org/developer/F8258880/8_steps.jpg) Luxcore renderer 50 steps (in luxcore number of steps does not multiply, therefore such a large number) ![Luxcore renderer 50 steps.jpg](https://archive.blender.org/developer/F8258882/Luxcore_renderer_50_steps.jpg) .blend [Camera motion blur bug.blend](https://archive.blender.org/developer/F8258884/Camera_motion_blur_bug.blend) Luxcore result looks much more accurate to me. I also found some strange problem when I made camera object parent of 3D text, but I will talk about it later if necessary.

Andrey commented

2020-01-03 23:41:23 +01:00

Added subscriber: @DEBIHOOD

Andrey commented

2020-01-04 18:54:35 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Marcin Twarowski commented

2020-01-07 10:31:43 +01:00

Added subscriber: @MarcinTwarowski

Marcin Twarowski commented

2020-01-07 10:31:43 +01:00

edited

Andrey commented

2020-01-13 10:36:49 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Needs Triage'

Philipp Oeser commented

2020-01-13 12:33:12 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-13 12:33:12 +01:00

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

Philipp Oeser commented

2020-01-13 12:33:12 +01:00

Can confirm, checking...

This is working fine for moving objects:
#72889.blend

Should be working (78c2063), so assume this is a bug...

EDIT: 78c2063 might not be related in the end, still, report looks like a bug

Can confirm, checking... This is working fine for moving objects: [#72889.blend](https://archive.blender.org/developer/F8275596/T72889.blend) Should be working (78c2063), so assume this is a bug... EDIT: 78c2063 might not be related in the end, still, report looks like a bug

blender-admin commented

2020-05-19 02:51:27 +02:00

This issue was referenced by blender/cycles@04fc69906e

This issue was referenced by blender/cycles@04fc69906e6534b89516474bed6c1949d876209a

blender-admin commented

2020-05-19 02:51:27 +02:00

This issue was referenced by 03fa66d274

This issue was referenced by 03fa66d2740c6ab10df6a86430475dfa98fc0f20

Josh Belanich commented

2020-05-19 03:50:23 +02:00

Added subscriber: @JoshuaBelanich