Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
Issue ID
1340197
Regression
No
Arial.ttf should not appear in the ObjectField of the UIBuilder and UIDebugger.
Arial.ttf is not a real font. It is a shell that the old Text system knows about and that redirects to an OS Font. Since this workflow is not compatible with the new Text system (TextCore) we should strive to hide this font from the UIToolkit users.
1- Open the UI Builder Window
2- Add a Label
3- Set the FontAsset to none
4- Set the Font to Arial.ttf
Expected: The user should not be able to assign "Arial.ttf"
Actual: The user can assign "Arial.ttf" and the UI throws.
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note:
Will fix later.