Page MenuHome

Changing the 'Render Region' when rendering with Python with 'Persistent Images' checked results in glitched renders
Open, Needs Triage by DeveloperPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30

Blender Version
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-10-21 13:53, hash: rB200267eb968d
Worked: -

Short description of error

I have a (simplified) script that moves to a specific frame, sets the render region to a specific position and renders, before repeating the process for the next frame with a new render region position. When the 'Persistent Images' option in Render> Performance> Final Render is on, some of the resulting renders are glitched (they open but have artifacts) and the objects do not seem to be in the correct position.

Turning off 'Persistent Images' results in renders with the objects in the expected location and without artifacts.

For some context, I do not specifically want to have 'Persistent Images' on; I have an add-on which repositions the render border on a per-frame basis and a user reported glitching renders.

Frame 8 - Persistent Images off - Correct location in render

Frame 8 - Persistent Images on - Incorrect location in render and artifacts

Frame 7 - Persistent Images off - Correct location in render

Frame 7 - Persistent Images on - Incorrect location in render

Exact steps for others to reproduce the error

  1. Open the attached blend file and set an output directory for the render.
  2. Press 'Run Script' in the open text editor to render out the images.

Images 3, 7, 8 and 9 will probably have artifacts and for the other frames the objects will be in the incorrect location (the border should be positioned perfectly around them).

Note: I have set the script to render 10 frames because it seems to depend on what was rendered previously as to whether the glitches/incorrect positions will appear. Rendering the glitched frames on their own does not produce the errors consistently.

Details

Type
Bug

Event Timeline