Search Issue Tracker
Fixed
Fixed in 3.1.1
Votes
3
Found in [Package]
3.1.1
Issue ID
PPB-52
Regression
Yes
Motion Blur affects a Terrain when it's Transform position is not zero and is stationary
Reproduction steps:
1. Open the attached “TerrainBug“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter the Play Mode
4. Observe the Game View
Expected result: The terrain is not blurry
Actual result: The terrain is blurry
Reproducible with: 3.3.0, 3.4.0 (2023.1.0a18, 2023.1.20f1, 2023.2.7f1, 2023.3.0b4)
Not reproducible with: 3.3.0, 3.4.0 (2021.3.34f1, 2022.3.18f1, 2023.1.0a17)
Reproducible on: M1 MacOS 14.2, Windows 10 (22H2)
Not reproducible on: No other environment tested
Note: Using MacOS with M1 “RenderingCommandBuffer: shader Hidden/Internal-Loading: invalid pass index (1..5) in DrawMesh“ errors are thrown in the Console
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 3.1.1):
Fixed in Unity Editor version 2023.3.0b6 -- this is an editor issue, package version won't make a difference. Any Unity Editor after 2023.3.0b6 should work as intended.