Search Issue Tracker
Fixed in 0.6.6-preview
Votes
0
Found in [Package]
0.5.3-preview
Issue ID
1116029
Regression
No
[Addressables] "ActivePlayerDataBuilderIndex" value is changed, instead of "ActivePlayModeDataBuilderIndex"
[Addressables] "ActivePlayerDataBuilderIndex" value is changed, instead of "ActivePlayModeDataBuilderIndex" and no NULL check for "ActivePlayModeDataBuilder"
Reproduction steps:
1. Open "MinimalRepro" project
2. Search for and open in VS "AddressableAssetSettings.cs" in the Packages Folder
3. In line 687, instead of "ActivePlayModeDataBuilderIndex" value being changed, "ActivePlayerDataBuilderIndex" value is changed
4. In line 686 "ActivePlayModeDataBuilder" doesn't have a NULL check
Expected Result: Proper value to be changed and a NULL check to be present
Actual Result: Wrong value is changed and no NULL check is present
Reproduced with: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1
Did not reproduce on: 2017.4.19f1 (No pacman)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment