Motion vector texture contains outdated info during and before the 'AfterRenderingTrasnparents' injection point

Unity: Post-processing and Compositing

URP

Fixed

6.0.X

2023.3.X

2023.2.X

2023.2.17f1

2022.3.X

2022.3.23f1

Won't Fix

2023.1.X

Motion Vector pass order now correctly follows the Copy Depth pass. Motion Vectors can now be rendered after Opaques, instead of always rendering after Transparents.

Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Open the Frame Debugger (Window > Analysis > Frame Debugger)
4. In the Frame Debugger Window, press the “Enable” button
5. Observe the “Motion Vectors” rendering event

Expected result: The “Motion Vectors” rendering event is created after the “Render PostProcessing Effects” rendering event
Actual result: The “Render PostProcessing Effects” rendering event occurs after the “Motion Vectors” rendering event

Reproducible with: 2022.3.10f1, 2023.1.17f1, 2023.2.0b14. 2023.3.0a10
Could not test with: 2021.3.31f1 (Two “error CS1061: 'ScriptableRenderer' does not contain a definition for 'cameraColorTargetHandle'“ compilation errors)

Reproducible on: Intel macOS 14
Not reproducible with: No other environment tested

Motion vector texture contains outdated info during and before the 'AfterRenderingTrasnparents' injection point

Unity: Post-processing and Compositing

Fixed

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Motion vector texture contains outdated info during and before the 'AfterRenderingTrasnparents' injection point

Unity: Post-processing and Compositing

Statuses

Fixed

Won't Fix

Resolution Notes

2023.3.XFixedMotion Vector pass order now correctly follows the Copy Depth pass. Motion Vectors can now be rendered after Opaques, instead of always rendering after Transparents.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?