Search Issue Tracker
Fixed
Fixed in 6000.0.39f1, 6000.1.0b6, 6000.2.0a4
Votes
0
Found in
6000.0.33f1
6000.1.0a10
6000.2.0a1
7000.0.0a1
Issue ID
UUM-91772
Regression
Yes
FaceFont value of FontEngine.GetFaceInfo will become 0 when FontEngine.LoadFontFace is called multiple times for the same font
Reproduction steps:
1. Open the attached project "ReproProj"
2. Build and Run the “/Assets/Scenes/SampleScene.unity“ Scene
3. Observe the Player
Expected result: No Errors exist
Actual result: “Arial pointSize:0 accentLine:0 baseline:0 descentLine:0 error!!!!” is present
Reproducible with: 6000.0.1f1, 6000.0.33f1, 6000.1.0a10
Not reproducible with: 2022.3.55f1, 6000.0.0f1
Reproducible on:
Release Build (Windows 10 Enterprise 21H2, MacMini M2)
Development Build (MacMini M2)
Play Mode (MacMini M2)
Not reproducible on:
Development Build (Windows 10 Enterprise 21H2)
Play Mode (Windows 10 Enterprise 21H2)
Testing environment: Windows 10 Enterprise 21H2, MacMini (M2)
Not reproducible on: No other environment tested
Note:
- Does not reproduce when calling FontEngine.GetFaceInfo immediately after calling FontEngine.LoadFontFace(font), however, if calling FontEngine.LoadFontFace(font) again and then call FontEngine.GetFaceInfo will result in FaceFont with various values set to 0
Link to slack thread:
https://unity.slack.com/archives/C0105CH72UV/p1737485246870989
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 6000.2.0a4):
Fixed corruption in FontEngine.GetFaceInfo
Resolution Note (fix version 6000.1.0b6):
Fixed corruption in FontEngine.GetFaceInfo
Resolution Note (fix version 6000.0.39f1):
Fixed corruption in FontEngine.GetFaceInfo