Output time remapping with Eevee motion blur can cause render to fail. #79939

New Issue

Paul R · 2020-08-20T08:48:39+02:00

Paul R commented

2020-08-20 08:48:39 +02:00

System Information
Operating system: SUSE Leap 15.1
Graphics card: NVidia RTX 2070 Super (official drivers)

Blender Version
Broken: 2.90, 83c78529b9, x86_64 linux, 2020-08-19
Worked: 2.90, aed11c673e, x86_64 linux, 2020-06-06

Short description of error
Some combinations of output time remapping along with a high motion blur shutter and step values can cause rendering to fail. F12 renders can cause the global frame to jump forwards while animation rendering can fail after outputting a single frame.

Exact steps for others to reproduce the error
#79939.blend

With the default scene, set the following parameters:

Time remapping (Output properties->Dimensions->Time remapping)
Old: 100
New: 400

Motion Blur
Shutter: 8.0
Steps: 32

(Make sure global frame is set to 1)

Result:
An F12 render will cause the global frame to jump to 4. Resetting back to 1 and rendering an animation (with default range 1-250) will result in only frame 0004.png being written out.

Observations:

Blender versions that predate the new mblur steps feature don't show this issue (early June and before)
Some time remapping combinations like 100:200 or 100:800 with the mblur parameters listed above don't trigger this issue.
Different mblur values will cause the time remapping to fail inconsistently.

**System Information** Operating system: SUSE Leap 15.1 Graphics card: NVidia RTX 2070 Super (official drivers) **Blender Version** Broken: 2.90, 83c78529b9ef, x86_64 linux, 2020-08-19 Worked: 2.90, aed11c673efe, x86_64 linux, 2020-06-06 **Short description of error** Some combinations of output time remapping along with a high motion blur shutter and step values can cause rendering to fail. F12 renders can cause the global frame to jump forwards while animation rendering can fail after outputting a single frame. **Exact steps for others to reproduce the error** [#79939.blend](https://archive.blender.org/developer/F8798885/T79939.blend) With the default scene, set the following parameters: Time remapping (Output properties->Dimensions->Time remapping) Old: 100 New: 400 Motion Blur Shutter: 8.0 Steps: 32 (Make sure global frame is set to 1) **Result:** An F12 render will cause the global frame to jump to 4. Resetting back to 1 and rendering an animation (with default range 1-250) will result in only frame 0004.png being written out. **Observations:** - Blender versions that predate the new mblur steps feature don't show this issue (early June and before) - Some time remapping combinations like 100:200 or 100:800 with the mblur parameters listed above don't trigger this issue. - Different mblur values will cause the time remapping to fail inconsistently.

Paul R commented

2020-08-20 08:48:39 +02:00

Added subscriber: @intracube

Raimund Klink commented

2020-08-20 15:12:59 +02:00

Added subscriber: @Raimund58

Raimund Klink commented

2020-08-20 15:12:59 +02:00

I can recreate the jump to frame 4.
I also noticed weird behaviours from Blender while trying to render a animation from frame 2 to 250.

Tested with version: 2.90.0 Beta, branch: master, commit date: 2020-08-19 10:14, hash: 83c78529b9, type: Release build date: 2020-08-19, 21:11:14

system-info_2.90.txt

I can recreate the jump to frame 4. I also noticed weird behaviours from Blender while trying to render a animation from frame 2 to 250. Tested with version: 2.90.0 Beta, branch: master, commit date: 2020-08-19 10:14, hash: 83c78529b9ef, type: Release build date: 2020-08-19, 21:11:14 [system-info_2.90.txt](https://archive.blender.org/developer/F8796719/system-info_2.90.txt)

Raimund Klink commented

2020-08-21 00:20:41 +02:00

Added subscriber: @fclem