Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.23f1
2023.2.17f1
6000.0.0b14
Issue ID
UUM-69151
Regression
No
"Generated inconsistent result" warning is shown when reimporting a single Dynamic font asset
Reproduction steps:
1. Open the attached “DynamicFontImporterInconsistentResult.zip” Project
2. Open the “SampleScene” (Scenes > SampleScene)
3. In the Project Window reimport “NotoSansCJKjp-Medium SDF.asset” (Assets > Fonts)
4. Observe the Console
Expected result: No warnings are shown in the Console
Actual result: “Importer(NativeFormatImporter) generated inconsistent result for asset(guid:35c8d54f5b49dc743ac61c75e7743446) "Assets/Fonts/NotoSansCJKjp-Medium SDF.asset"
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” warning is shown in the Console
Reproducible with: 2021.3.37f1, 2022.3.23f1, 2023.2.17f1, 6000.0.0b14
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Reproduction might be inconsistent as sometimes it only shows up after entering and exiting the Play mode or reimporting a few times, but the warning also reappears when clicking “Clear Dynamic Data” for the “NotoSansCJKjp-Medium SDF.asset” (This option is located when selecting the asset and clicking on the three dots in the Inspector)
- Deleting the Library folder solves the issue temporarily
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
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
Resolution Note:
Thank you for reporting a bug to Unity.
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.