Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.39f1
2021.3.8f1
2022.1.13f1
2022.2.0b6
2023.1.0a6
2023.2.0a1
Issue ID
UUM-13264
Regression
No
Not all shaders get rendered when using custom Camera Matrix
How to reproduce:
1. Open the attached project “in_9123”
2. Open “SampleScene” in Scenes
3. Select “Main Camera” Camera
4. Attach the Game view somewhere on the screen so it would be visible while moving the camera position
5. Move camera along x axis
6. Observe how shadows are rendered
Expected result: Shadows are rendered while moving the Camera
Actual result: Shadows are not rendered all the time while moving the camera and the Shadow sphere is visible in position: (-700, 60, -3)
Reproducible on: 2020.3.39f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b6, 2023.1.0a6
Reproducible with: Windows 10 Pro
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.