Search Issue Tracker
In Progress
Won't Fix in 2023.2.X
Votes
1
Found in
2023.2.7f1
Issue ID
UUM-61079
Regression
Yes
Decal GameObject is flickering when changing the Camera’s position if using the “Deferred” Rendering Path and “DBuffer” Decal Type
How to reproduce:
1. Open the user’s attached “DecalTest.zip” project
2. In the Hierarchy window, select “Main Camera” GameObject
3. In the Inspector window, keep changing the Position Y value
4. Observe the Game window
Expected result: “Decal Projector” GameObject doesn’t disappear
Actual result: “Decal Projector” GameObject disappears with some values
Reproducible with: 16.0.3 (2023.2.0a23), 16.0.5 (2023.2.7f1)
Not reproducible with: 12.1.3 (2021.3.34f1), 14.0.10 (2022.3.18f1), 16.0.2 (2023.2.0a22), 17.0.0 (2023.3.0a2), 17.0.2 (2023.3.0b4)
Reproduced on: macOS 13.6.3 (Intel)
Not reproducible on: No other environment tested
-
rospeathstudios
Mar 08, 2024 11:32
This bug has prevented me from upgrading to 2023.2. I suspect deferred pipeline URP with DBuffer decals is not a rare mixture and this issue causes any camera movement to make all decals flicker & bounce, making it absolutely game breaking. Could this please be looked at with some urgency?
Changing decals to screen space comes with their own visual problems (seemingly fixed in 2023.3) so this isn't a option either.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.