Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
2022.3.10f1
2023.1.14f1
2023.2.0b11
2023.3.0a6
Issue ID
UUM-51816
Regression
No
Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
How to reproduce:
1. Open any project
2. In the Project Browser select an Asset
3. In the Inspector for that Asset scroll down to the very bottom to "AssetBundle"
4. Observe the "AssetBundle" label
5. Observe the second drop-down menu without label
6. Try and create "something" new in the second dropdown menu
Expected result: "AssetBundle" has spacing -> "Asset Bundle" (Editor Design Consistency), The second dropdown menu has to have a label or other form of indication as to what it is (Asset Bundle variant). The second dropdown menu should not be available/enabled if the Asset Bundle is not set
Actual result: "AssetBundle" has no spacing, second dropdown menu has no indication as to what it is. If user is setting a variant name without setting the Asset Bundle first, the error "Cannot set the AssetBundle variant "asdasdas" for asset "Assets/New Render Texture.renderTexture" as the AssetBundle name hasn't been set.
Please set the AssetBundle name before setting the AssetBundle variant." is logged
Reproducible with: 2021.3.29f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b11, 2023.3.0a6
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
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.