Search Issue Tracker
Fixed
Fixed in 1.21.2
Votes
0
Found in [Package]
1.18.16
1.19.19
1.20.3
1.21.1
Issue ID
ADDR-2904
Regression
No
[Addressables] Bundle Naming Mode has a different mode selection when single or multiple assets are selected
Reproduction steps:
1. Open the user’s attached project.
2. Go to Window > Asset Management > Adressables > Groups
3. Select any Addressables Group
4. In the Inspector find and expand the “Bundle Naming Mode” options
5. Inspect given modes
6. Select a few Addressables Groups
7. Inspect given modes
Expected result: Selecting multiple group assets, "Bundle Naming Mode" displays the same modes as a single asset.
Actual result: Selecting multiple group assets, "Bundle Naming Mode" displays different modes than a single asset.
Reproducible with: 1.18.16 (2020.3.38f1), 1.19.19 (2020.3.38f1), 1.20.3 (2020.3.38f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b5, 2023.1.0a6), 1.20.5 (2020.3.38f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b5, 2023.1.0a6)
Reproducible on: Windows 10
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment