[ ] Have you added a backport label (if needed)? For example, the need-backport-* label. After you backport the PR, the label changes to backported-*.
[ ] Have you updated the changelog? Each package has a CHANGELOG.md file.
[ ] Have you updated or added the documentation for your PR? When you add a new feature, change a property name, or change the behavior of a feature, it's best practice to include related documentation changes in the same PR. If you do add documentation, make sure to add the relevant Graphics Docs team member as a reviewer of the PR. If you are not sure which person to add, see the Docs team contacts sheet.
[ ] Have you added a graphic test for your PR (if needed)? When you add a new feature, or discover a bug that tests don't cover, please add a graphic test.
Purpose of this PR
Why is this PR needed, what hard problem is it solving/fixing?
Fix deprecated API warning by passing motion vector color and depth RTs as RTHandles instead of RenderTargetIdentifiers
Testing status
Describe what manual/automated tests were performed for this PR
Built and ran on Quest with AppSW Enabled, verified MotionVectors were rendered as expected
Please read the Contributing guide before making a PR.
Checklist for PR maker
need-backport-*label. After you backport the PR, the label changes tobackported-*.CHANGELOG.mdfile.Purpose of this PR
Why is this PR needed, what hard problem is it solving/fixing?
Fix deprecated API warning by passing motion vector color and depth RTs as RTHandles instead of RenderTargetIdentifiers
Testing status
Describe what manual/automated tests were performed for this PR
Built and ran on Quest with AppSW Enabled, verified MotionVectors were rendered as expected
Comments to reviewers
Notes for the reviewers you have assigned.