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
- UI Shader Graph throws 'UnityDisplayOrientationPreTransform' error when Android is the selected platform
- Editor memory leak when entering and exiting Play Mode in a blank URP project
- Point Lights with the "Hard Shadows" Shadow Type appear as black squares when Rendering Path is set to "Forward+" or "Deferred+"
- Error SGICE002 is wrongly shown when the tuple elements in a foreach statement don’t match the order of the tuple returned by SystemAPI.Query
- LockBufferForWrite incorrectly rejects valid writes when GraphicsBuffer size exceeds 32-bit limit due to integer overflow
Add comment