Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.33f1
2022.3.15f1
Issue ID
UUM-57924
Regression
No
Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
Reproduction steps:
1. Create a new project
2. Download and import "Viking Village URP" and open the “The_Viking_Village” Scene
3. Download and import "Third Person Controller + Fly Mode"
4. Observe the Scene window
Expected result: Shaders don’t get corrupted
Actual result: Shaders get corrupted and Textures become pink
Reproducible with: 2021.3.33f1, 2022.3.15f1
Could not test with: 2023.2.3f1, 2023.3.0a17 (broken Shaders due to errors in the Console)
Reproduced on: macOS Sonoma 14.1.1 (Intel), Windows 11 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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.