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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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.