Search Issue Tracker
By Design
By Design in 6000.0.X
Votes
0
Found in
2021.3.37f1
2022.3.22f1
2023.2.17f1
6000.0.0b13
Issue ID
UUM-70647
Regression
No
Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Reproduction steps:
1. Open the attached “MBlurIssue.zip” Project
2. Open the “Scenes/SampleScene” scene
3. Enter the Play mode
4. Observe the Motion Vectors in the Game View
Expected result: The “Motion Vectors” data points in the correct direction for mesh data that was off-screen the previous frame, showing green on the right and yellow on the left
Actual result: The “Motion Vectors" data points in the negative direction for mesh data that was off-screen the previous frame, showing the black and red band at the bottom
Reproducible with: 2021.3.37f1, 2022.3.22f1, 2023.2.17f1, 6000.0.0b13
Reproducible on: Windows 11
Not reproducible with: No other environment tested
Note:
- The reported is using a custom Renderer Feature “MotionBlurRendererFeature” that shows Motion Vectors
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Hi there
I took a look at this, and don't think the issue is with URP. Doing a RenderDoc capture shows that the motion vector texture is generated as expected, without the artifacts from the custom debug view. It's possible that you might not be interpreting the texture correctly.
- Mikkel
Resolution Note (6000.0.X):
Hi there
I took a look at this, and don't think the issue is with URP. Doing a RenderDoc capture shows that the motion vector texture is generated as expected, without the artifacts from the custom debug view. It's possible that you might not be interpreting the texture correctly.
- Mikkel