Search Issue Tracker
Not Reproducible
Votes
1
Found in
2023.1.19f1
2023.2.0b16
2023.3.0a13
6000.0.0b11
Issue ID
UUM-55583
Regression
No
Blur makes it look like meshes are moving away from the first placed mesh when instancing multiple meshes with "Graphics.DrawMeshInstanced" or "DrawMeshInstancedIndirect"
How to reproduce:
1. Open the attached “bug_check_vanilla_True.zip“ project
2. Open the “OutdoorScene“ Scene
3. Enter Play Mode
4. Observe the Game view
Expected result: The blur makes it look like the meshes are moving relative to their velocity
Actual result: The blur makes it look like the meshes are moving away from the 0, 0, 0 position (first-placed mesh)
Reproducible with: 2023.1.19f1, 2023.2.0b16, 2023.3.0a13
Can’t test with: 2021.3.32f1, 2022.3.12f1 (Blur isn’t working)
Reproducible on: macOS 14.0 Sonoma (Intel)
Not reproducible on: No other environment tested
Note: Also reproducible in Player
Comments (1)
-
Ziddon
Aug 21, 2024 07:08
I've just encountered this bug. Had me completely bamboozled for a few hours before I realized it was caused by motion blur. Seems to happen when using a vertex shader (animated vertices) + drawmeshinstancedindirect + motion blurr. Objects are automatically blurred more and more the further from the origin they are.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
After check, we are able to reproduce the issue on 2023.2.20f1 but not on 2023.3.0b7 or 6000.0.3f1. Given 2023.2 is end of life, we will not port fix here (we haven't identify the root cause).