Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.5.4
Issue ID
LOC-1197
Regression
No
Custom SDF Font shaders are duplicated or are incorrectly perceived as duplicated when Addressables with the Custom fonts are built
How to reproduce:
1. Open the “IN-96295.zip“ project
2. Open the Window > Asset Management > Addressables > Groups
3. Press Build > New Build > Default Build Script
4. Observe the Addresables Report
Expected result: No warning is displayed
Actual result: In the Summary section, a “2 Duplicate Assets were detected in the build“ warning is displayed
Reproducible in: 1.4.5, 1.5.4 (2022.3.59f1, 6000.41f1, 6000.1.0b9, 6000.2.0a6)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Built-in fonts do not seem to cause this problem
- Bug appears to only occur when the fonts are placed within the Localization Asset Tables
- Each unique custom font adds 1 “Duplicated asset” (i.e. if only one of the custom fonts is used in the Localization Tables, only 1 duplicate will be detected)
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note:
After further investigation, I can confirm that this behavior is intended. The two font files share certain dependencies. When a shared dependency is not marked as addressable, it gets copied into both Addressable groups, which creates duplication.
To resolve this issue, you can mark the shared dependency as addressable in the asset settings. For better organization, you might consider moving it into a separate, shared Addressables group if needed. Unfortunately, it is not possible to automate this process within the localization system at this time.